summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authorpjd <pjd@FreeBSD.org>2012-09-23 20:12:10 +0000
committerpjd <pjd@FreeBSD.org>2012-09-23 20:12:10 +0000
commit212634d921b6016d77a964b0299d6df7a93aacc1 (patch)
tree0772e4df508e44f9ca88d1971c54fb2acb4e2d85 /lib/libc
parent462a1240363ef90831d9b6cf6d345fc3c6e2ee0d (diff)
downloadFreeBSD-src-212634d921b6016d77a964b0299d6df7a93aacc1.zip
FreeBSD-src-212634d921b6016d77a964b0299d6df7a93aacc1.tar.gz
It is possible to recursively destroy snapshots even if the snapshot
doesn't exist on a dataset we are starting from. For example if we have the following configuration: tank tank/foo tank/foo@snap tank/bar tank/bar@snap We can execute: # zfs destroy -t tank@snap eventhough tank@snap doesn't exit. Unfortunately it is not possible to do the same with recursive rename: # zfs rename -r tank@snap tank@pans cannot open 'tank@snap': dataset does not exist ...until now. This change allows to recursively rename snapshots even if snapshot doesn't exist on the starting dataset. Sponsored by: rsync.net MFC after: 2 weeks
Diffstat (limited to 'lib/libc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud