mirror of
https://github.com/kdave/btrfs-progs
synced 2025-04-10 11:11:16 +00:00
btrfs-progs: docs: fix typos
Thanks to hunspell. [ci skip] Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
David Sterba
parent
06d01abe82
commit
ea421ec2a2
@ -67,7 +67,7 @@ Referencing:
|
||||
|
||||
- generic links can use the free form link syntax with description ```Link text <https://example.com>`__``
|
||||
(note the double underscore, this is *anonymous* link and does not create a reference)
|
||||
or plain link that will auto-render to a clikable link https://example.com
|
||||
or plain link that will auto-render to a clickable link https://example.com
|
||||
|
||||
- in manual pages: always use full link as it's meant to be read in terminal
|
||||
output and must allow copy&paste
|
||||
|
||||
@ -853,7 +853,7 @@ Pull requests:
|
||||
`v5.4-rc7 <https://git.kernel.org/linus/00aff6836241ae5654895dcea10e6d4fc5878ca6>`__,
|
||||
`v5.4-rc8 <https://git.kernel.org/linus/afd7a71872f14062cc12cac126bb8e219e7dacf6>`__
|
||||
|
||||
- tree checker: adde sanity checks for tree items, extent items, and references
|
||||
- tree checker: added sanity checks for tree items, extent items, and references
|
||||
- deprecated subvolume creation mode BTRFS_SUBVOL_CREATE_ASYNC
|
||||
- qgroup relation deletion tries harder, orphan entries are removed too
|
||||
- space handling improvements (ticket reservations, flushing, overcommit logic)
|
||||
@ -1023,7 +1023,7 @@ Pull requests:
|
||||
Highlights:
|
||||
|
||||
- performance improvements in fsync (dbench workload: higher throughput, lower latency)
|
||||
- sysfs exports current exclusive operataion (balance, resize, device add/del/...)
|
||||
- sysfs exports current exclusive operation (balance, resize, device add/del/...)
|
||||
- sysfs exports supported send stream version
|
||||
|
||||
Core:
|
||||
@ -1083,7 +1083,7 @@ Features:
|
||||
|
||||
Core changes:
|
||||
|
||||
- subpage block size support peparations
|
||||
- subpage block size support preparations
|
||||
|
||||
Fixes:
|
||||
|
||||
@ -1434,7 +1434,7 @@ Qgroup:
|
||||
- limits are shared upon snapshot
|
||||
- allow to remove qgroup which has parent but no child
|
||||
- fix status of qgroup consistency after rescan
|
||||
- fix quota status bits after dsiabling
|
||||
- fix quota status bits after disabling
|
||||
- mark qgroups inconsistent after assign/delete actions
|
||||
- code cleanups
|
||||
|
||||
@ -1475,7 +1475,7 @@ Fixes:
|
||||
^^^^^^^^^^^^^^
|
||||
|
||||
- send fixes: cloning, sending with parent
|
||||
- improved handling of framgented space using bitmaps
|
||||
- improved handling of fragmented space using bitmaps
|
||||
- new mount option for debugging: fragment=data|metadata|all
|
||||
- updated balance filters: limit, stripes, usage
|
||||
- more bugfixes and cleanups
|
||||
@ -1501,7 +1501,7 @@ Fixes:
|
||||
writes (now does: nologreplay)
|
||||
|
||||
- default inline limit is now 2048 (instead of page size, usually 4096)
|
||||
- /dev/btrfs-control now understands the GET_SUPPORTE_FEATURES ioctl
|
||||
- /dev/btrfs-control now understands the GET_SUPPORTED_FEATURES ioctl
|
||||
- get rid of harmless message "''could not find root %llu''"
|
||||
- preparatory work for subpage-blocksize patchset
|
||||
- fix bug when using overlayfs
|
||||
@ -1574,7 +1574,7 @@ Fixes:
|
||||
^^^^^^^^^^^^^^^
|
||||
|
||||
- new tracepoints: file item
|
||||
- fix qgoup accounting when inode_cache is in use
|
||||
- fix qgroup accounting when inode_cache is in use
|
||||
- fix incorrect number report in stat::t_blocks under certain conditions
|
||||
- raid56 fixes:
|
||||
|
||||
@ -1877,7 +1877,7 @@ Fixes:
|
||||
^^^^^^^^^^^^^^^
|
||||
|
||||
* ''fiemap'' exports information about shared extents
|
||||
* bugfix and stability foucsed release
|
||||
* bugfix and stability focused release
|
||||
|
||||
3.14 (Mar 2014)
|
||||
^^^^^^^^^^^^^^^
|
||||
|
||||
@ -140,7 +140,7 @@ defragment [options] <file>|<dir> [<file>|<dir>...]
|
||||
logic. Reasonable values are from tens to hundreds of megabytes.
|
||||
|
||||
--step SIZE
|
||||
Perform defragmention in the range in SIZE steps and flush (*-f*) after each one.
|
||||
Perform defragmentation in the range in SIZE steps and flush (*-f*) after each one.
|
||||
The range is default (the whole file) or given by *-s* and *-l*, split into
|
||||
the steps or done in one go if the step is larger. Minimum range size is 256KiB.
|
||||
|
||||
|
||||
@ -550,7 +550,7 @@ BTRFS_IOC_ADD_DEV
|
||||
|
||||
Add a given block device to the filesystem. Unlike the command :command:`btrfs device add`
|
||||
there's are no safety checks (like existence of another filesystem on the
|
||||
device), device preparataion (like TRIM or zone reset), so use it with care.
|
||||
device), device preparation (like TRIM or zone reset), so use it with care.
|
||||
|
||||
This is a filesystem-exclusive operation and it will fail if there's another
|
||||
one already running, with one exception, when there's a paused balance.
|
||||
@ -968,7 +968,7 @@ Use cases (:ref:`definition of constants<struct_btrfs_ioctl_subvol_wait>`):
|
||||
* - ioctl args
|
||||
- :ref:`struct btrfs_ioctl_subvol_wait<struct_btrfs_ioctl_subvol_wait>`
|
||||
* - args.subvolid
|
||||
- Depending on the mode, the numeric id of subolume to wait for, or
|
||||
- Depending on the mode, the numeric id of subvolume to wait for, or
|
||||
the one queried by *PEEK* modes
|
||||
* - args.mode
|
||||
- mode of operation described above
|
||||
|
||||
@ -220,7 +220,7 @@ SYSFS INTERFACE
|
||||
|
||||
.. include:: ch-sysfs.rst
|
||||
|
||||
.. _man-btrfs5-fileysstem-exclusive-operations:
|
||||
.. _man-btrfs5-filesystem-exclusive-operations:
|
||||
|
||||
FILESYSTEM EXCLUSIVE OPERATIONS
|
||||
-------------------------------
|
||||
|
||||
@ -72,7 +72,7 @@ exclusive_operation
|
||||
|
||||
Shows the running exclusive operation.
|
||||
Check section
|
||||
:ref:`FILESYSTEM EXCLUSIVE OPERATIONS<man-btrfs5-fileysstem-exclusive-operations>`
|
||||
:ref:`FILESYSTEM EXCLUSIVE OPERATIONS<man-btrfs5-filesystem-exclusive-operations>`
|
||||
for details.
|
||||
|
||||
generation
|
||||
@ -216,7 +216,7 @@ scrub_speed_max
|
||||
(RW, since: 5.14)
|
||||
|
||||
Shows the scrub speed limit for this device. The unit is Bytes/s.
|
||||
0 means no limit. The value can be set but is not persisent.
|
||||
0 means no limit. The value can be set but is not persistent.
|
||||
|
||||
writeable
|
||||
(RO, since: 5.6)
|
||||
|
||||
@ -64,7 +64,7 @@ candidate for a CC: of the bugreport.
|
||||
|
||||
**Do**: talk to the maintainer if he forgot to add this tag to the final patch.
|
||||
Reviews do take time and the patches land in various branches early after
|
||||
they're sent to the mailingslist for testing, but the reviews are always
|
||||
they're sent to the mailinglist for testing, but the reviews are always
|
||||
welcome.
|
||||
|
||||
**Do**: collect the Reviewed-by tags for patches that get resent unchanged e.g.
|
||||
@ -236,7 +236,7 @@ Good practices, contribution hints
|
||||
- be patient if your patch is not accepted immediately, try to send a gentle
|
||||
ping if there's a significant time without any action
|
||||
- if you want to start contributing but are not sure about how to do that,
|
||||
lurk in the mailingist or on the IRC channel
|
||||
lurk in the mailinglist or on the IRC channel
|
||||
- every patch should implement one thing -- this is vaguely defined, you may
|
||||
receive comments about patch splitting or merging with other
|
||||
- every patch must be compilable when applied, possibly with all related
|
||||
@ -451,7 +451,7 @@ copyright holders of changes in a given file. The code is usually heavily
|
||||
changed over time in smaller portions, slowly morphing into something that does
|
||||
not resemble the original code anymore though it shares a lot of the core ideas
|
||||
and implemented logic. A copyright notice by a company that does not exist
|
||||
anymore from 10 years ago is a clear example of uselesness for the developers.
|
||||
anymore from 10 years ago is a clear example of uselessness for the developers.
|
||||
|
||||
When code is moved verbatim from a file to another file, in the new file it
|
||||
appears to be contributed by a single author while it is in most cases code
|
||||
|
||||
@ -120,7 +120,7 @@ There are several ways how to react to the unexpected conditions:
|
||||
This would cause the filesystem to be flipped read-only to prevent further
|
||||
corruption.
|
||||
|
||||
Additionally call trace would be dumpped for the first btrfs_abort_transaction()
|
||||
Additionally call trace would be dumped for the first btrfs_abort_transaction()
|
||||
call site.
|
||||
|
||||
- ASSERT()
|
||||
|
||||
@ -114,7 +114,7 @@ Log Root Tree
|
||||
UUID Tree
|
||||
---------
|
||||
|
||||
The tree storesc correspondence between UUIDs and subvolumes. Used for
|
||||
The tree stores correspondence between UUIDs and subvolumes. Used for
|
||||
quick lookup during send.
|
||||
|
||||
|
||||
|
||||
@ -614,7 +614,7 @@ hopefully not destroying both copies of particular data in case of DUP.
|
||||
|
||||
The wear levelling techniques can also lead to reduced redundancy, even if the
|
||||
device does not do any deduplication. The controllers may put data written in
|
||||
a short timespan into the same physical storage unit (cell, block etc). In case
|
||||
a short time span into the same physical storage unit (cell, block etc). In case
|
||||
this unit dies, both copies are lost. BTRFS does not add any artificial delay
|
||||
between metadata writes.
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user