Comments (1)
datasets.*.mountpoint
- This sets a "legacy" mountpoint, aka the fstab. Typical ZFS installations instead use the mountpoint property (see the next point)
datasets.*.options.mountpoint
- This sets the respective zfsprop - the native feature used by ZFS to automatically mount datasets independently of fstab (typically via a systemd service that grabs information from the datasets and mounts it).
datasets.*.options.*
can actually be used to set any zfsprop - compression, encryption, or even custom user-specified ones likecom.sun:auto-snapshot
(which is used in second party tooling outside of ZFS, in this case some sort of sun microsystems thing).
datasets.*.content.mountpoint
- This isn't actually valid - I believe you're referring to
disko.devices.<devicename>.content.partitions.<partname>.content.mountpoint
, notdisko.devices.zpool.<zpoolname>.datasets.<datasetname>.content.mountpoint
. In actuality it doesn't really matter - since neither are valid in the context - the former is only valid ifdisko.devices.<devicename>.content.partitions.<partname>.type
is NOTzfs
.- It essentially boils down to ambiguous wording -
disko.devices.zpool
is used to define the contents inside a zfs pool - datasets, zfs volumes, and their respective properties - whereasdisko.devices.<devicename>...
defines the physical layout of the zfs pool as a whole (what disks to use, whether to use an entire disk or a single partition etc). Disko further abstracts upon this by adding in custom glue in the form of mountpoint. - In my mind the best solution would be to rename
mountpoint
to something likefstabEntry
to disambiguate the two -mountpoint
is generic and has it's own special meaning in various contexts. One alternative (or additional?) solution would be to rename...<datasetname>.options
to...<datasetname>.properties
/zfsprops
, since that aligns closer to the upstream implementation.
- It essentially boils down to ambiguous wording -
Edit:
Further confusion comes because in order to use an fstab entry to mount a zfs dataset, you need to set the zfsprop mountpoint=legacy
for it to work properly.
p.s. I realize that changing an option name isn't ideal, but it's not unheard of, and is in my opinion better to do sooner rather than later, in case disko sees more widespread adoption and it becomes even more cemented. Part of the problem is also the lack of easily readable docs, so some of this concern may be invalid once those are available (though I personally prefer explicit configuration rather than ambiguous configuration).
from disko.
Related Issues (20)
- Using disko to generate raspberry pi sd card images
- Random boot failues due to partition confusion because disko now relies on `by-partlabel` HOT 12
- ZFS Features Support: Dataset property inheritance HOT 2
- Converting an existing system to use disko? HOT 5
- GRUB Mirrored boot entries with disko HOT 2
- zpool create error: one or more vdevs refer to the same device HOT 1
- How to test luks setup with `--vm-test` HOT 5
- device already has a partition, skipping creating zpool zroot HOT 1
- Can't automount ZFS dataset without using mountpoint="legacy" HOT 3
- `disko-install` should error out immediately if it was invoked without `sudo` HOT 1
- [DOC] add demo/example config for subvolumes on btrfs on lvm on luks HOT 1
- Add docs for upgrade from legacy table to gpt HOT 5
- QUESTION: neededForBoot option HOT 2
- Random Boot failures due to failing to mount /usr/bin HOT 4
- Size range HOT 1
- encrypted swap and hibernation HOT 2
- Generate an .iso unattended install image HOT 17
- typo in the docs?
- how to to pass flake `self` using `specialArgs`? HOT 2
- disko-install: error: infinite recursion encountered HOT 13
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from disko.