hello again
i think there is a mechanism i can use to do this.
the file system doesn't look at the blocks table when processes are trying
to access an offset in the file, but in the file size which i can change
to zero in the beginning and later update it every time i write a quantum.
at the moment we are going to lock files until all the blocks were
written.
i might try the above mentioned hack later
/gaby
regards
Benhanokh Gabriel
-----------------------------------------------------------------------------
"If you think C++ is not overly complicated, just what is a
protected abstract virtual base class with a pure virtual private destructor,
and when was the last time you needed one?"
-- Tom Cargil, C++ Journal, Fall 1990. --
On Sun, 7 May 2000, Stephen C. Tweedie wrote:
> Hi,
>
> On Sun, May 07, 2000 at 01:21:54PM +0300, Benhanokh Gabriel wrote:
>
> > No process will ever get to read those blocks.
>
> No? What is to prevent a process from reading a block which has been
> allocated but not written? There is nothing in the ext2 filesystem
> format which lets you distinguish between written and unwritten blocks:
> all you can tell is if a block is allocated or not.
>
> --Stephen
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun May 07 2000 - 21:00:20 EST