On Mon, Feb 19, 2001 at 08:34:36PM +0000, Malcolm Beattie wrote:
> Luka Renko writes:
> > > From: Malcolm Beattie [mailto:[EMAIL PROTECTED]]
> > > How safe is it to have a faked i_size in an inode? The only process
> > > to get an actual open descriptor on such an inode will be the
> > > migration daemon (which will be privileged, of course) but it would
> > > be nice to know how horribly things could break if it did things
> > > other than write() data to the underlying file.
> > You could just create sparse file instead. You just truncate the file,
> > lseek() to original size and write a single byte.
>
> Nice idea. It does restrict the underlying filesystem used (although
> I was only going to start with ext2 and other decent filesystems anyway
> which can all do sparse files). But it saves any potential nastiness
> about fake i_size behaviour so I think it's worth it.
Surely sparse files are a proof-of-concept that it's fine to have a faked
i_size?
--
Revolutions do not require corporate support.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
