#
a63188c8 |
| 03-Jun-2023 |
Tomohiro Kusumi <tkusumi@netbsd.org> |
usr.sbin/makefs: Add HAMMER2 offline bulkfree support
Since makefs HAMMER2 implements the entire HAMMER2 logic in userspace with selected vops using single threaded xops, it's actually trivial to su
usr.sbin/makefs: Add HAMMER2 offline bulkfree support
Since makefs HAMMER2 implements the entire HAMMER2 logic in userspace with selected vops using single threaded xops, it's actually trivial to support other operations, e.g. HAMMER2 ioctls.
This commit adds bulkfree (free unreferenced blocks by scanning the entire data chains from vchain) option to makefs. Unlike the existing hammer2(8) "bulkfree" directive which requires live filesystem, this option enables offline bulkfree against unmounted HAMMER2 image.
The offline bulkfree takes HAMMER2 specific "-o B" option. When this option is specified, makefs runs offline bulkfree against `image-file` argument instead of creating one, hence it must be a valid HAMMER2 image. `image-file` can be either a regular file or block device. Unlike normal use case, `directory` argument is unused, but it's still required. It can be any valid path or simply "--".
e.g. $ makefs -t hammer2 -o B /dev/adx -- $ makefs -t hammer2 -o B /path/to/hammer2.img --
Technically, all HAMMER2 ioctls can be implemented in makefs as offline version, but "bulkfree" and "growfs" are probably the only hammer2(8) directives that make sense to exist as offline version.
Note that the limitation regarding OOM mentioned in 2d60b848f2 also applies to bulkfree, i.e. makefs(8) could fail with partially written `image-file` if it contains insane number of files or directories.
show more ...
|