I've recently learned that the btrfs options at boot time include a 'no barriers' option. This reduces write times, but puts data in danger if you experience lock-ups (like me) or power outages. From the btrfs wiki (https://btrfs.wiki.kernel.org/index.php ... e/btrfs(5) ): "Disabling barriers gets rid of that penalty but will most certainly lead to a corrupted filesystem in case of a crash or power loss. The ordinary metadata blocks could be yet unwritten at the time the new superblock is stored permanently, expecting that the block pointers to metadata were stored permanently before."
see here : https://pastebin.com/F2jHq8hx -- search for barriers. You'll see that as soon as the device brought up my now corrupted 16tb array, it disabled barriers. When I chatted with those in the #btrfs IRC, they were shocked that this was put into a production environment.
So, if you're going to use btrfs on your RAID on a Terramaster device, make sure you have a UPS.
It really stinks that dev decided to do this.
If you're running a Teramaster NAS, get a UPS... else corruption
Re: If you're running a Teramaster NAS, get a UPS... else corruption
Hi jbeazell,
Thank you very much for your report!
We have made some optimizations to the configuration of the btrfs file system, including the barriers option you have feedback. These optimizations will be released in next update.
Thank you very much for your report!
We have made some optimizations to the configuration of the btrfs file system, including the barriers option you have feedback. These optimizations will be released in next update.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)