Nicolas Williams wrote:
On Mon, Dec 18, 2006 at 05:44:08PM -0500, Jeffrey Hutzelman wrote:
On Monday, December 18, 2006 11:32:37 AM -0600 Nicolas Williams
<[EMAIL PROTECTED]> wrote:
I'd say go for both, (a) and (b). Of course, (b) may not be easy to
implement.
Another option would be to warn the user and set a flag on the shared block
which causes it to be bleached when the last reference goes away. Of
course, one still might want to give the user the option of forcing
immediate bleaching of the shared data.
Sure, but if I want something bleached I probably want it bleahced
_now_, not who knows when.
I think there are two related things here, given your comments and
suggestions for a bleach(1) command and VOP/FOP implementation you are
thinking about a completely different usage method than I am.
How do you /usr/bin/bleach the tmp file that your editor wrote to before
it did the rename ? You can't easily do that - if at all in some cases.
I'm looking for the systemic solution here not the end user controlled one.
For comparison what you are suggesting is like doing crypto with
encrypt(1) it works on pathnames, where as what I'm suggesting is more
like ZFS crypto it works "inside" ZFS with deep intimate knowledge of
ZFS and requires zero change on behalf of the user or admin.
While I think having this in the VOP/FOP layer is interesting it isn't
the problem I was trying to solve and to be completely honest I'm really
not interested in solving this outside of ZFS - why make it easy for
people to stay on UFS ;-)
But why set that per-file? Why not per-dataset/volume? "Bleach all
blocks when they are freed" automatically means bleaching blocks when
the lask reference is gone (as a result of an unlink of the last file
that had some block, say).
I didn't have anything per file, but exactly what you said. The policy
was when files are removed, when data sets are removed, when pools are
removed.
--
Darren J Moffat
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
