From Gentoo Wiki
Jump to: navigation, search
This page is a translated version of the page Btrfs and the translation is 0% complete.

Other languages:
English • ‎español • ‎français • ‎italiano • ‎polski • ‎русский • ‎中文(中国大陆)‎ • ‎日本語 • ‎한국어

Btrfs is a copy-on-write (CoW) filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance, repair, and easy administration. Jointly developed at Oracle, Red Hat, Fujitsu, Intel, SUSE, STRATO, and many others, btrfs is licensed under the GPL and open for contribution from anyone.


Ext4 is safe and stable and can handle large filesystems with extents, but why switch? While it is true that Btrfs is still considered experimental and is growing in stability, the time when Btrfs will become the default filesystem for Linux systems is getting closer. Some Linux distributions have already begun to switch to it with their current releases. Btrfs has a number of advanced features in common with ZFS, which is what made the ZFS filesystem popular with BSD distributions and NAS devices.

  • Copy on Write (CoW) and snapshotting - Make incremental backups painless even from a "hot" filesystem or virtual machine (VM).
  • File level checksums - Metadata for each file includes a checksum that is used to detect and repair errors.
  • Compression - Files may be compressed and decompressed on the fly, which speeds up read performance.
  • Auto defragmentation - The filesystems are tuned by a background thread while they are in use.
  • Subvolumes - Filesystems can share a single pool of space instead of being put into their own partitions.
  • RAID - Btrfs does its own RAID implementations so LVM or mdadm are not required in to have RAID. Currently RAID 0 and 1 are supported; RAID 5 and 6 are upcoming.
  • Partitions are optional - While Btrfs can work with partitions, it has the potential to use raw devices (/dev/<device>) directly.
  • Data deduplication - There is limited data deduplication support; however, deduplication will eventually become a standard feature in Btrfs. This enables Btrfs to save space by comparing files via binary diffs.
For an up-to-date and somewhat exhaustive listing of features see the upstream wiki's status page. Not all features are sufficiently mature for wide use though.

Down the road, new clustered filesystems will readily take advantage of Btrfs with its copy on write and other advanced features for their object stores. Ceph is one example of a clustered filesystem that looks very promising, and can take advantage of Btrfs.



Activez les options suivantes du noyau pour activer la prise en charge de Btrfs :

KERNEL Activate Btrfs in the kernel
File systems  --->
    <*> Btrfs filesystem


Le paquet sys-fs/btrfs-progs contient les utilitaires nécessaire au fonctionnent de Btrfs.

root #emerge --ask sys-fs/btrfs-progs


Typing long Btrfs commands can quickly become a hassle. Each command (besides the initial btrfs command) can be reduced to a very short set of instructions. This method is helpful when working from the command line to reduce the amount of characters typed.

Par exemple, pour défragmenter un système de fichiers situé à / (ci-dessous la commande longue) :

root #btrfs filesystem defragment -v /

Shorten each of the longer commands after the btrfs command by reducing them to their unique, shortest prefix. In this context, unique means that no other btrfs commands will match the command at the command's shortest length. The shortened version of the above command is:

root #btrfs fi de -v /

No other btrfs commands start with fi; filesystem is the only one. The same goes for the de sub-command under the filesystem command.


La commande mkfs.btrfs détruit de façon irréversible tout le contenu de la partition qui est désignée pour être formater. Soyez sûr que le disque et la partition sélectionnés sont correctes avant de lancer n'importe quelle {commande {c

Pour créer un système de fichiers sur la partition /dev/sdXN :

root #mkfs.btrfs /dev/sdXN

Dans l'exemple suivant, remplacez N par le numéro de partition et X par la lettre correspondant au disque qui va être formaté. Par exemple, pour formater la troisième partition du premier disque en Btrfs, lancez :

root #mkfs.btrfs /dev/sda3
La dernière colonne dans /etc/fstab devrait être 0 pour toutes les partitions Btrfs. fsck.btrfs et btrfsck ne devraient pas être lancés au démarrage.


Après création, les systèmes de fichiers peuvent être montés de différentes manières :

  • mount - Montage manuel.
  • fstab - Définir des points de montage dans /etc/fstab activant un montage automatique à chaque démarrage.
  • Removable media - Montages automatiques à la demande (utile pour les périphériques USB).
  • AutoFS - Montage automatique à l'accès au système de fichiers.

Conversion de systèmes de fichiers basés sur ext*

Il est possible de convertir des systèmes de fichiers ext2, ext3, et ext4 en Btrfs en utilisant l'utilitaire btrfs-convert.

The following instructions only supports the conversion of filesystems that are unmounted. To convert the root partition, boot to a system rescue disk (SystemRescueCD works nicely) and run on the conversion commands on the root partition.

Premièrement, soyez sûr que le point de montage est bien démonté :

root #umount <périphérique_monté>

Vérifiez l'intégrité du système de fichier en utilisant l'outil adéquat fsck. Dans l'exemple suivant, le système de fichier est du ext4 :

root #fsck.ext4 -f <périphérique_monté>

Utilisez btrfs-convert pour convertir un périphérique formaté en ext*, en Btrfs :

root #btrfs-convert <périphérique_monté>

Assurez-vous d'éditer /etc/fstab après que le périphérique est été formaté, en changeant la colonne correspondant au système de fichiers utilisé, d'ext4 en Btrfs :

FILE /etc/fstabChangement d'ext4 en Btrfs
<périphérique>   <point_de_montage>  btrfs  defaults  0 0


Une autre fonctionnalité du Btrfs est la défragmentation en ligne. Pour défragmenter un système de fichiers racine en Btrfs, lancez :

root #btrfs filesystem defragment -r -v /
Defragmenting with kernel versions < 3.9 or ≥ 3.14-rc2 as well as with Linux stable kernel versions ≥ 3.10.31, ≥ 3.12.12 or ≥ 3.13.4 breaks up ref-links between files and their COW copies[1] and thus may increase space usage considerably. Make sure to have enough free space available and not too many snapshots on the drive as full btrfs partitions can get really slow.


Btrfs supporte la compression transparente : trois alghorithmes de compression sont disponibles zlib, lzo, et zstd[2].

Il est possible de compresser des fichiers spécifiques, en utilisant l'attribut suivant :

user $chattr +c

L'option de montage compress spécifie le comportement à suivre lors de la création de tous nouveaux fichiers. Pour recompresser tous le système de fichiers, lancer la commande suivante :

root #btrfs filesystem defragment -r -v -clzo /

Depending on the CPU and disk performance, using lzo compression could improve the overall throughput.

Il est possible d'utiliser la compression avec l'algorithme zlib plutôt que lzo. zlib est plus lent mais a un ratio de compression supérieur :

root #btrfs filesystem defragment -r -v -czlib /

Niveau de compression

Depuis la version 4.15.0 du noyau[3], la compression utilisant zlib peut maintenant utiliser différents niveaux de compression, allant de 1 à 9. Par exemple, pour utiliser le niveau de compression maximum au montage :

root #mount -o compress=zlib:9 /dev/sdXY /chemin/vers/point_de_montage

Ou pour utiliser le niveau de compression minimal :

root #mount -o compress=zlib:1 /dev/sdXY /chemin/vers/point_de_montage

Ou ajuster la compression au remontage :

root #mount -o remount,compress=zlib:3 /chemin/vers/point_de_montage

The compression level should be visible in /proc/mounts or by checking the most recent output of dmesg |grep -i btrfs.

root #dmesg |grep -i btrfs
[    0.495284] Btrfs loaded, crc32c=crc32c-intel
[ 3010.727383] BTRFS: device label My Passport devid 1 transid 31 /dev/sdd1
[ 3111.930960] BTRFS info (device sdd1): disk space caching is enabled
[ 3111.930973] BTRFS info (device sdd1): has skinny extents
[ 9428.918325] BTRFS info (device sdd1): use zlib compression, level 3

Ratio de compression et usage du disque

The usual userspace tools for determining used and free space like du and df may provide inaccurate results on a Btrfs partition due to inherent design differences in the way files are written compared to, for example, ext2/3/4[4].

It is therefore advised to use the du/df alternatives provided by the btrfs userspace tool btrfs filesystem. In Addition to that, The compsize tool found from the sys-fs/compsize package can be helpful in providing additional information regarding compression ratios and the disk usage of compressed files. The following are example uses of these tools for a btrfs partition mounted under /media/drive.

user $btrfs filesystem du -s /media/drive
     Total   Exclusive  Set shared  Filename
 848.12GiB   848.12GiB       0.00B  /media/drive/
user $btrfs filesystem df /media/drive
Data, single: total=846.00GiB, used=845.61GiB
System, DUP: total=8.00MiB, used=112.00KiB
Metadata, DUP: total=2.00GiB, used=904.30MiB
GlobalReserve, single: total=512.00MiB, used=0.00B
user $compsize /media/drive
Processed 2262 files, 112115 regular extents (112115 refs), 174 inline.
Type       Perc     Disk Usage   Uncompressed Referenced  
TOTAL       99%      845G         848G         848G       
none       100%      844G         844G         844G       
zlib        16%      532M         3.2G         3.2G 

Périphériques multiples (RAID)

Btrfs can be used with multiple devices in order to create RAIDs. Using Btrfs to create filesystems that span multiple devices is much easier than creating using mdadm; there is no initialization time needed for creation.

The simplest method is to use the entirety of the unpartitioned block device to create a filesystem that spans multiple devices. For example, to create a filesystem in RAID1 mode across two devices:

root #mkfs.btrfs -m raid1 <périphérique1> <périphérique2> -d raid1 <périphérique1> <périphérique2>

Converting between RAID modes is possible with the balance sub-command. For example, say a multiple device RAID 1 is mounted at /srv. It is possible to convert this RAID1 to RAID0 with using the following command:

root #btrfs balance start -dconvert=raid0 -mconvert=raid0 --force /srv

RAID mode conversion can be performed while the filesystem is online and in use. Possible RAID modes in btrfs include RAID0, RAID1, RAID5, RAID6, and RAID10. See the upstream BTRFS wiki for more information.

It is currently not safe to use the RAID 5 or 6 modes[5]. RAID 5 and 6 modes have seen some fixes[6] in Linux 4.12, but overall status is still marked as unstable.[7][8]. Users who want to use RAID5 or RAID6 functionality of btrfs are encouraged to check the btrfs status page for stability status of said modes before utilizing the modes.


As mentioned above in the features list, Btrfs can create subvolumes. Subvolumes can be used to better organize and manage data. They become especially powerful when combined with snapshots. Important distinctions must be made between Btrfs subvolumes and subvolumes created by Logical Volume Management (LVM). Btrfs subvolumes are not block level devices, they are POSIX file namespaces.[9] They can be created at any location in the filesystem and will act like any other directory on the system with one caveat: subvolumes can be mounted and unmounted. Subvolumes are nestable (subvolumes can be created inside other subvolumes), and easily created or removed.

A subvolume cannot be created across different Btrfs filesystems. If /dev/sda and /dev/sdb both contain separate (non-RAID) Btrfs filesystems, there is no way a subvolume can expand across the two filesystems. The snapshot can be moved from one filesystem to another, but it cannot span across the two. It must be on /dev/sda or /dev/sdb.


To create a subvolume, issue the following command inside a Btrfs filesystem's name space:

root #btrfs subvolume create <destination>

Replace <dest-name> with the desired destination and subvolume name. For example, if a Btrfs filesystem exists at /mnt/btrfs, a subvolume could be created inside it using the following command:

root #btrfs subvolume create /mnt/btrfs/sousvolume1


To see the subvolume(s) that have been created, use the subvolume list command followed by a Btrfs filesystem location. If the current directory is somewhere inside a Btrfs filesystem, the following command will display the subvolume(s) that exist on the filesystem:

root #btrfs subvolume list .

If a Btrfs filesystem with subvolumes exists at the mount point created in the example command above, the output from the list command will look similar to the following:

root #btrfs subvolume list /mnt/btrfs
ID 309 gen 102913 top level 5 path mnt/btrfs/sousvolume1


Les sous-volumes peuvent être proprement supprimés grâce à la commande subvolume delete suivie du chemin vers le sous-volume. Tous les chemins des sous-volume disponibles peuvent être obtenus en utilisant la commande de listage ci-dessus.

root #btrfs subvolume delete <chemin>

As above, replace <subvolume-path> with the actual path to the subvolume to be removed. To delete the subvolume used in the examples above, the following command would be issued:

root #btrfs subvolume delete /mnt/btrfs/sousvolume1
Delete subvolume (no-commit): '/mnt/btrfs/sousvolume1'


Snapshots are subvolumes that share data and metadata with other subvolumes. This is made possible by Btrfs' Copy on Write (CoW) ability.[9] Snapshots can be used for several purposes, one of which is to create backups of file system structures at specific points in time.

Si la racine est en Btrfs, il est possible de créer un instantané en utilisant les commandes subvolume snapshot :

root #mkdir -p /mnt/backup/rootfs
root #btrfs subvolume snapshot / /mnt/backup/rootfs/

The following small shell script can be added to a timed cron job to create a timestamped snapshot backup of a Btrfs formatted root filesystem. The timestamps can be adjusted to whatever is preferred by the user.

FILE btrfs_instantane.shBtrfs rootfs instantané exemple de travail cron

NOW=$(date +"%Y-%m-%d_%H:%M:%S")
if [ ! -e /mnt/backup ]; then
    mkdir -p /mnt/backup
cd /
btrfs subvolume snapshot / "/mnt/backup/backup_${NOW}"


A subvolume can be mounted in a location different from where it was created, or users can choose to not mount them at all. For example, a user could create a Btrfs filesystem in /mnt/btrfs and create /mnt/btrfs/home and /mnt/btrfs/portage subvolumes. The subvolumes could then be mounted at /home and /usr/portage, with the original top level subvolume left unmounted. This results in a configuration where the subvolumes' relative path from the top level subvolume is different from their actual path.

To mount a subvolume, perform the following command, where <rel-path> is the relative path of the subvolume from the top level subvolume, obtainable through the subvolume list command:

root #mount -o subvol=<chemin relatif> <périphérique> <point de montage>

Similarly, one can update the filesystem tab to mount their Btrfs subvolumes like so:

FILE /etc/fstabMounting Subvolumes
<device>  <mountpoint>  btrfs  subvol=<rel-path>  0 2


Using with VM disk images

When using Btrfs with virtual machine disk images, it is best to disable copy-on-write on the disk images in order to speed up IO performance. This can only be performed on files that are newly created. It also possible to disable CoW on all files created within a certain directory. For example, using the chattr command:

root #chattr +C /var/lib/libvirt/images

Clear the free space cache

It is possible to clear Btrfs' free space cache by mounting the filesystem with the clear_cache mount option. For example:

root #mount -o clear_cache /chemin/vers/périphérique /chemin/vers/point_de_montage

Btrfs hogging memory (disk cache)

When utilizing some of Btrfs' special abilities (like making many --reflink copies or creating a crazy amount of snapshots), lot of memory can be eaten and not freed fast enough by the kernel's inode cache. This issue can go undiscovered since memory dedicated to the disk cache might not be clearly visible in traditional system monitoring utilities. The slabtop utility (available as part of the sys-process/procps package) was specifically created to determine how much memory kernel objects are consuming:

root #slabtop
Active / Total Objects (% used)    : 2259363 / 2338091 (96.6%)
Active / Total Slabs (% used)      : 467797 / 467803 (100.0%)
Active / Total Caches (% used)     : 83 / 175 (47.4%)
Active / Total Size (% used)       : 1489775.62K / 1512200.52K (98.5%)
Minimum / Average / Maximum Object : 0.02K / 0.65K / 4096.00K

1034532 1032386  99%    1.04K 344844        3   1379376K btrfs_inode

If the inode cache is consuming too much memory, the kernel can be manually instructed to drop the cache by echoing an integer value to the /proc/sys/vm/drop_caches file[10].

To be safe, and to help the kernel determine the maximum amount of freeable memory, be sure to run a sync before running the echo commands below:

user $sync

Most of the time Btrfs users will probably want to echo 2 to reclaim just the slab objects (dentries and btrfs_inodes):

root #echo 2 > /proc/sys/vm/drop_caches

To clear the entire disk cache (slab objects and the page cache) use echo 3 instead:

root #echo 3 > /proc/sys/vm/drop_caches
While the above commands are non-destructive (as long as a sync was completed before running them), they could seriously but temporarily slow down the system while the kernel loads only the necessary items back into memory. Think twice before running the above commands for systems under heavy load!

More information on kernel slabs can be found in this dedoimedo blog entry.

Mounting Btrfs fails, returning mount: unknown filesystem type 'btrfs'

The original solution by Tim on Stack Exchange inspired the following solution: build the kernel manually instead of using genkernel:

#cd /usr/src/linux
#make menuconfig
#make && make modules_install
#cp arch/x86_64/boot/bzImage /boot
#mv /boot/bzImage /boot/votre_noyau
#genkernel --install initramfs

La racine Btrfs ne démarre pas

Genkernel's initramfs as created with the command below doesn't load btrfs:

root #genkernel --btrfs initramfs

Compilez le support de Btrfs dans le noyau plutôt que comme un module, ou utilisez genkernel-next ou Dracut pour générer l'initramfs.

Voir aussi

  • Btrfs snapshots - Un script qui crée des instantanés au changement de fichiers
  • Btrfs/System Root Guide - Utiliser Btrfs comme une collection de sous-volume dont un racine.
  • Btrfs native system root guide - Un guide alternatif sur l'utilisation d'un sous-volume Btrfs comme la racine du système.
  • ext4 - Le système de fichiers par défaut sur la plupart des distributions.
  • Samba shadow copies - Using Samba to expose Shadow Copies as 'Previous Versions' to Windows clients.
  • Snapper - Un programme en ligne de commande s'occupant de gérer des instantanés Btrfs.
  • ZFS - Un système de fichier qui partage de nombreux points communs avec le Btrfs, mais a des problème de licence.

Ressources externes