Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Theodore Y. Ts'o
From: Daniel Phillips <[EMAIL PROTECTED]> Date:Fri, 01 Sep 2000 20:49:14 +0200 Curiously, this field is measured in 512 byte units, giving a 2TB Ext2 filesize limit. That's starting to look uncomfortably small - I can easily imagine a single database file wanting to be

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Daniel Phillips
Alexander Viro wrote: > > On Fri, 1 Sep 2000, Daniel Phillips wrote: > > > Linda Walsh wrote: > > > It may not matter too too much, but blocks are being passed around as > > > 'ints'. On the ia32 architecture, this implies a maximum of 512*2G->1T > > > disk size. Probably don't need to worry

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Alexander Viro
On Fri, 1 Sep 2000, Daniel Phillips wrote: > Linda Walsh wrote: > > It may not matter too too much, but blocks are being passed around as > > 'ints'. On the ia32 architecture, this implies a maximum of 512*2G->1T > > disk size. Probably don't need to worry about this today, but in a few > >

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Alan Cox
> What I'd like to add is: while we're at it, how about losing the 512 > byte magic multiplier and go with the filesystem block size? That way > Ext2 file size automatically goes up by a factor of 8 every time we > manage to double the filesystem block size (blocksize*2 and triple > indirect =>

512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Daniel Phillips
Linda Walsh wrote: > It may not matter too too much, but blocks are being passed around as > 'ints'. On the ia32 architecture, this implies a maximum of 512*2G->1T > disk size. Probably don't need to worry about this today, but in a few > years? Should we be changing the internal interfaces to

512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Daniel Phillips
Linda Walsh wrote: It may not matter too too much, but blocks are being passed around as 'ints'. On the ia32 architecture, this implies a maximum of 512*2G-1T disk size. Probably don't need to worry about this today, but in a few years? Should we be changing the internal interfaces to use

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Alan Cox
What I'd like to add is: while we're at it, how about losing the 512 byte magic multiplier and go with the filesystem block size? That way Ext2 file size automatically goes up by a factor of 8 every time we manage to double the filesystem block size (blocksize*2 and triple indirect = 2**3).

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Alexander Viro
On Fri, 1 Sep 2000, Daniel Phillips wrote: Linda Walsh wrote: It may not matter too too much, but blocks are being passed around as 'ints'. On the ia32 architecture, this implies a maximum of 512*2G-1T disk size. Probably don't need to worry about this today, but in a few years?

Re: 512 byte magic multiplier (was: Large File support and blocks)

2000-09-01 Thread Theodore Y. Ts'o
From: Daniel Phillips [EMAIL PROTECTED] Date:Fri, 01 Sep 2000 20:49:14 +0200 Curiously, this field is measured in 512 byte units, giving a 2TB Ext2 filesize limit. That's starting to look uncomfortably small - I can easily imagine a single database file wanting to be