On 5/24/06, Jeremy Teo <[EMAIL PROTECTED]> wrote:
Hello,
with reference to bug id #4852821: user undo
I have implemented a basic prototype that has the current functionality:
1) deleted files/directories are moved to /your_pool/your_fs/.zfs/deleted
Unfortunately, it is non-trivial to completely reproduce the namespace
of deleted files: for now, deleting "/foo/bar" will result in
".zfs/deleted/bar".
2) As a result of 1, deleted files move out of .zfs/deleted in FIFO.
Ie. if you remove /foo/bar twice, the most recent copy will be the one
remaining in .zfs/deleted.
3) If another user deletes /foo/bar, and you try to delete /foo/bar,
you will be denied permissions. Again, this is due to namespace
clashes.
how about changing the name of the file to uid or username-filename
this atleast gets you the ability to let each user the ability to
delete there own file, shouldn't be much work. Another possible
enhancement would be adding anything field in stat(stat) in the files
name after its deleted. This would be set per filesystem. mod, uid,
username(the code should do the conversion), gid, size, mtime and just
parse a format string like $mtime-$name.
James Dickens
uadmin.blogspot.com
I'm leaning towards completely reproducing the namespace, but would
like to get a feel for whether the benefits outweigh the code
complexity. Advice would be appreciated.
Also, I presume I can request-sponsor for 4852821 and get someone from
the zfs team to mentor me?
Thanks again for all your time. :)
--
Regards,
Jeremy
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
