On 2018-04-25 07:13, Gandalf Corvotempesta wrote:
2018-04-23 17:16 GMT+02:00 David Sterba <dste...@suse.cz>:
Reviewed and updated for 4.16, there's no change regarding the overall
status, though 4.16 has some raid56 fixes.
Thank you!
Any ETA for a stable RAID56 ? (or, even better, for a stable btrfs
ready for production use)
I've seen many improvements in these months and a stable btrfs seems
to be not that far.
Define 'stable'.
If you want 'bug free', that won't happen ever. Even 'stable'
filesystems like XFS and ext4 still have bugs found and fixed on a
somewhat regular basis. The only filesystem drivers that don't have
bugs reported are either so trivial that there really are no bugs (see
for example minix and vfat) or aren't under active development (and
therefore all the bugs have been fixed already).
If you just want 'safe for critical data', it's mostly there already
provided that your admins and operators are careful. Assuming you avoid
qgroups and parity raid, don't run the filesystem near full all the
time, and keep an eye on the chunk allocations (which is easy to
automate with newer kernels), you will generally be fine. We've been
using it in production where I work for a couple of years now, with the
only issues we've encountered arising from the fact that we're stuck
using an older kernel which doesn't automatically deallocate empty chunks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
