Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: vnd cgd disks don't mark underlying file as modified

On Mon, Oct 06, 2008 at 06:59:04AM -0400, Greg Troxel wrote:
> "Steven M. Bellovin" <> writes:
> > I have a vnd+cgd file system.  Even if I write to it, the underlying
> > file is not marked as modified, and hence is not backed up by
> > incremental dumps.  This strikes me as a bug.  (This is amd64-current.)
> I think it's just a vnd bug, not a vnd+cgd bug - I have the same issue
> with the backing files for vnds exported from dom0 to a domU.
> A tricky question is if the mtime should change on every write, instead
> of just at close.

Our standard mtime policy is to flag the file as needs-mtime-update, and 
then whenever anyone looks, we update the time. This degenerates to 
update-on-close if no one looks.

However this really should be handled by the underlying file system, 
shouldn't it?

Take care,


Attachment: pgpkA6O0ED1Po.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index