Hi all, I want to backup a pool called mpool. I want to do this by doing a zfs send of a mpool snapshot and receive into a different pool called bpool. All this on the same machine. I'm sharing various filesystems via zfs sharenfs and sharesmb. Sending and receiving of the entire pool works as expected, including incremental updates. After exporting and importing bpool all shares get activated. All nfs shares get duplicated albeit with a different root. But the cifs shares really get duplicated. Looking at the output from sharemgr the share from bpool, which got mounted last, got precedence over the real share. What I want is a second pool which is a copy of the first including all properties. I don't want to turn turn off sharing by setting sharenfs and sharesmb to off. Because when I need to restore the pool I also need to set all the sharing properties again. Currently I use the following strategy: # zpool create -m none -O canmount=noauto bpool c5t15d0 c5t16d0 # zfs snapshot -r tp...@00 # zfs send -R tp...@00 | zfs recv -vFud bpool # zfs set canmount=noauto [each filesystem in bpool] # zpool export bpool # zpool import bpool After the import of bpool no extra shares in sharemgr and all properties still intact except the canmount property.
Can I either send or receive the canmount=noauto property? (PSARC/2009/510) I know that I need at least version 22 for that. I tried it on a b134 with version 22 pools but couldn't get it to work. How can I prevent mounting filesystems during zpool import? I know how to mount it on a different root that doesn't solve my problem. Why can't the canmount zfs property be inherited? Any suggestion and / or strategy to accomplish will be more than welcome. Thank you for your interest and time, Frederik -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
