mirror of
https://github.com/koverstreet/bcachefs-tools.git
synced 2025-02-23 00:00:02 +03:00
89b322abb3
Instead of requiring the user to supply all the device nodes for a multi-device FS, allow them to specifiy 1 of them. We then fetch the UUID for the FS and then find all the disks on the system that match this UUID. This allows me to bring up a bcachefs FS in /etc/fstab by using a UUID. This works because it appears the mount command looks up the UUID, finds an entry in /dev/disk/by-uuid and then passes that found device node to mount.bcachefs which fails with `insufficient_devices_to_start` as bcachefs is expecting a list of devices with a ":" between them. This behavior is preserved if a user specifies a list of all the needed device nodes to bring up the FS. Signed-off-by: Tony Asleson <tasleson@redhat.com> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> |
||
|---|---|---|
| .github | ||
| bch_bindgen | ||
| c_src | ||
| ccan | ||
| debian | ||
| doc | ||
| fsck | ||
| include | ||
| initramfs | ||
| libbcachefs | ||
| linux | ||
| packaging | ||
| raid | ||
| src | ||
| tests | ||
| udev | ||
| .bcachefs_revision | ||
| .editorconfig | ||
| .gitignore | ||
| bcachefs | ||
| bcachefs.8 | ||
| build.nix | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| COPYING | ||
| default.nix | ||
| flake.lock | ||
| flake.nix | ||
| INSTALL.md | ||
| make-release-tarball.sh | ||
| Makefile | ||
| Makefile.compiler | ||
| mount.bcachefs.sh | ||
| README.md | ||
| rustfmt.toml | ||
bcachefs-tools
Userspace tools and docs for bcachefs
Bcachefs is an advanced new filesystem for Linux, with an emphasis on reliability and robustness and the complete set of features one would expect from a modern filesystem.
This repo primarily consists of the following:
- bcachefs tool, the reason this repo exists.
- {mkfs,mount,fsck}.bcachefs utils, which is just wrappers calling the corresponding subcommands in the main tool
- docs in the form of man-pages and a user manual
Please refer to the main site for getting started An in-depth user manual is (also) found on the official website
Version semantics
The tools relies on an expected disk format structure which is reflected by your current kernel version. Disk format can be upgraded or downgraded automatically by the kernel, if needed.
- Any patch-level change means no disk format change
- Any minor-level change means a potential disk format change which is not breaking
- Any major-level change means breaking changes
Build and install
Refer to INSTALL.md
Bug reports and contributions
- The official mailing list, linux-bcachefs@vger.kernel.org
- IRC: #bcache on OFTC (irc.oftc.net). Although, note that it can be easily missed.