> The other option is to allow users to this by doing operations in the > special ".zfs" directory. This should even be possible over NFS or CIFS. > For example creation, rename and delete of snapshots using normal file > system tools, in .zfs/snapshot. > > mv seems to be able to rename a snapshot. Maybe we could have cp on a > snapshot mean clone eg: > $ cd .zfs/snapshot > $ mv foo bar > $ cp bar baz > $ rm may > > Would rename the snapshot called foo to the snapshot called bar > It would then create a clone called baz based on the snapshot bar. > Finally removing the snapshot called may.
I had replied to another post about this but didn't see any responses. Is this behavior of being able to manipulate the snapshots through normal file commands documented somewhere? While it's cool, I'm a little suspicious that something I might create to guard against file system accidents (a snapshot) can itself be destroyed by an accidental file system access, not an explicit ZFS command. I also don't quite understand why snapshot manipulation works via files only in some situations and not in others. # zfs snapshot zpool/[EMAIL PROTECTED] # zfs snapshot zpool/[EMAIL PROTECTED] # cd /zpool/test/.zfs/snapshot # ls snap1 a b c d e # ls -l snap2 total 5 -rw-r--r-- 1 root root 0 May 10 15:37 a -rw-r--r-- 1 root root 0 May 10 15:37 b -rw-r--r-- 1 root root 0 May 10 15:37 c -rw-r--r-- 1 root root 0 May 10 15:37 d -rw-r--r-- 1 root root 0 May 10 15:37 e # rmdir snap1 snap2 rmdir: directory "snap2": Directory is a mount point or in use # zfs destroy zpool/[EMAIL PROTECTED] # Why can snap1 be removed directly but snap2 cannot? Thanks. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
