Debian Codegraph @

upstream/debian-trixie/man8/btrfs-balance.8

raw
1 .\" Man page generated from reStructuredText.
2 .
3 .
4 .nr rst2man-indent-level 0
5 .
6 .de1 rstReportMargin
7 \\$1 \\n[an-margin]
8 level \\n[rst2man-indent-level]
9 level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
10 -
11 \\n[rst2man-indent0]
12 \\n[rst2man-indent1]
13 \\n[rst2man-indent2]
14 ..
15 .de1 INDENT
16 .\" .rstReportMargin pre:
17 . RS \\$1
18 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
19 . nr rst2man-indent-level +1
20 .\" .rstReportMargin post:
21 ..
22 .de UNINDENT
23 . RE
24 .\" indent \\n[an-margin]
25 .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
26 .nr rst2man-indent-level -1
27 .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
28 .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
29 ..
30 .TH "BTRFS-BALANCE" "8" "May 18, 2026" "7.0" "BTRFS"
31 .SH NAME
32 btrfs-balance \- balance block groups on a btrfs filesystem
33 .SH SYNOPSIS
34 .sp
35 \fBbtrfs balance\fP <subcommand> <args>
36 .SH DESCRIPTION
37 .sp
38 The primary purpose of the balance feature is to spread block groups across
39 all devices so they match constraints defined by the respective profiles. See
40 \fI\%mkfs.btrfs(8)\fP section \fI\%PROFILES\fP
41 for more details.
42 The scope of the balancing process can be further tuned by use of filters that
43 can select the block groups to process. Balance works only on a mounted
44 filesystem. Extent sharing is preserved and reflinks are not broken.
45 Files are not defragmented nor recompressed, file extents are preserved
46 but the physical location on devices will change.
47 .sp
48 The balance operation is cancellable by the user. The on\-disk state of the
49 filesystem is always consistent so an unexpected interruption (e.g. system crash,
50 reboot) does not corrupt the filesystem. The progress of the balance operation
51 is temporarily stored as an internal state and will be resumed upon mount,
52 unless the mount option \fIskip_balance\fP is specified.
53 .sp
54 \fBWARNING:\fP
55 .INDENT 0.0
56 .INDENT 3.5
57 Running balance without filters will take a lot of time as it basically move
58 data/metadata from the whole filesystem and needs to update all block
59 pointers.
60 .UNINDENT
61 .UNINDENT
62 .sp
63 The filters can be used to perform following actions:
64 .INDENT 0.0
65 .IP \(bu 2
66 convert block group profiles (filter \fIconvert\fP)
67 .IP \(bu 2
68 make block group usage more compact (filter \fIusage\fP)
69 .IP \(bu 2
70 perform actions only on a given device (filters \fIdevid\fP, \fIdrange\fP)
71 .UNINDENT
72 .sp
73 The filters can be applied to a combination of block group types (data,
74 metadata, system). Note that changing only the \fIsystem\fP type needs the force
75 option. Otherwise \fIsystem\fP gets automatically converted whenever \fImetadata\fP
76 profile is converted.
77 .sp
78 When metadata redundancy is reduced (e.g. from RAID1 to single) the force option
79 is also required and it is noted in system log.
80 .sp
81 \fBNOTE:\fP
82 .INDENT 0.0
83 .INDENT 3.5
84 The balance operation needs enough work space, i.e. space that is completely
85 unused in the filesystem, otherwise this may lead to ENOSPC reports. See
86 the section \fIENOSPC\fP for more details.
87 .UNINDENT
88 .UNINDENT
89 .SH COMPATIBILITY
90 .sp
91 \fBNOTE:\fP
92 .INDENT 0.0
93 .INDENT 3.5
94 The balance subcommand also exists under the \fBbtrfs filesystem\fP namespace.
95 This still works for backward compatibility but is deprecated and should not
96 be used any more.
97 .UNINDENT
98 .UNINDENT
99 .sp
100 \fBNOTE:\fP
101 .INDENT 0.0
102 .INDENT 3.5
103 A short syntax \fBbtrfs balance <path>\fP works due to backward compatibility
104 but is deprecated and should not be used any more. Use \fBbtrfs balance start\fP
105 command instead.
106 .UNINDENT
107 .UNINDENT
108 .SH PERFORMANCE IMPLICATIONS
109 .sp
110 Balancing operations are very IO intensive and can also be quite CPU intensive,
111 impacting other ongoing filesystem operations. Typically large amounts of data
112 are copied from one location to another, with corresponding metadata updates.
113 .sp
114 Depending upon the block group layout, it can also be seek heavy. Performance
115 on rotational devices is noticeably worse compared to SSDs or fast arrays.
116 .SH SUBCOMMAND
117 .INDENT 0.0
118 .TP
119 .B cancel <path>
120 cancels a running or paused balance, the command will block and wait until the
121 current block group being processed completes
122 .sp
123 Since kernel 5.7 the response time of the cancellation is significantly
124 improved, on older kernels it might take a long time until currently
125 processed chunk is completely finished.
126 .TP
127 .B pause <path>
128 pause running balance operation, this will store the state of the balance
129 progress and used filters to the filesystem
130 .TP
131 .B resume <path>
132 resume interrupted balance, the balance status must be stored on the filesystem
133 from previous run, e.g. after it was paused or forcibly interrupted and mounted
134 again with \fIskip_balance\fP
135 .TP
136 .B start [options] <path>
137 start the balance operation according to the specified filters, without any filters
138 the data and metadata from the whole filesystem are moved. The process runs in
139 the foreground.
140 .sp
141 \fBNOTE:\fP
142 .INDENT 7.0
143 .INDENT 3.5
144 The balance command without filters will basically move everything in the
145 filesystem to a new physical location on devices (i.e. it does not affect the
146 logical properties of file extents like offsets within files and extent
147 sharing). The run time is potentially very long, depending on the filesystem
148 size. To prevent starting a full balance by accident, the user is warned and
149 has a few seconds to cancel the operation before it starts. The warning and
150 delay can be skipped with \fI\-\-full\-balance\fP option.
151 .UNINDENT
152 .UNINDENT
153 .sp
154 Please note that the filters must be written together with the \fI\-d\fP, \fI\-m\fP and
155 \fI\-s\fP options, because they\(aqre optional and bare \fI\-d\fP and \fI\-m\fP also work and
156 mean no filters.
157 .sp
158 \fBNOTE:\fP
159 .INDENT 7.0
160 .INDENT 3.5
161 When the target profile for conversion filter is \fIraid5\fP or \fIraid6\fP,
162 there\(aqs a safety timeout of 10 seconds to warn users about the status of the feature
163 .UNINDENT
164 .UNINDENT
165 .sp
166 \fBOptions\fP
167 .INDENT 7.0
168 .TP
169 .B \-d[<filters>]
170 act on data block groups, see section \fI\%FILTERS\fP for details about \fIfilters\fP
171 .TP
172 .B \-m[<filters>]
173 act on metadata chunks, see \fI\%FILTERS\fP for details about \fIfilters\fP
174 .TP
175 .B \-s[<filters>]
176 act on system chunks (requires \fI\-f\fP), see \fI\%FILTERS\fP for details about \fIfilters\fP\&.
177 .UNINDENT
178 .INDENT 7.0
179 .TP
180 .B \-f
181 force a reduction of metadata integrity, e.g. when going from \fIraid1\fP to
182 \fIsingle\fP, or skip safety timeout when the target conversion profile is \fIraid5\fP
183 or \fIraid6\fP
184 .UNINDENT
185 .INDENT 7.0
186 .TP
187 .B \-\-background|\-\-bg
188 run the balance operation asynchronously in the background, uses \X'tty: link https://man7.org/linux/man-pages/man2/fork.2.html'\fI\%fork(2)\fP\X'tty: link' to
189 start the process that calls the kernel ioctl
190 .UNINDENT
191 .INDENT 7.0
192 .TP
193 .B \-\-enqueue
194 wait if there\(aqs another exclusive operation running, otherwise continue
195 .TP
196 .B \-v
197 (deprecated) alias for global \(aq\-v\(aq option
198 .UNINDENT
199 .TP
200 .B status [\-v] <path>
201 Show status of running or paused balance.
202 .sp
203 \fBOptions\fP
204 .INDENT 7.0
205 .TP
206 .B \-v
207 (deprecated) alias for global \fI\-v\fP option
208 .UNINDENT
209 .UNINDENT
210 .SH FILTERS
211 .sp
212 From kernel 3.3 onwards, BTRFS balance can limit its action to a subset of the
213 whole filesystem, and can be used to change the replication configuration (e.g.
214 convert data from \fBsingle\fP to \fBRAID1\fP).
215 .sp
216 Balance can be limited to a block group profile with the following options:
217 .INDENT 0.0
218 .IP \(bu 2
219 \fB\-d\fP for data block groups
220 .IP \(bu 2
221 \fB\-m\fP for metadata block groups (also implicitly applies to \fI\-s\fP)
222 .IP \(bu 2
223 \fB\-s\fP for system block groups
224 .UNINDENT
225 .sp
226 The options have an optional parameter which means that the parameter must start
227 right after the option without a space (this is mandatory getopt syntax), like
228 \fB\-dusage=10\fP\&. Options for all block group types can be specified in one command.
229 .sp
230 A filter has the following structure: \fBfilter[=params][,filter=...]\fP
231 .sp
232 To combine multiple filters use \fB,\fP, without spaces. Example: \fB\-dconvert=raid1,soft\fP
233 Note that most filters can only be specified once per block group profile
234 (data/metadata/system block groups).
235 .sp
236 BTRFS can have different profiles on a single device or the same profile on
237 multiple device.
238 .sp
239 The main reason why you want to have different profiles for data and metadata
240 is to provide additional protection of the filesystem\(aqs metadata when devices fail,
241 since a single sector of unrecoverable metadata will break the filesystem,
242 while a single sector of lost data can be trivially recovered by deleting the broken file.
243 .sp
244 Before changing profiles, make sure there is enough unallocated space on
245 existing drives to create new metadata block groups (for filesystems
246 over 50GiB, this is \fB1GB * (number_of_devices + 2))\fP\&.
247 .sp
248 Default profiles on BTRFS are:
249 .INDENT 0.0
250 .IP \(bu 2
251 data: \fBsingle\fP
252 .IP \(bu 2
253 .INDENT 2.0
254 .TP
255 .B metadata:
256 .INDENT 7.0
257 .IP \(bu 2
258 single devices: \fBdup\fP
259 .IP \(bu 2
260 multiple devices: \fBraid1\fP
261 .UNINDENT
262 .UNINDENT
263 .UNINDENT
264 .sp
265 The available filter types are:
266 .SS Filter types
267 .INDENT 0.0
268 .TP
269 .B profiles=<profiles>
270 Balances only block groups with the given profiles. Parameters
271 are a list of profile names separated by \fB|\fP (pipe).
272 .TP
273 .B usage=<percent>, usage=<range>
274 Balances only block groups with usage under the given percentage. The
275 value of 0 is allowed and will clean up completely unused block groups, this
276 should not require any new work space allocated. You may want to use \fIusage=0\fP
277 in case balance is returning ENOSPC and your filesystem is not too full.
278 .sp
279 The argument may be a single value or a range. The single value \fBN\fP means \fIat
280 most N percent used\fP, equivalent to \fB\&..N\fP range syntax. Kernels prior to 4.4
281 accept only the single value format.
282 The minimum range boundary is inclusive, maximum is exclusive.
283 .sp
284 This filter can only be specified once per block group profile.
285 .TP
286 .B devid=<id>
287 Balances only block groups which have at least one chunk on the given
288 device. To list devices with ids use \fBbtrfs filesystem show\fP\&.
289 .sp
290 This filter can only be specified once per block group profile.
291 .TP
292 .B drange=<range>
293 Balance only block groups which overlap with the given byte range on any
294 device. Use in conjunction with \fBdevid\fP to filter on a specific device. The
295 parameter is a range specified as \fBstart..end\fP\&.
296 .sp
297 This filter can only be specified once per block group profile.
298 .TP
299 .B vrange=<range>
300 Balance only block groups which overlap with the given byte range in the
301 filesystem\(aqs internal virtual address space. This is the address space that
302 most reports from btrfs in the kernel log use. The parameter is a range
303 specified as \fBstart..end\fP\&.
304 .sp
305 This filter can only be specified once per block group profile.
306 .TP
307 .B convert=<profile>
308 Convert each selected block group to the given profile name identified by
309 parameters.
310 .sp
311 This filter can only be specified once per block group profile.
312 .sp
313 \fBNOTE:\fP
314 .INDENT 7.0
315 .INDENT 3.5
316 Starting with kernel 4.5, the \fBdata\fP chunks can be converted to/from the
317 \fBDUP\fP profile on a single device.
318 .sp
319 Starting with kernel 4.6, all profiles can be converted to/from \fBDUP\fP on
320 multi\-device filesystems.
321 .UNINDENT
322 .UNINDENT
323 .sp
324 \fBWARNING:\fP
325 .INDENT 7.0
326 .INDENT 3.5
327 Bad or missing device are not detected immediately during
328 runtime and this depends on some later event like failed write
329 or failed transaction commit. If there\(aqs a known failing
330 device, or a device deleted by \fB/sys/block/<dev>/device/delete\fP interface,
331 the device will be still accessed and written to.
332 .sp
333 In such case, one should not convert to a profile with lower
334 redundancy (e.g. from \fIRAID1\fP to \fISINGLE\fP),
335 as attempts to create new chunks on the new devices will cause
336 various problems.
337 .sp
338 The proper action is to use \fBbtrfs replace\fP or
339 \fBbtrfs device remove\fP to handle the failing/missing
340 device first. Then convert will work with all devices
341 correctly.
342 .UNINDENT
343 .UNINDENT
344 .TP
345 .B limit=<number>, limit=<range>
346 Process only given number of chunks, after all filters are applied. This can be
347 used to specifically target a chunk in connection with other filters (\fBdrange\fP,
348 \fBvrange\fP) or just simply limit the amount of work done by a single balance run.
349 .sp
350 The argument may be a single value or a range. The single value \fBN\fP means \fIat
351 most N chunks\fP, equivalent to \fB\&..N\fP range syntax. Kernels prior to 4.4 accept
352 only the single value format. The range minimum and maximum are inclusive.
353 .sp
354 This filter can only be specified once per block group profile.
355 .TP
356 .B stripes=<range>
357 Balance only block groups which have the given number of stripes. The parameter
358 is a range specified as \fBstart..end\fP\&. Makes sense for block group profiles that
359 utilize striping, i.e. RAID0/10/5/6. The range minimum and maximum are
360 inclusive.
361 .sp
362 This filter can only be specified once per block group profile.
363 .TP
364 .B soft
365 Takes no parameters. Only has meaning when converting between profiles, or
366 When doing convert from one profile to another and soft mode is on,
367 chunks that already have the target profile are left untouched.
368 This is useful e.g. when half of the filesystem was converted earlier but got
369 cancelled.
370 .sp
371 The soft mode switch is (like every other filter) per\-type.
372 For example, this means that we can convert metadata chunks the \(dqhard\(dq way
373 while converting data chunks selectively with soft switch.
374 .sp
375 This filter can only be specified once per block group profile.
376 .UNINDENT
377 .sp
378 Profile names, used in \fBprofiles\fP and \fBconvert\fP are one of:
379 .INDENT 0.0
380 .IP \(bu 2
381 \fBraid0\fP
382 .IP \(bu 2
383 \fBraid1\fP
384 .IP \(bu 2
385 \fBraid1c3\fP
386 .IP \(bu 2
387 \fBraid1c4\fP
388 .IP \(bu 2
389 \fBraid10\fP
390 .IP \(bu 2
391 \fBraid5\fP
392 .IP \(bu 2
393 \fBraid6\fP
394 .IP \(bu 2
395 \fBdup\fP
396 .IP \(bu 2
397 \fBsingle\fP
398 .UNINDENT
399 .sp
400 The mixed data/metadata profiles can be converted in the same way, but conversion
401 between mixed and non\-mixed is not implemented. For the constraints of the
402 profiles please refer to \fI\%mkfs.btrfs(8)\fP section
403 \fI\%PROFILES\fP\&.
404 .SH ENOSPC
405 .sp
406 The way balance operates, it usually needs to temporarily create a new block
407 group and move the old data there, before the old block group can be removed.
408 For that it needs the work space, otherwise it fails for ENOSPC reasons.
409 This is not the same ENOSPC as if the free space is exhausted. This refers to
410 the space on the level of block groups, which are bigger parts of the filesystem
411 that contain many file extents.
412 .sp
413 The free work space can be calculated from the output of the \fBbtrfs filesystem show\fP
414 command:
415 .INDENT 0.0
416 .INDENT 3.5
417 .sp
418 .EX
419 Label: \(aqBTRFS\(aq uuid: 8a9d72cd\-ead3\-469d\-b371\-9c7203276265
420 Total devices 2 FS bytes used 77.03GiB
421 devid 1 size 53.90GiB used 51.90GiB path /dev/sdc2
422 devid 2 size 53.90GiB used 51.90GiB path /dev/sde1
423 .EE
424 .UNINDENT
425 .UNINDENT
426 .sp
427 \fIsize\fP \- \fIused\fP = \fIfree work space\fP
428 .sp
429 \fI53.90GiB\fP \- \fI51.90GiB\fP = \fI2.00GiB\fP
430 .sp
431 An example of a filter that does not require workspace is \fIusage=0\fP\&. This will
432 scan through all unused block groups of a given type and will reclaim the
433 space. After that it might be possible to run other filters.
434 .sp
435 \fBCONVERSIONS ON MULTIPLE DEVICES\fP
436 .sp
437 Conversion to profiles based on striping (RAID0, RAID5/6) require the work
438 space on each device. An interrupted balance may leave partially filled block
439 groups that consume the work space.
440 .SH EXAMPLES
441 .sp
442 A more comprehensive example when going from one to multiple devices, and back,
443 can be found in section \fITYPICAL USECASES\fP of \fI\%btrfs\-device(8)\fP\&.
444 .SS MAKING BLOCK GROUP LAYOUT MORE COMPACT
445 .sp
446 The layout of block groups is not normally visible; most tools report only
447 summarized numbers of free or used space, but there are still some hints
448 provided.
449 .sp
450 Let\(aqs use the following real life example and start with the output:
451 .INDENT 0.0
452 .INDENT 3.5
453 .sp
454 .EX
455 $ btrfs filesystem df /path
456 Data, single: total=75.81GiB, used=64.44GiB
457 System, RAID1: total=32.00MiB, used=20.00KiB
458 Metadata, RAID1: total=15.87GiB, used=8.84GiB
459 GlobalReserve, single: total=512.00MiB, used=0.00B
460 .EE
461 .UNINDENT
462 .UNINDENT
463 .sp
464 Roughly calculating for data, \fI75G \- 64G = 11G\fP, the used/total ratio is
465 about \fI85%\fP\&. How can we can interpret that:
466 .INDENT 0.0
467 .IP \(bu 2
468 chunks are filled by 85% on average, i.e. the \fIusage\fP filter with anything
469 smaller than 85 will likely not affect anything
470 .IP \(bu 2
471 in a more realistic scenario, the space is distributed unevenly, we can
472 assume there are completely used chunks and the remaining are partially filled
473 .UNINDENT
474 .sp
475 Compacting the layout could be used on both. In the former case it would spread
476 data of a given chunk to the others and removing it. Here we can estimate that
477 roughly 850 MiB of data have to be moved (85% of a 1 GiB chunk).
478 .sp
479 In the latter case, targeting the partially used chunks will have to move less
480 data and thus will be faster. A typical filter command would look like:
481 .INDENT 0.0
482 .INDENT 3.5
483 .sp
484 .EX
485 # btrfs balance start \-dusage=50 /path
486 Done, had to relocate 2 out of 97 chunks
487
488 $ btrfs filesystem df /path
489 Data, single: total=74.03GiB, used=64.43GiB
490 System, RAID1: total=32.00MiB, used=20.00KiB
491 Metadata, RAID1: total=15.87GiB, used=8.84GiB
492 GlobalReserve, single: total=512.00MiB, used=0.00B
493 .EE
494 .UNINDENT
495 .UNINDENT
496 .sp
497 As you can see, the \fItotal\fP amount of data is decreased by just 1 GiB, which is
498 an expected result. Let\(aqs see what will happen when we increase the estimated
499 usage filter.
500 .INDENT 0.0
501 .INDENT 3.5
502 .sp
503 .EX
504 # btrfs balance start \-dusage=85 /path
505 Done, had to relocate 13 out of 95 chunks
506
507 $ btrfs filesystem df /path
508 Data, single: total=68.03GiB, used=64.43GiB
509 System, RAID1: total=32.00MiB, used=20.00KiB
510 Metadata, RAID1: total=15.87GiB, used=8.85GiB
511 GlobalReserve, single: total=512.00MiB, used=0.00B
512 .EE
513 .UNINDENT
514 .UNINDENT
515 .sp
516 Now the used/total ratio is about 94% and we moved about \fI74G \- 68G = 6G\fP of
517 data to the remaining block groups, i.e. the 6GiB are now free of filesystem
518 structures, and can be reused for new data or metadata block groups.
519 .sp
520 We can do a similar exercise with the metadata block groups, but this should
521 not typically be necessary, unless the used/total ratio is really off. Here
522 the ratio is roughly 50% but the difference as an absolute number is \(dqa few
523 gigabytes\(dq, which can be considered normal for a workload with snapshots or
524 reflinks updated frequently.
525 .INDENT 0.0
526 .INDENT 3.5
527 .sp
528 .EX
529 # btrfs balance start \-musage=50 /path
530 Done, had to relocate 4 out of 89 chunks
531
532 $ btrfs filesystem df /path
533 Data, single: total=68.03GiB, used=64.43GiB
534 System, RAID1: total=32.00MiB, used=20.00KiB
535 Metadata, RAID1: total=14.87GiB, used=8.85GiB
536 GlobalReserve, single: total=512.00MiB, used=0.00B
537 .EE
538 .UNINDENT
539 .UNINDENT
540 .sp
541 Just 1 GiB decrease, which possibly means there are block groups with good
542 utilization. Making the metadata layout more compact would in turn require
543 updating more metadata structures, i.e. lots of IO. As running out of metadata
544 space is a more severe problem, it\(aqs not necessary to keep the utilization
545 ratio too high. For the purpose of this example, let\(aqs see the effects of
546 further compaction:
547 .INDENT 0.0
548 .INDENT 3.5
549 .sp
550 .EX
551 # btrfs balance start \-musage=70 /path
552 Done, had to relocate 13 out of 88 chunks
553
554 $ btrfs filesystem df .
555 Data, single: total=68.03GiB, used=64.43GiB
556 System, RAID1: total=32.00MiB, used=20.00KiB
557 Metadata, RAID1: total=11.97GiB, used=8.83GiB
558 GlobalReserve, single: total=512.00MiB, used=0.00B
559 .EE
560 .UNINDENT
561 .UNINDENT
562 .SS GETTING RID OF COMPLETELY UNUSED BLOCK GROUPS
563 .sp
564 Normally the balance operation needs a work space, to temporarily move the
565 data before the old block groups gets removed. If there\(aqs no work space, it
566 ends with \fIno space left\fP\&.
567 .sp
568 There\(aqs a special case when the block groups are completely unused, possibly
569 left after removing lots of files or deleting snapshots. Removing empty block
570 groups is automatic since 3.18. The same can be achieved manually with a
571 notable exception that this operation does not require the work space. Thus it
572 can be used to reclaim unused block groups to make it available.
573 .INDENT 0.0
574 .INDENT 3.5
575 .sp
576 .EX
577 # btrfs balance start \-dusage=0 /path
578 .EE
579 .UNINDENT
580 .UNINDENT
581 .sp
582 This should lead to decrease in the \fItotal\fP numbers in the \fBbtrfs filesystem df\fP output.
583 .SH EXIT STATUS
584 .sp
585 Unless indicated otherwise below, all \fBbtrfs balance\fP subcommands
586 return a zero exit status if they succeed, and non zero in case of
587 failure.
588 .sp
589 The \fBpause\fP, \fBcancel\fP, and \fBresume\fP subcommands exit with a status of
590 \fB2\fP if they fail because a balance operation was not running.
591 .sp
592 The \fBstatus\fP subcommand exits with a status of \fB0\fP if a balance
593 operation is not running, \fB1\fP if the command\-line usage is incorrect
594 or a balance operation is still running, and \fB2\fP on other errors.
595 .SH AVAILABILITY
596 .sp
597 \fBbtrfs\fP is part of btrfs\-progs. Please refer to the documentation at
598 \X'tty: link https://btrfs.readthedocs.io'\fI\%https://btrfs.readthedocs.io\fP\X'tty: link'\&.
599 .SH SEE ALSO
600 .sp
601 \fI\%mkfs.btrfs(8)\fP,
602 \fI\%btrfs\-device(8)\fP
603 .\" Generated by docutils manpage writer.
604 .