Date: Mon, 19 Jun 2017 09:51:47 -0700 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Christian Kujau <lists@nerdbynature.de> Cc: David Christensen <dpchrist@holgerdanske.com>, freebsd-questions@freebsd.org Subject: Re: zpool import -N mounts filesystems anyway Message-ID: <8294aeef-6399-cc5d-1d3d-ac1925430b05@bluerosetech.com> In-Reply-To: <alpine.DEB.2.21.1.1706182222130.3364@trent.utfs.org> References: <7f41df25-df2e-298e-d33e-cc95874e831c@bluerosetech.com> <eb778163-8387-fd55-8e8f-d65ec221e6e8@holgerdanske.com> <d4b055f2-2273-6df8-fe55-640f3b56e04d@bluerosetech.com> <alpine.DEB.2.21.1.1706182222130.3364@trent.utfs.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/18/2017 22:28, Christian Kujau wrote: > On Sun, 18 Jun 2017, Mel Pilgrim wrote: >> # zpool list backupA >> cannot open 'backupA': no such pool >> # zpool import -N backupA >> # zpool list backupA >> NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT >> backupA 696G 189G 507G - 1% 27% 1.00x ONLINE - >> # zfs list backupA >> NAME USED AVAIL REFER MOUNTPOINT >> backupA 189G 486G 22K /backup-ext/backupA > > Are you sure that the pool is actually mounted at this point? Yes, the root dataset (and only the root dataset) gets mounted: # zfs get -r canmount,mountpoint backupB NAME PROPERTY VALUE SOURCE backupB canmount noauto local backupB mountpoint /backup-ext/backupB local backupB/z0 canmount noauto local backupB/z0 mountpoint /backup-ext/backupB/z0 inherited from backupB # zpool export backupB # ls -l /backup-ext/backupB total 0 # zpool import backupB # ls /backup-ext/backupB z0 # zfs list -ro name,mounted,mountpoint backupB NAME MOUNTED MOUNTPOINT backupB yes /backup-ext/backupB backupB/z0 no /backup-ext/backupB/z0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8294aeef-6399-cc5d-1d3d-ac1925430b05>