There are times when ZFS options can not be applied at the moment,
i.e. changing desired mountpoints of active filesystems (or setting
a mountpoint over a filesystem location that is currently not empty).

Such attempts now bail out with messages like:
cannot unmount '/var/adm': Device busy
cannot mount '/export': directory is not empty

and such.

Is it possible to force the new values to be saved into ZFS dataset
properties, so they do take effect upon next pool import?

I currently work around the harder of such situations with a reboot
into a different boot environment or even into a livecd/failsafe,
just so that the needed datasets or paths won't be "busy" and so I
can set, verify and apply these mountpoint values. This is not a
convenient way to do things :)

//Jim Klimov

zfs-discuss mailing list

Reply via email to