berizzle Posted July 11, 2015 Share Posted July 11, 2015 Updated from 6.0.0 to 6.0.1. I did not start the array after the reboot. Changed array slots from 24 to 22 and cache from 1 to 2. Doing this only to see options for additional cache slots. Now I see the cache drive FS is btrfs and not reiserfs. I start the array and you know the rest, I have an option to format the cache drive. How do I undo what happened? Or at least mount the drive to recover the data? I am surprised this happened. Quote Link to comment
berizzle Posted July 11, 2015 Author Share Posted July 11, 2015 A rebooted did not change the issue. Selecting the cache drive and selecting none and reselecting the drive changed the cache FS to auto. Started the array and all is well. Very odd behavior. Quote Link to comment
itimpi Posted July 11, 2015 Share Posted July 11, 2015 If you want a cache pool (i.e. more than 1 drive) then the only format that is supported for that is BTRFS. This is because it makes use of a BTRFS specific capability to provide redundancy. Quote Link to comment
berizzle Posted July 11, 2015 Author Share Posted July 11, 2015 Understood but it was very odd that there is no warning that the cache drive will be formatted. The drive appeared to be RAW even though it wasn't. What is the benefit of this BTRFS for unRAID? Quote Link to comment
BRiT Posted July 12, 2015 Share Posted July 12, 2015 Raid-1 cache pool of 2 or more drives for your cache system. However, a multitude of users are/were having severe corruption issues with BTRFS that were unfixable so they reverted back to XFS or RFS. I and others don't trust BTRFS for our data drives or even the cache drive. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.