Rudolf Potucek wrote:
It seems like the appropriate solution would be to
have a tool that
allows removing a file from one or more snapshots
at the same time as
removing the source ...
That would make them not really snapshots. And such
a tool would have
to "fix" clones too.
While I concur that being able to remove files from snapshots is somewhat
against the concept behind snapshots, I feel that there is a tradeoff here for
the administrator:
Let's say we accidentally snapshotted a very large temporary file. We don't
need the file and we don't need its snapshot. Yet the only way to free the
space taken up by this accidentally snapshotted file is to delete the WHOLE
snapshot, including all the files of which snapshots may be required. To
paraphrase: that would make this snapshot not really a snapshot ANYMORE.
At this point having a separate tool that allows you to do "spring cleaning"
and deleting files from snapshots would quite possibly be more in the spirit of
snapshotting than having to delete snapshots.
Just my $.02,
Rudolf
NO. Snapshotting is sacred - once you break the model where a snapshot
is a point-in-time picture, all sorts of bad things can happen. You've
changed a fundamental assumption of snapshots, and this then impacts how
we view them from all sorts of angles; it's a huge loss to trade away
for a very small gain.
Should you want to modify a snapshot for some reason, that's what the
'zfs clone' function is for. clone your snapshot, promote it, and make
your modifications.
--
Erik Trimble
Java System Support
Mailstop: usca22-123
Phone: x17195
Santa Clara, CA
Timezone: US/Pacific (GMT-0800)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
