Hello, with the advent of clones and snapshots, one will of course start creating them. Which also means destroying them.
Am I the only one who is *extremely* nervous about doing "zfs destroy some/[EMAIL PROTECTED]"? This goes bot manually and automatically in a script. I am very paranoid about this; especially because the @ sign might conceivably be incorrectly interpreted by some layer of scripting, being a non-alphanumeric character and highly atypical for filenames/paths. What about having dedicated commands "destroysnapshot", "destroyclone", or "remove" (less dangerous variant of "destroy") that will never do anything but remove snapshots or clones? Alternatively having something along the lines of "zfs destroy --nofs" or "zfs destroy --safe". I realize this is borderline being in the same territory as special casing "rm -rf /" and similar, which is generally not considered a good idea. But somehow the snapshot situation feels a lot more risky. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
