diff options
| author | Kent Overstreet <kent.overstreet@gmail.com> | 2021-04-11 20:00:23 -0400 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@gmail.com> | 2021-04-11 20:30:13 -0400 |
| commit | ba9cd507193e4e308acc6ec84ebcfd0f15fe997d (patch) | |
| tree | 1019468ab344383f04f6f8ae082c53087079a02e | |
| parent | ca5107a90dd49b640c922e2f72bf032447b1ac28 (diff) | |
fix typos
| -rw-r--r-- | Roadmap.mdwn | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/Roadmap.mdwn b/Roadmap.mdwn index 13e4442..684be04 100644 --- a/Roadmap.mdwn +++ b/Roadmap.mdwn @@ -173,15 +173,14 @@ need online fsck. Fsck in bcachefs is divided up into two main components: there is `btree_gc`, which walks the btree and regenerates allocation information (and also checks -btree topology), and there is fsck proper which checks higher level filesystme +btree topology), and there is fsck proper which checks higher level filesystem invariants (e.g. extents/dirents/xattrs must belong to an inode, and filesystem connectivity). -so named because -bachefs originally (when it was bcache) not only did not have persistent -allocation information, it also didn't keep bucket sector counts up to date when -adding/removing extents from the btree - it relied entirely on periodically -rescanning the btree. +The `btree_gc` subsystem is so named because originally (when bcachefs was +bcache) not only did not have persistent allocation information, it also didn't +keep bucket sector counts up to date when adding/removing extents from the btree +- it relied entirely on periodically rescanning the btree. This capability was kept for a very long time, partly as an aid to testing an debugging when uptodate allocation information was being developed, then |