translator
987
edits
Difference between revisions of "Btrfs"
restructured
(reordered) |
(restructured) |
||
| Line 53: | Line 53: | ||
When not otherwise specified, additional devices are handled as '''J'''ust a '''B'''unch '''o'''f '''D'''isks (JBOD); this means | When not otherwise specified, additional devices are handled as '''J'''ust a '''B'''unch '''o'''f '''D'''isks (JBOD); this means | ||
{{Info|In most cases it is advisable to use only one Btrfs volume}} | {{Info|In most cases it is advisable to use only one Btrfs volume}} | ||
=== move a volume to another disk === | |||
There are a lot of ways you can move a "normal" filesystem from one disk to another. But there are dangers with moving btrfs volumes that do not exist with other filesystems! '''Don´t ever move a btrfs volume with a tool that does not say it is 100% btrfs-proof.''' | |||
When at any time there are 2 partitions in one computer that have the same filesystem UUID, one ore both filesystems '''may be destroyed'''. Under the topic '''tips''' you will find an easy way to do this without danger | |||
{{BoxDanger|Do NOT| | |||
* make a block-level copy of a Btrfs filesystem to another block device | |||
* use LVM snapshots, or any other kind of block level snapshots | |||
* turn a copy of a filesystem that is stored in a file into a block device with the loopback driver | |||
* try to mount either the original or the copy while both are visible to the same kernel | |||
See why at [https://btrfs.wiki.kernel.org/index.php/Gotchas Block-level copies of devices@btrfs.wiki.kernel.org]}} | |||
== subvolume == | == subvolume == | ||
| Line 86: | Line 96: | ||
= Btrfs RAID = | = Btrfs RAID = | ||