Legacy ZFS uses fstab to mount its datasets. In an attempt to fix
another problem 900bc0206348 broke legacy ZFS in fstab(5). This
comit works around the problem by mountcritlocal scanning /etc/fstab
for zfs mountpoint and if any are found invoke /etc/rc.d/zpool start.
Details
Details
Running here.
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Just a quick Q, but I think this is for the best.
Though it still has the problem the other fix tried to fix i think. Do we want to put the loop after all the other filesystem? Or would that break ufs mounts on ZFS? Zfs doing its own thing is kinda a pain...
libexec/rc/rc.d/mountcritlocal | ||
---|---|---|
34 | Do we call it directly or use service? |
Comment Actions
No. Because the order of mounts in fstab is not preserved. It would be non-zfs first then zfs. Currently filesystems are mounted in sequence.
Agreed, this is a bit of a hack but IMO there is no other choice between the two options.
libexec/rc/rc.d/mountcritlocal | ||
---|---|---|
34 | service(8) is not available until /usr is mounted. /usr could be (and is here) mounted by mountcritlocal. |