Difference between revisions of "Btrfs"

citation of kernel.org inserted
(test collapsible descriptions)
(citation of kernel.org inserted)
Line 55: Line 55:


==== not stable ? ====
==== not stable ? ====
Sure this is partly right. But please look for the date of such statements. Some seem to date from 10 years ago. So if you want to give btrfs a chance, you have to look for newer statements. Maybe even look at btrfs.wiki.kernel.org sure there is the best information regarding btrfs
The status of btrfs was experimental for a long time, but the the core functionality is considered '''good enough for daily use'''. <small>(from kernel.org)</small>
 
If you see statements declaring Btrfs as not stable, please look for the date of them. Some seem to date from 10 years ago. So if you want to give btrfs a chance, you have to look for newer statements. Maybe even look at btrfs.wiki.kernel.org there sure is the best information regarding btrfs


==== experimental ? ====
==== experimental ? ====
Btrfs is feature-rich! And there are some features that are '''not implemented yet'''. Others are only '''partly implemented'''. Some are '''experimental''' and not suggested for production use. As is always the case in Linux-land ''you'' decide what to use, and so you are responsible for your own decisions.
Btrfs is feature-rich! There are new features being implemented and these should be considered experimental for a few releases when the bugs get ironed out when number of brave users help stabilizing it.<small>(from kernel.org)</small>
 
Some features are '''not implemented yet'''. Others are only '''partly implemented'''. Some are '''experimental''' and not suggested for production use. As is always the case in Linux-land ''you'' decide what to use, and so you are responsible for your own decisions.


==== not usable for production ? ====
==== not usable for production ? ====
translator
1,001

edits