Chris Mason wrote:
>
> On 9/5/00, 5:26:29 AM, Daniel Phillips wrote
> >
> > ...as it stands, a valuable piece of
> > information - the previous size of the file - is getting stepped on
> > just before inode->i_op->truncate(inode) gets called. This leads to
> > some messy posturing if you need to know the old size before going to
> > the new size.
>
> I'm not against sending the old size, it could be useful. But, your
> truncate operation wants to find the old size on its own. If the data in
> the on disk stat data is at all out of date (likely if you allow the
> dirty inode list to do your inode flushing, and have a crash) you need to
> find the real size of the file before truncating it.
OK, let's go nice n slow here... Now, what is the real size of a
file? To me, it's the size that the inode cache thinks it is, and
that supercedes what's on disk. Surely I can count on (struct inode
*) inode->i_size to tell me the size of my file?
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
