NAME<\/a> btrfs-device \u2212 manage devices of btrfs filesystems<\/p>\n btrfs device<\/b> The btrfs device<\/b> command group is used to manage devices of the btrfs filesystems.<\/p>\n Btrfs filesystem can be created on top of single or multiple block devices. Data and metadata are organized in allocation profiles with various redundancy policies. There\u2019s some similarity with traditional RAID levels, but this could be confusing to users familiar with the traditional meaning. Due to the similarity, the RAID terminology is widely used in the documentation. See mkfs.btrfs<\/b>(8) for more details and the exact profile capabilities and constraints.<\/p>\n The device management works on a mounted filesystem. Devices can be added, removed or replaced, by commands provided by btrfs device<\/b> and btrfs replace<\/b>.<\/p>\n The profiles can be also changed, provided there\u2019s enough workspace to do the conversion, using the btrfs balance<\/b> command and namely the filter convert<\/i>.<\/p>\n Type<\/p>\n The block group profile type is the main distinction of the information stored on the block device. User data are called Data<\/i>, the internal data structures managed by filesystem are Metadata<\/i> and System<\/i>.<\/p>\n Profile<\/p>\n A profile describes an allocation policy based on the redundancy\/replication constraints in connection with the number of devices. The profile applies to data and metadata block groups separately. Eg. single<\/i>, RAID1<\/i>.<\/p>\n RAID level<\/p>\n Where applicable, the level refers to a profile that matches constraints of the standard RAID levels. At the moment the supported ones are: RAID0, RAID1, RAID10, RAID5 and RAID6.<\/p>\n See the section TYPICAL USECASES<\/b> for some examples.<\/p>\n add<\/b> [\u2212Kf] Add device(s) to the filesystem identified by If applicable, a whole device discard (TRIM) operation is performed prior to adding the device. A device with existing filesystem detected by blkid<\/b>(8) will prevent device addition and has to be forced. Alternatively the filesystem can be wiped from the device using eg. the wipefs<\/b>(8) tool.<\/p>\n The operation is instant and does not affect existing data. The operation merely adds the device to the filesystem structures and creates some block groups headers.<\/p>\n Options<\/b><\/p>\n \u2212K|\u2212\u2212nodiscard<\/p>\n do not perform discard (TRIM) by default<\/p>\n \u2212f|\u2212\u2212force<\/p>\n force overwrite of existing filesystem on the given disk(s)<\/p>\n \u2212\u2212enqueue<\/p>\n wait if there\u2019s another exclusive operation running, otherwise continue<\/p>\n remove<\/b> [options] Remove device(s) from a filesystem identified by Device removal must satisfy the profile constraints, otherwise the command fails. The filesystem must be converted to profile(s) that would allow the removal. This can typically happen when going down from 2 devices to 1 and using the RAID1 profile. See the TYPICAL USECASES<\/b> section below.<\/p>\n The operation can take long as it needs to move all data from the device.<\/p>\n It is possible to delete the device that was used to mount the filesystem. The device entry in the mount table will be replaced by another device name with the lowest device id.<\/p>\n If the filesystem is mounted in degraded mode (\u2212o degraded), special term missing<\/i> can be used for device<\/i>. In that case, the first device that is described by the filesystem metadata, but not present at the mount time will be removed.<\/p>\n Note<\/big><\/b> Options<\/b><\/p>\n \u2212\u2212enqueue<\/big><\/p>\n wait if there\u2019s another exclusive operation running, otherwise continue<\/big><\/p>\n delete<\/b> Alias of remove kept for backward compatibility<\/big><\/p>\n ready<\/b> Wait until all devices of a multiple\u2212device filesystem are scanned and registered within the kernel module. This is to provide a way for automatic filesystem mounting tools to wait before the mount can start. The device scan is only one of the preconditions and the mount can fail for other reasons. Normal users usually do not need this command and may safely ignore it.<\/big><\/p>\n scan<\/b> [options] [ Scan devices for a btrfs filesystem and register them with the kernel module. This allows mounting multiple\u2212device filesystem by specifying just one from the whole group.<\/big><\/p>\n If no devices are passed, all block devices that blkid reports to contain btrfs are scanned.<\/big><\/p>\n The options \u2212\u2212all\u2212devices<\/i> or \u2212d<\/i> can be used as a fallback in case blkid is not available. If used, behavior is the same as if no devices are passed.<\/big><\/p>\n The command can be run repeatedly. Devices that have been already registered remain as such. Reloading the kernel module will drop this information. There\u2019s an alternative way of mounting multiple\u2212device filesystem without the need for prior scanning. See the mount option device<\/i>.<\/big><\/p>\n Options<\/b><\/big><\/p>\n \u2212d|\u2212\u2212all\u2212devices<\/big><\/p>\n Enumerate and register all devices, use as a fallback in case blkid is not available.<\/big><\/p>\n \u2212u|\u2212\u2212forget<\/big><\/p>\n Unregister a given device or all stale devices if no path is given, the device must be unmounted otherwise it\u2019s an error.<\/big><\/p>\n stats<\/b> [options] Read and print the device IO error statistics for all devices of the given filesystem identified by Options<\/b><\/big><\/p>\n \u2212z|\u2212\u2212reset<\/big><\/p>\n Print the stats and reset the values to zero afterwards.<\/big><\/p>\n \u2212c|\u2212\u2212check<\/big><\/p>\n Check if the stats are all zeros and return 0 if it is so. Set bit 6 of the return code if any of the statistics is no\u2212zero. The error values is 65 if reading stats from at least one device failed, otherwise it\u2019s 64.<\/big><\/p>\n usage<\/b> [options] Show detailed information about internal allocations on devices.<\/big><\/p>\n The level of detail can differ if the command is run under a regular or the root user (due to use of restricted ioctls). The first example below is for normal user (warning included) and the next one with root on the same filesystem:<\/big><\/p>\n WARNING: cannot read detailed chunk info, per\u2212device usage will not be shown, run as root \/dev\/sdc1, ID: 1 \u2022 Device size<\/i> \u2014 size of the device as seen by the filesystem (may be different than actual device size)<\/big><\/p>\n \u2022 Device slack<\/i> \u2014 portion of device not used by the filesystem but still available in the physical space provided by the device, eg. after a device shrink<\/big><\/p>\n \u2022 Data,single<\/i>, Metadata,single<\/i>, System,single<\/i> \u2014 in general, list of block group type (Data, Metadata, System) and profile (single, RAID1, …) allocated on the device<\/big><\/p>\n \u2022 Data,RAID0\/3<\/i> \u2014 in particular, striped profiles RAID0\/RAID10\/RAID5\/RAID6 with the number of devices on which the stripes are allocated, multiple occurences of the same profile can appear in case a new device has been added and all new available stripes have been used for writes<\/big><\/p>\n \u2022 Unallocated<\/i> \u2014 remaining space that the filesystem can still use for new block groups<\/big><\/p>\n Options<\/b><\/big><\/p>\n \u2212b|\u2212\u2212raw<\/big><\/p>\n raw numbers in bytes, without the B<\/i> suffix<\/big><\/p>\n \u2212h|\u2212\u2212human\u2212readable<\/big><\/p>\n print human friendly numbers, base 1024, this is the default<\/big><\/p>\n \u2212H<\/big><\/p>\n print human friendly numbers, base 1000<\/big><\/p>\n \u2212\u2212iec<\/big><\/p>\n select the 1024 base for the following options, according to the IEC standard<\/big><\/p>\n \u2212\u2212si<\/big><\/p>\n select the 1000 base for the following options, according to the SI standard<\/big><\/p>\n \u2212k|\u2212\u2212kbytes<\/big><\/p>\n show sizes in KiB, or kB with \u2212\u2212si<\/big><\/p>\n \u2212m|\u2212\u2212mbytes<\/big><\/p>\n show sizes in MiB, or MB with \u2212\u2212si<\/big><\/p>\n \u2212g|\u2212\u2212gbytes<\/big><\/p>\n show sizes in GiB, or GB with \u2212\u2212si<\/big><\/p>\n \u2212t|\u2212\u2212tbytes<\/big><\/p>\n show sizes in TiB, or TB with \u2212\u2212si<\/big><\/p>\n If conflicting options are passed, the last one takes precedence.<\/big><\/p>\n STARTING WITH A SINGLE\u2212DEVICE FILESYSTEM<\/b> The amount of data stored is 16GiB, metadata have allocated 2GiB.<\/big><\/p>\n ADD NEW DEVICE<\/big><\/b><\/big><\/p>\n We want to increase the total size of the filesystem and keep the profiles. The size of the new device \/dev\/sdb<\/i> is 100GiB.<\/big><\/p>\n $ btrfs device add \/dev\/sdb \/mnt<\/big><\/p>\n The amount of free data space increases by less than 100GiB, some space is allocated for metadata.<\/big><\/p>\n CONVERT TO RAID1<\/big><\/b><\/big><\/p>\n Now we want to increase the redundancy level of both data and metadata, but we\u2019ll do that in steps. Note, that the device sizes are not equal and we\u2019ll use that to show the capabilities of split data\/metadata and independent profiles.<\/big><\/p>\n The constraint for RAID1 gives us at most 50GiB of usable space and exactly 2 copies will be stored on the devices.<\/big><\/p>\n First we\u2019ll convert the metadata. As the metadata occupy less than 50GiB and there\u2019s enough workspace for the conversion process, we can do:<\/big><\/p>\n $ btrfs balance start \u2212mconvert=raid1 \/mnt<\/big><\/p>\n This operation can take a while, because all metadata have to be moved and all block pointers updated. Depending on the physical locations of the old and new blocks, the disk seeking is the key factor affecting performance.<\/big><\/p>\n You\u2019ll note that the system block group has been also converted to RAID1, this normally happens as the system block group also holds metadata (the physical to logical mappings).<\/big><\/p>\n What changed:<\/big><\/p>\n \u2022 available data space decreased by 3GiB, usable roughly (50 \u2212 3) + (100 \u2212 3) = 144 GiB<\/big><\/p>\n \u2022 metadata redundancy increased<\/big><\/p>\n IOW, the unequal device sizes allow for combined space for data yet improved redundancy for metadata. If we decide to increase redundancy of data as well, we\u2019re going to lose 50GiB of the second device for obvious reasons.<\/big><\/p>\n $ btrfs balance start \u2212dconvert=raid1 \/mnt<\/big><\/p>\n The balance process needs some workspace (ie. a free device space without any data or metadata block groups) so the command could fail if there\u2019s too much data or the block groups occupy the whole first device.<\/big><\/p>\n The device size of \/dev\/sdb<\/i> as seen by the filesystem remains unchanged, but the logical space from 50\u2212100GiB will be unused.<\/big><\/p>\n REMOVE DEVICE<\/big><\/b><\/big><\/p>\n Device removal must satisfy the profile constraints, otherwise the command fails. For example:<\/big><\/p>\n $ btrfs device remove \/dev\/sda \/mnt In order to remove a device, you need to convert the profile in this case:<\/big><\/p>\n $ btrfs balance start \u2212mconvert=dup \u2212dconvert=single \/mnt The device stats keep persistent record of several error classes related to doing IO. The current values are printed at mount time and updated during filesystem lifetime or from a scrub run.<\/big><\/p>\n $ btrfs device stats \/dev\/sda3 write_io_errs<\/big><\/p>\n Failed writes to the block devices, means that the layers beneath the filesystem were not able to satisfy the write request.<\/big><\/p>\n read_io_errors<\/big><\/p>\n Read request analogy to write_io_errs.<\/big><\/p>\n flush_io_errs<\/big><\/p>\n Number of failed writes with the FLUSH<\/i> flag set. The flushing is a method of forcing a particular order between write requests and is crucial for implementing crash consistency. In case of btrfs, all the metadata blocks must be permanently stored on the block device before the superblock is written.<\/big><\/p>\n corruption_errs<\/big><\/p>\n A block checksum mismatched or a corrupted metadata header was found.<\/big><\/p>\n generation_errs<\/big><\/p>\n The block generation does not match the expected value (eg. stored in the parent node).<\/big><\/p>\n Since kernel 5.14 the device stats are also available in textual form in \/sys\/fs\/btrfs\/FSID\/devinfo\/DEVID\/error_stats<\/i>.<\/big><\/p>\n btrfs device<\/b> returns a zero exit status if it succeeds. Non zero is returned in case of failure.<\/big><\/p>\n If the \u2212s<\/i> option is used, btrfs device stats<\/b> will add 64 to the exit status if any of the error counters is non\u2212zero.<\/big><\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
DEVICE MANAGEMENT<\/a>
SUBCOMMAND<\/a>
TYPICAL USECASES<\/a>
DEVICE STATS<\/a>
EXIT STATUS<\/a>
AVAILABILITY<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
DEVICE MANAGEMENT <\/a> <\/h2>\n
SUBCOMMAND <\/a> <\/h2>\n
In most cases, there is only one missing device in degraded mode, otherwise mount fails. If there are two or more devices missing (e.g. possible in RAID6), you need specify missing<\/i> as many times as the number of missing devices to remove all of them.<\/p>\n
\/dev\/sdc1, ID: 1
Device size: 931.51GiB
Device slack: 0.00B
Unallocated: 931.51GiB<\/big><\/p>\n
Device size: 931.51GiB
Device slack: 0.00B
Data,single: 641.00GiB
Data,RAID0\/3: 1.00GiB
Metadata,single: 19.00GiB
System,single: 32.00MiB
Unallocated: 271.48GiB<\/big><\/p>\nTYPICAL USECASES <\/a> <\/h2>\n
Assume we\u2019ve created a filesystem on a block device \/dev\/sda<\/i> with profile single\/single<\/i> (data\/metadata), the device size is 50GiB and we\u2019ve used the whole device for the filesystem. The mount point is \/mnt<\/i>.<\/big><\/p>\n
ERROR: error removing device ‘\/dev\/sda’: unable to go below two devices on raid1<\/big><\/p>\n
$ btrfs device remove \/dev\/sda \/mnt<\/big><\/p>\nDEVICE STATS <\/a> <\/h2>\n
[\/dev\/sda3].write_io_errs 0
[\/dev\/sda3].read_io_errs 0
[\/dev\/sda3].flush_io_errs 0
[\/dev\/sda3].corruption_errs 0
[\/dev\/sda3].generation_errs 0<\/big><\/p>\nEXIT STATUS <\/a> <\/h2>\n
AVAILABILITY <\/a> <\/h2>\n