July 15, 201510 yr This applies to reads as well: depending on nature of the defect, it could take a "long" time to complete a read. At least in unRaid parity-protected array case, if read should fail with unrecoverable error, we will 'rebuild' the data by reading all the other devices and use parity reconstruction. In this case, we then try to write the rebuilt data back to the device - If the device is seriously defective this write will fail, resulting in disabling it. It has long been reported that only a failed write would cause a disk to be kicked, but I always felt that a failed read would lead to a failed write, and a disk being kicked, as you explain. Thanks for confirming.
July 15, 201510 yr Author I have been using 2x120GB btrfs raid1 cache pool since v6b6 without issue. I have a 20GB docker.img on it which I have never come close to filling, I do not cache user share writes, I have about a dozen dockers using it for appdata, and I typically only have about 40% used space of the 120GB. How do you tell unRAID not to use the cache for user share writes?
July 15, 201510 yr I have been using 2x120GB btrfs raid1 cache pool since v6b6 without issue. I have a 20GB docker.img on it which I have never come close to filling, I do not cache user share writes, I have about a dozen dockers using it for appdata, and I typically only have about 40% used space of the 120GB. How do you tell unRAID not to use the cache for user share writes? Each user share can be configured to use or not use the cache drive to cache writes.
August 12, 201510 yr Another way would be to remove device, balance, remove next device, balance, etc., until down to one device.Tried that, didn't work. http://lime-technology.com/forum/index.php?topic=41326.msg392229#msg392229 The code I'm looking at, 6.0.1, in case where only one device is left in the pool executes /sbin/btrfs balance start -f -dconvert=single -mconvert=single /mnt/cache and then /sbin/btrfs device delete missing /mnt/cache The fact the post you cite does not have those lines means either that person was using an older version, or there's a bug. I am facing the same situation. Have added a second cache drive and then removed it. After removing it, my 1st cache drive can no longer be mounted and shows as unmountable. I tried above, but the cache drive cannot be found (which makes sense as it is not unmountable). Any thoughts what to do? Would love to have my data back. Thanks!
August 12, 201510 yr I tried above, but the cache drive cannot be found (which makes sense as it is not unmountable). Any thoughts what to do? Would love to have my data back. Thanks! Please post a report on the Defects board and include your system log.
August 14, 201510 yr execute the 'balance' utility (via the 'cache' page link). where is this cache page in the webui?
August 14, 201510 yr execute the 'balance' utility (via the 'cache' page link). where is this cache page in the webui? Main - Cache Devices - click Cache. This will take you to a page with Cache Settings. Look under Balance Status.
Archived
This topic is now archived and is closed to further replies.