Geoff Nordli
2012-Sep-13 19:58 UTC
[zfs-discuss] defer_destroy property set on snapshot creation
I am running NexentaOS_134f This is really weird, but I for some reason the defer_destroy property is being set on new snapshots and I can''t turn it off. Normally it should be enabled when using the zfs destroy -d command. The property doesn''t seem to be inherited from anywhere. It seems to have just started happening. Here are the steps showing how it works. Really, it is working as expected, but the property shouldn''t be set on creation. Create snapshot: root at grok-zfs1:~# zfs snapshot groklab/ws08r2-U2037 at 5 root at grok-zfs1:~# zfs get defer_destroy | grep U2037\@5 groklab/ws08r2-U2037 at 5 defer_destroy on - Create a clone: root at grok-zfs1:~# zfs clone groklab/ws08r2-U2037 at 5 groklab/test2 root at grok-zfs1:~# zfs list -t all | grep test2 groklab/test2 0 886G 11.6G - The snapshot is still there: root at grok-zfs1:~# zfs list -t all | grep U2037\@5 groklab/ws08r2-U2037 at 5 0 - 11.6G - Destroy the clone: root at grok-zfs1:~# zfs destroy groklab/test2 Snapshot is gone: root at grok-zfs1:~# zfs list -t all | grep U2037\@5 root at grok-zfs1:~# thanks, Geoff
Apparently Analagous Threads
- NFS/SATA lockups (svc_cots_kdup no slots free & sata port time out)
- SCSI write retry errors on ZIL SSD drives...
- stmf corruption and dealing with dynamic lun mapping
- msdfs root -- client error "refers to a location that is unavailable"
- Any options on crypt+zfs ?