-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rootfs mount order issue (tmpfs + zfs) #270
Comments
not sure if thats a disko or a nixpkgs problem. maybe posting a config which causes the breakage will help me investigate |
Sorry I think I forgot to save the troubling config but this should at least be close to reproducing the issue. If I remember correctly, I ended up using legacy mountpoints for all datasets in order to workaround the ordering issue.
|
I think this issue should be fixed by #474 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
disko mounts zfs pool before the rootfs mount (which is tmpfs in my case), shadowing the zfs native mounts. Example log:
Ideal scenario
disko should mount the root before importing the zfs pool.
BTW I'm only using one legacy mount to workaround impermance desire for a mount which has
neededForBoot
set from the nix configuration (so it doesn't quite "see" zfs native mounts).Workarounds
From the log output, it appears to me that using legacy mounts for all zfs datasets would work.
The text was updated successfully, but these errors were encountered: