dude, i just explained it =) ok...let me see if i can do better...
if you have a file that's 1 gb , in zfs you have those blocks added. on a normal filesystem when you edit the file or add to it, it will erase the old file and add a new one over it (more or less). on zfs, you have the blocks added just liek when you first add them on antoher system, but when you edit it and change it, it doesn't erase the file and add the "changed" file, it adds JUST what is different. because of this, both "copies" of the file exist (the old one + blocks referencing what has changed) now, a snapshot, is a point in time COPY of what THIS looks like....so, when files CHANGE, snapshots GROW, not always BASED on the size of the files, but on the size of how different things are...does this make more sense? then when you DELETE a file or something, all of those original changes are still referenced in snapshots....so the more snapshots you have, and the MORE things change, the MORE SPACE you're going to take up.... On Tue, Aug 18, 2009 at 12:04 PM, Matthew Stevenson < no-re...@opensolaris.org> wrote: > I do understand these concepts, but to me that still doesn't explain why > adding the size of each snapshot together doesn't equal the size reported by > zfs list in USEDSNAP. > > I'm clearly missing something. Hmmm... > -- > This message posted from opensolaris.org > _______________________________________________ > 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
