Bug 204506 - bsdinstall(8) umount target should be able to unmount zfs filesystems
Summary: bsdinstall(8) umount target should be able to unmount zfs filesystems
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.2-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-sysinstall mailing list
Depends on:
Reported: 2015-11-12 15:41 UTC by fre.fbsdpr
Modified: 2018-05-28 19:41 UTC (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description fre.fbsdpr 2015-11-12 15:41:13 UTC

When calling the script target with the ZFSBOOT_DISKS variable set, the zfsboot target will be run.  This logic should also be used for the umount target, choosing 'zfs umount -a' to be run.
Comment 1 Kamil Czekirda freebsd_committer 2015-12-20 21:46:05 UTC

We can add 'zfs umount -a', but it's not a perfect, because I sometimes use bsdinstall in my workstation which use zfs on root partition, but it's uncommon usecase.

I've reported this to Devin some time ago, could you tell something? Maybe Allan?
Comment 2 fre.fbsdpr 2015-12-21 17:52:31 UTC
Then, how about iterating over filesystems under $ZFSBOOT_POOL_NAME?
Comment 3 Kamil Czekirda freebsd_committer 2015-12-22 22:00:12 UTC
Revision with 'zfs umount -a' created:
Comment 4 Allan Jude freebsd_committer 2015-12-23 20:27:53 UTC
I think you want to use:


To only unmount anything mounted under /mnt

Also, you should first check if any ZFS was actually used, as running a zfs command for the first time loads the ZFS kernel module, and you don't want to do that if the user just did a ufs only install
Comment 5 Kamil Czekirda freebsd_committer 2015-12-29 22:22:50 UTC
Revision updated, any ideas for optimalization?
Comment 6 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:41:25 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
- Untouched since 2018-01-01.
- Affects Base System OR Documentation


Reset to open status.

I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.