Difference between revisions of "Btrfs"

m
Corrected minor typos
(basis for future extension)
m (Corrected minor typos)
Line 15: Line 15:


=== why not btrfs ? ===
=== why not btrfs ? ===
A lot of people say: "'''I don't use btrfs because''' it is experimental and is '''not stable'''. You can´t use it in production. It is not save!".
A lot of people say: "'''I don't use btrfs because''' it is experimental and is '''not stable'''. You can´t use it in production. It is not safe!".


==== not stable ? ====
==== not stable ? ====
Line 21: Line 21:


==== 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. And as in linux general YOU decide what to use, and so you are responsible for your own decisions.
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.


==== not usable for production ? ====
==== not usable for production ? ====
* Some linux distributions do support btrfs as main file system
* Some Linux distributions do support btrfs as main file system
* Some firms do use btrfs in production@wiki.btrfs.kernel.org
* Some firms do use btrfs in production@wiki.btrfs.kernel.org
* Some manufactorers do deploy devices where btrfs is used inside
* Some manufacturers do deploy devices where btrfs is used inside


==== difficult to repair ? ====
==== difficult to repair ? ====
Moderators, translator
286

edits