Brian Behlendorf 608860b6d0 Delay before destroying loopback devices ... Generally I don't approve of just adding an arbitrary delay to avoid a problem but in this case I'm going to let it slide. We may need to delay briefly after 'zpool destroy' returns to ensure the loopback devices are closed. If they aren't closed than losetup -d will not be able to destroy them. Unfortunately, there's no easy state the check so we'll have to make due with a simple delay.		2011-06-03 14:38:25 -07:00
..
zpios-profile	Fix 'zfs set volsize=N pool/dataset'	2011-05-02 08:54:40 -07:00
zpios-test	Fix 'zfs set volsize=N pool/dataset'	2011-05-02 08:54:40 -07:00
zpool-config	Delay before destroying loopback devices	2011-06-03 14:38:25 -07:00
zpool-layout	Fix 'zfs set volsize=N pool/dataset'	2011-05-02 08:54:40 -07:00
common.sh.in	Call udevadm trigger more safely	2011-04-05 13:00:51 -07:00
Makefile.am	Remove spl/zfs modules as part of cleanup	2010-11-11 11:40:06 -08:00
Makefile.in	Fix 'zfs set volsize=N pool/dataset'	2011-05-02 08:54:40 -07:00
zconfig.sh	Update zconfig.sh to use new zvol names	2011-04-19 16:33:41 -07:00
zfault.sh	Remove partition from vdev name in zfault.sh	2010-11-29 10:53:53 -08:00
zfs.sh	Update 'zfs.sh -u' to umount all zfs filesystems	2011-02-16 11:10:31 -08:00
zpios-sanity.sh	Fix zpios-sanity.sh return code	2011-06-02 10:13:15 -07:00
zpios-survey.sh	Add linux zpios support	2010-08-31 13:42:01 -07:00
zpios.sh	Always unload zpios.ko on exit	2011-06-02 10:25:35 -07:00
zpool-create.sh	Add build system	2010-08-31 13:41:27 -07:00