Actually, if your zfs filesystem has snapshots zfs will complain that the fs
can't be destroyed (or that you have to use the -f switch to force it). So
the first thing I do when making a new filesystem is create a snapshot to
protect me from destroying a filesystem :)
On 5/21/07, Peter Schuller <
> On the other hand personally I just don't see the need for this since
> the @ char isn't special to the shell so I don't see where the original
> problem came from.
I never actually *had* a problem, I am just nervous about it. And yes, @
is not special for classical shells, but it's still more s
Chris Gerhard wrote:
You are not alone.
My preference would be for an optional -t option to zfs destroy:
zfs destroy -t snapshot tank/[EMAIL PROTECTED]
or
zfs destroy -t snapshot -r tank/fs
would delete all the snapshots below tank/fs
I agree since that would fit nicely with the existin
ZFS can make for complicated environments. Your dog wants management
tools. :)
Seriously - We're adding all of these options to ZFS. Where are the
tools that let someone make an informed decision concerning what their
actions are going to do to the system? Where is the option that lets
someon
You are not alone.
My preference would be for an optional -t option to zfs destroy:
zfs destroy -t snapshot tank/[EMAIL PROTECTED]
or
zfs destroy -t snapshot -r tank/fs
would delete all the snapshots below tank/fs
This message posted from opensolaris.org
_
