Re: Filesystem holes

[Matt Dillon]

:
:Presumably writing into these holes repeatedly is a none-too-efficient 
:affair (requiring moving all the stuff on either side), or am I missing the 
:point slightly?
:
:Dave :)

    It isn't quite that bad, but it isn't a walk in the park either.
    Since data blocks are referenced from a block table, inserting new
    blocks is cheap.  However, this means that data may not be physically
    ordered in the file -- if your read crosses a block boundry it may require
    an extra seek.  FreeBSD's FFS does have the reallocblks feature turned
    on and this will cause the filesystem to try to reorder nearby blocks,
    but it was never designed to handle sparse files so....

                                                -Matt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message