Nicolas Williams wrote:
On Wed, Apr 21, 2010 at 01:03:39PM -0500, Jason King wrote:
ISTR POSIX also doesn't allow a number of features that can be turned
on with zfs (even ignoring the current issues that prevent ZFS from
being fully POSIX compliant today). I think an additional option for
the snapdir property ('directory' ?) that provides this behavior (with
suitable warnings about posix compliance) would be reasonable.
I believe it's sufficient that zfs provide the necessary options to
act in a posix compliant manner (much like you have to set $PATH
correctly to get POSIX conforming behavior, even though that might not
be the default), though I'm happy to be corrected about this.
Yes, that's true. But you couldn't rely on this behavior, whereas you
can rely on dataset roots having .zfs. If you're going to script this,
then you'll want to rely on the current (POSIX-compliant) behavior.
This isn't about scripting, it's about users. For a user to self-restore
a "whoops" deletion, she needs to:
sd="$PWD"
while ! test -d "$sd"/.zfs/snapshot; do sd="${sd%/*}; done
if test -n "$sd"; then
echo "Snapshots are in $sd/.zfs/snapshot"
else
echo "No snapshot dir found"
fi
Which is so user hostile the SA gets a call/email/ticket to do it for them.
And what happens if the root of the ZFS filesystem isn't even NFS
mounted? User home dirs, for example, where we don't make every home dir
its own zfs? There is no .zfs dir, so...
--
Carson
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
