3 ms·
A filesystem should systematically from the ground up be designed to be safe, specially one making the claims of BTRFS. BTRFS however went threw a number of cy
by nickik 6y ago
A filesystem should systematically from the ground up be designed to be safe, specially one making the claims of BTRFS.
BTRFS however went threw a number of cycles where it was considered save and then end up having issues. Of course there were always features considered unstable. It eating my own data, using non of the unstable features at the time. Maybe I could have recovered it but neither me nor the best IT person I know could recover anything.
My file system rule is simple, eat my data once and I will never use you again.
Maybe its all fine now, and all these issues are gone. Likely this is the case, however I will not use it again.
I would not recommend people not use it, but I'm simply not going to.
- ulzeraj 6y agoMicro-OS uses BTRFS for operating system only. User data defaults to XFS. The transactional-server role mounts the operating system as read only with /var and /etc being virtual file systems that are committed each shutdown. You can use whatever you want including ZFS for your data.
- Conan_Kudo 6y agoThat's not true. User data has defaulted to Btrfs for over two years now. This change occurred across the entire family of openSUSE distributions.
- pnutjam 6y agoThings change, new stuff always takes awhile to stabilize. ZFS went into Solaris n 2001, Btrfs went into the Linux kernel in 2013. I've been using it for at least 5 years with no issues.