Hi,
On Mon, 1 May 2000, Stephen C. Tweedie wrote:
> > Is it possible to have a gap between the super-block and the
> > start of group 0's metadata?
>
> Yes. It's called the "s_first_data_block" field in the ext2
> superblock, and lets you offset the data zone from the start of the
> filesyst
Hi all,
>> 2. Is fsync() supposed to sync all outstanding writes for that file
>>handle only, or for the inode that is referenced by it?
>
>>From SingleUnix:
>
>The fsync() function can be used by an application to indicate that
>all data for the open file description named by fildes
from fsync(). I
also have patches which try to implement fdatasync correctly on
ext2. If anyone could answer (some of) these questions it would really
help improving these.
Thanks,
Lennert Buytenhek
<[EMAIL PROTECTED]>
Hi,
the interested are invited to check out ext2resize
990711. Its about a hundred times faster now, so
it should actually be usable. It can be found at:
http://www.dsv.nl/~buytenh/ext2resize
Have fun
Lennert Buytenhek
<[EMAIL PROTECTED]>
Stephen Tweedie said:
>Hi,
>
>On Fri, 2 Jul 1999 10:58:27 -0600 (MDT), Andreas Dilger
><[EMAIL PROTECTED]> said:
>
>> I agree that reserving GDT blocks would be a small hack for v0 of ext2,
but
>> we could add a "COMPATIBLE" extension to v1 of ext2 that gave the number
of
>> GDT blocks reserved.
on't need to reserve more than 4 GDT blocks over what people
>already allocate in order to give them the normal expansion needs. If
>they need more expansion at a later date, they can unmount the FS and
>do block shuffling offline.
I just got an email from John Finlay saying he's got a 52GB fs with
6000+ block groups. So the 1024 block group limit is just bogus.
The header in question which #defined the max # of block groups
to be 1024 is wrong, then.
Lennert Buytenhek
