Home
last modified time | relevance | path

Searched refs:subvolume (Results 1 – 9 of 9) sorted by relevance

/systemd-251/src/shared/
Dbtrfs-util.c55 static int extract_subvolume_name(const char *path, const char **subvolume) { in extract_subvolume_name() argument
60 assert(subvolume); in extract_subvolume_name()
68 *subvolume = fn; in extract_subvolume_name()
100 int btrfs_subvol_make_fd(int fd, const char *subvolume) { in btrfs_subvol_make_fd() argument
105 assert(subvolume); in btrfs_subvol_make_fd()
107 r = validate_subvolume_name(subvolume); in btrfs_subvol_make_fd()
125 strncpy(args.name, subvolume, sizeof(args.name)-1); in btrfs_subvol_make_fd()
132 const char *subvolume; in btrfs_subvol_make() local
137 r = extract_subvolume_name(path, &subvolume); in btrfs_subvol_make()
145 return btrfs_subvol_make_fd(fd, subvolume); in btrfs_subvol_make()
[all …]
Dbtrfs-util.h65 int btrfs_subvol_make_fd(int fd, const char *subvolume);
80 int btrfs_subvol_remove_fd(int fd, const char *subvolume, BtrfsRemoveFlags flags);
86 int btrfs_subvol_get_id(int fd, const char *subvolume, uint64_t *ret);
/systemd-251/docs/
DHOME_DIRECTORY.md34 If the plain directory or `btrfs` subvolume storage mechanism of
35 `systemd-homed` is used (i.e. `--storage=directory` or `--storage=subvolume` on
147 directory-based storage mechanisms (`directory`, `subvolume` and `fscrypt`)
DUSER_RECORD.md350 `storage` → A string, one of `classic`, `luks`, `directory`, `subvolume`,
355 is self-contained. Similar, `subvolume` is a `btrfs` subvolume that also
428 the LUKS volume on. For `fscrypt`, `directory`, `subvolume` this refers to the
772 updated to prefer `subvolume`, which however doesn't change the actual storage
799 directory/subvolume/fscrypt storage this is the current disk space used as
DPORTABLE_SERVICES.md166 2. The image must either be a plain sub-directory (or btrfs subvolume)
288 sub-directory, a btrfs subvolume or a raw disk image.
DDISCOVERABLE_PARTITIONS.md348 system/container manager it will be mounted with its *default* subvolume. The
349 installer should make sure to set the default subvolume correctly using "btrfs
350 subvolume set-default".
DENVIRONMENT.md300 subvolumes only if the OS itself is installed into a subvolume. If set to `1`
344 enabled, the quota group of the subvolume is automatically added to a
/systemd-251/
DTODO1598 - as an extension to the directory+subvolume backend: if located on
DNEWS1363 $SYSTEMD_IMPORT_SYNC, which may be used disable btrfs subvolume
3604 now default to the directory or subvolume backends instead of the
8635 instead of a subvolume (even on a btrfs file system) if the
8637 subvolume. This should simplify things with certain chroot()
9735 root directory, subvolume or disk image automatically, in