On Wed, Jun 15 at 7:29, Edward Ned Harvey wrote:
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Richard Elling
That would suck worse.
Don't mind Richard. He is of the mind that ZFS is perfect for everything
just the way it is, and anybody who wants anything different should adjust
their thought process.
Richard, just because it's not something you want, doesn't mean you should
rain on somebody else's parade. If Simon wants something like that, kudos
to him.
I know I've certainly had many situations where people wanted to snapshot or
rev individual files everytime they're modified. As I said - perfect
example is Google Docs. Yes it is useful. But no, it's not what ZFS does.
suck worse = every single file would show a snapshot version for every
change anywhere in the filesystem, not just the changes unique to that file.
Imagine scrolling through a few hundred thousand snapshots in the
windows "old version" dialog because your 5000 files were getting
edited 2-3 times/day for a month. Imagine trying to parse the results
of 'zfs list -t snapshot'. Picture the disaster of that system in 5
years of operation.
IMO, this problem begs for one of today's content management systems
plus 10 minutes of training on how to use it effectively. Save the
snapshotting for the periodic backup of the CMS system and/or users's
systems. Sure, map work areas via NFS or CIFS, and give them a
time-machine like picture of history for that work area (hourly for a
day, daily for a week, weekly for a month, monthly for a year, etc.)
--eric
--
Eric D. Mudama
edmud...@bounceswoosh.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
