zfs mounted filesystem doesn't show up

Rob Rati lists at midsummerdream.org
Sun Mar 6 18:05:59 UTC 2016


No, I'm not using -u in receive.  Here's the command I use to receive:

/sbin/zfs recv -F -d pool

To send, I'm doing a 

/sbin/zfs send -i <snapshot> <snapshot>

Result of zfs get mounted... command is the same before and after I remount.
before:
NAME               PROPERTY    VALUE               SOURCE
pool/host/root  mounted     yes                 -
pool/host/root  canmount    on                  default
pool/host/root  mountpoint  /pool/host/root  default

after:
NAME               PROPERTY    VALUE               SOURCE
pool/host/root  mounted     yes                 -
pool/host/root  canmount    on                  default
pool/host/root  mountpoint  /pool/host/root  default

I'm not using jails.

Rob

On Mar 4, 2016, at 10:29 AM, Matthew Seaman wrote:

> On 2016/03/04 13:55, Rob Rati wrote:
>> I have 2 systems running zfs, and one back up to the other by taking
>> a snapshot and sending it to the other.  The data and snapshot
>> information all appear in the 2nd system, but the directories aren't
>> accessible from the command line despite being mounted.  If I do a
>> mount I see this:
>> 
>> pool/host/root on /pool/host/root (zfs, local, nfsv4acls)
>> 
>> But I can't list or cd into /pool/host/root.  However, if I zfs
>> umount /pool/host/root then zfs mount /pool/host/root everything is
>> fine and I can see the data.  This seems to be occurring every time
>> the first system backs up to the second.
> 
> Are you by any chance using the -u flag for zfs receive ? Probably not,
> but it's best to rule out the simple things...
> 
> What exactly are the commands you're issuing to do the whole zfs send
> ... | zfs receive ... process?  What's the result of:
> 
>   zfs get mounted,canmount,mountpoint zroot/whatever
> 
> both on the freshly received (inaccessible) copy of the zfs and after
> you've remounted it?  Are there jails involved here, and are you doing
> anything with the zfs jailed property?
> 
> 	Cheers,
> 
> 	Matthew
> 
> 
> 
> 



More information about the freebsd-questions mailing list