>> # btrfs balance start -v -dusage=5 /var/spool/cyrus/ >> Dumping filters: flags 0x1, state 0x0, force is off >> DATA (flags 0x2): balancing, usage=5 >> Done, had to relocate 213 out of 1302 chunks >> >> >> Now, it's working. > > Why would anybody ever run production data on btrfs? > > https://btrfs.wiki.kernel.org/index.php/Main_Page > > "The Btrfs code base is under heavy development." > > https://btrfs.wiki.kernel.org/index.php/Gotchas > > "Files with a lot of random writes can become heavily fragmented > (10000+ extents) causing trashing on HDDs and excessive multi-second > spikes of CPU load on systems with an SSD or large amount a RAM." > > Unfortunately, both cyrus.index files and skiplist/twoskip databases > get a lot of random writes - though both repack occasionally which > reduces fragmentation. > > I've tried other filesystems a few times, and I keep coming back to > ext4 for consistent performance and crash safety (at least on decent > hardware which doesn't lie about fsync) - XFS has lost data, btrfs has > always been shiny at first, but turned into a performance disaster > over time. > > -- > Bron Gondwana > br...@fastmail.fm > >
Thanks Bron. I agree. It was a "decisión de mierda". Some years ago, I had problems with reiserfs... Now, this. Now, I have to figure out how to backup data and restore in ext4 partition. Thanks.
