>Number: 181235 >Category: kern >Synopsis: zfs block devices not appearing after zfs recv >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Aug 12 05:20:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Christopher Harrison >Release: 9.1-RELEASE >Organization: >Environment: # uname -a FreeBSD s1 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 [email protected]:/usr/obj/usr/src/sys/GENERIC amd64
>Description: When using zfs send of snapshots I am recieving the stream into a zfs recv pipe "zfs send -R ... | ssh test1 "zfs recv -vF -d ..." The problem occurs if I want to use the newly received zfs block device after the receive completes. The data is shown as completed. The zfs send stream show complete. zfs get all lists the proper sizes and info for the newly created data set. However the /dev/zvol/... device is not there. The only way I have been able to force the zfs block device to be exposed to the /dev file tree is through a zpool export, zpool import. Otherwise the zfs block dev is not accessible nor available though the normal block devfs. >How-To-Repeat: create a zpool create a zfs block dev (zfs create -V 10G -b 4k z/volumes/test123 ) snapshot the zfs block dev (zfs snapshot z/volumes/test123@201308010) zfs send the snapshot (zfs send -R z/volumes/test123@201308010 | ssh mytest "zfs recv -vF -d ztest" Let the zfs send/recv complete try to access the newly received zfs block dev (ls -la /dev/zvol/ztest/volumes/test123, no found). >Fix: >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
