The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Btrfs/zh-cn
BTRFS 是一个基于写时复制 (COW) 原则的文件系统，最初是在 Oracle 公司设计的，用于 Linux。Btrfs 的开发始于 2007 年，自 2014 年 8 月起，该文件系统的磁盘格式被标记为稳定。
2015 年，Btrfs 被采纳为 SUSE Linux Enterprise Server 12 的默认文件系统。在 RedHat 宣布停止支持 Btrfs 后，SUSE 于 2017 年重申了对 Btrfs 的承诺。
Btrfs 旨在解决 Linux 文件系统中缺乏文件池、快照、校验和以及集成多设备跨度的问题。
设置和使用 BTRFS 非常简单。在这个简单的介绍中，我们将使用现有的 debian-sources 或 debian-sources-lts 内核在 Funtoo Linux 下设置 BTRFS，比如 Funtoo Linux 为你预置的内核，我们还将使用我们的 BTRFS 存储池来存储不属于 Funtoo Linux 安装本身的数据。Funtoo Linux 将从一个非 BTRFS 文件系统启动，作为初始化过程的一部分，将初始化我们的 BTRFS 存储，并将其挂载在我们选择的位置。
安装
安装 BTRFS 不需要任何额外的步骤，因为它是 Linux 内核的一部分（从 2.6.29 开始在主线 Linux 内核中）。让我们用 emerge 安装 BTRFS 用户空间工具 (btrfs-progs)。
root # emerge btrfs-progs
BTRFS 现在可以使用了。
BTRFS 概念
BTRFS 可以用来管理它使用的物理磁盘，物理磁盘被添加到 BTRFS 卷中。然后，BTRFS 可以从卷中创建子卷，子卷上可以存储文件。
与传统的 Linux 文件系统不同，BTRFS 文件系统将从底层卷按需分配存储空间。
在 BTRFS 的世界里，卷这个词对应的是一个存储池 (ZFS) 或一个卷组 (LVM)。
- 设备 - 一个或多个底层物理卷。
- 卷 - 一个大型存储池，由设备的所有空间组成，可支持不同的冗余级别。
- 子卷 - 这些是被挂载的部分，你可以在其中存储文件。
- 快照 - 子卷在某个时间点的只读副本和/或子卷在某个时间点的读写副本（也就是克隆）。
创建一个卷
要创建一个基本的 BTRFS 卷，将需要一个额外的空盘。执行以下步骤：
root # mkfs.btrfs /dev/sdxy btrfs-progs v4.17.1 See http://btrfs.wiki.kernel.org for more information. Detected a SSD, turning off metadata duplication. Mkfs with -m dup if you want to force metadata duplication. Performing full device TRIM /dev/sdj (223.57GiB) ... Label: (null) UUID: d6bcba6e-8fd5-41fc-9bb4-79628c5c928c Node size: 16384 Sector size: 4096 Filesystem size: 223.57GiB Block group profiles: Data: single 8.00MiB Metadata: single 8.00MiB System: single 4.00MiB SSD detected: yes Incompat features: extref, skinny-metadata Number of devices: 1 Devices: ID SIZE PATH 1 223.57GiB /dev/sdxy
/dev/sdxy 应该是一个未使用的磁盘。如果这个磁盘上有任何已存在的数据，可能需要使用以下命令：
root # mkfs.btrfs -f /dev/sdxy
现在可以像挂载其他 linux 文件系统一样挂载所创建的卷。
root # mkdir /mnt/btrfs-top-level root # mount /dev/sdxy /mnt/btrfs-top-level root # mount ... /dev/sdxy on /mnt/btrfs-top-level type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
It is recommended that nothing is stored directly on this top-level volume (ID 5) root directory.
Creating Subvolumes
Btrfs has a concept of subvolumes. Subvolume is an independently mountable POSIX filetree (but not a block device). There are several basic schemas to layout subvolumes (including snapshots) as well as mixtures thereof.
Lets create children of the top level subvolume (ID 5). We will have:
@data- it will serve as mountable/data.snapshots- here snapshots will be stored
root # cd /mnt/btrfs-top-level root # btrfs subvolume create @data root # btrfs subvolume create .snapshots root # btrfs subvolume list /mnt/btrfs-top-level ID 256 gen 322338 top level 5 path @data ID 257 gen 322275 top level 5 path .snapshots
The default Subvolume
Changing the default subvolume with btrfs subvolume default will make the top level of the filesystem accessible only when subvol or subvolid mount options are specified
When btrfs block device is mounted without specifying a subvolume the default one is used. To check default subvolume run
root # btrfs subvolume get-default /mnt/btrfs-top-level ID 5 (FS_TREE)
For the convenience lets make @data subvolume as the default one. It's good to double check the subvolume ID first. Either btrfs subvolume list or btrfs subvolume show can be used for that
root # btrfs subvolume show /mnt/btrfs-top-level/@data ... Subvolume ID: 256
Now you can make this subvolume as a default one
root # btrfs subvolume set-default 256 /mnt/btrfs-top-level root # btrfs subvolume get-default /mnt/btrfs-top-level ID 256 gen 322336 top level 5 path @data
At this point you can stop working on the top level subvolume (ID 5) and instead mount directly @data subvolume.
root # cd /mnt root # umount /mnt/btrfs-top-level root # mkdir /data root # mount /dev/sdxy /data
Nested Subvolumes
Nested subvolumes are not going to be a part of snapshots created from their parent subvolume. So one typical reason is to exclude certain parts of the filesystem from being snapshot.
Lets create a separate nested subvolume for /data/independent.
root # btrfs subvolume create /data/independent root # btrfs subvolume list /data ID 258 gen 161 top level 256 path independent
Usually you will want to "split" areas which are "complete" and/or "consistent" in themselves. Examples for this more-fine grained partitioning could be /var/log, /var/www or /var/lib/postgresql.
/etc/fstab
To automatically mount the @data subvolume after reboot you need to modify /etc/fstab
/etc/fstab - fstab for btrfs/dev/sdxy /data btrfs subvolid=256,defaults 0 0
According to btrfs docs most mount options apply to the whole filesystem and only options in the first mounted subvolume will take effect. This means that (for example) you can't set per-subvolume nodatacow, nodatasum, or compress.
Now lets verify if this changes were correct
root # cd / root # umount /data root # mount /data root # ls /data independent
Did you just notice that although we mounted our @data subvolume the nested subvolume @data/independent is also present?
Snapshots
For the purpose of checking out this cool btrfs feature lets populate our filesystem with some example data first
root # echo 'btrfs' > /data/foo.txt root # echo 'fun' > /data/independent/bar.txt
As you probably remember on the top level (next to @data subvolume) you've also created the .snapshots subvolume. You can mount it now to create some snapshots
root # mkdir /mnt/snapshots root # mount /dev/sdxy /mnt/snapshots -o subvolid=257
A snapshot is a subvolume like any other, with given initial content. By default, snapshots are created read-write. File modifications in a snapshot do not affect the files in the original subvolume. Lets create a read-write snapshot for /data and read-only snapshot for /data/independent
root # btrfs subvolume snapshot /data /mnt/snapshots/data_$(date -u -Iseconds) Create a snapshot of '/data' in '/mnt/snapshots/data_2022-08-30T22:04:57+00:00' root # btrfs subvolume snapshot -r /data/independent /mnt/snapshots/independent_$(date -u -Iseconds) Create a readonly snapshot of '/data/independent' in '/mnt/snapshots/independent_2022-08-30T22:05:29+00:00'
Once again, nested subvolumes are not going to be a part of snapshots created from their parent subvolume. So you shouldn't be surprised when you compare the contents of the /data vs the contents of the /mnt/snapshots
root # tree /data /data ├── foo.txt └── independent └── bar.txt root # tree /mnt/snapshots /mnt/snapshots ├── data_2022-08-30T22:04:57+00:00 │ └── foo.txt └── independent_2022-08-30T22:05:29+00:00 └── bar.txt
At this point you might be interested in send and receive btrfs features.
According to btrfs docs a snapshot is not a backup: snapshots work by use of BTRFS copy-on-write behaviour. A snapshot and the original it was taken from initially share all of the same data blocks. If that data is damaged in some way (cosmic rays, bad disk sector, accident with dd to the disk), then the snapshot and the original will both be damaged.
Wrap up
It is recommended to run btrfs scrub once in a while. E.g. every month
Scrub is the online check and repair functionality that verifies the integrity of data and metadata, assuming the tree structure is fine. You can run it on a mounted file system; it runs as a background process during normal operation.
To start a (background) scrub on the filesystem which contains /data run
root # btrfs scrub start /data scrub started on /data, fsid 40f8b94f-07ee-4f7e-beb1-8e686abc246d (pid=5525)
To check the status of a running scrub
root # btrfs scrub status /data UUID: 40f8b94f-07ee-4f7e-beb1-8e686abc246d Scrub started: Tue Aug 30 00:38:54 2022 Status: running Duration: 0:00:15 Time left: 0:00:34 ETA: Tue Aug 30 00:39:44 2022 Total to scrub: 149.06GiB Bytes scrubbed: 44.79GiB (30.04%) Rate: 2.99GiB/s Error summary: no errors found
你现在应该已经到了可以开始使用 BTRFS 来完成各种任务的阶段。虽然 BTRFS 的内容比这篇简短的介绍要多得多，但你现在应该对 BTRFS 的基本概念有了很好的理解。