login
Header Space

 
 

Re: fsck large filesystem, memory limit problem

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Will <wg.mlist@...>
Cc: <misc@...>
Date: Monday, May 12, 2008 - 11:49 am

On Fri, May 09, 2008 at 11:16:28AM -0400, Will wrote:


OK, your filesystem indeed uses default block and fragment sizes. The
# of inodes is about 238M.

De fsck_ffs code allocates a number of arrays directly depending on
the # of indodes in setup(), totalling 4 bytes per inode. Some other
data is also needed, so it's not surprise you hit the 1G data space limit.

I can only conclude that the 2TB number I gave to Nick for the FAQ is
wrong, and should be 1TB. There might be some leeway there, but I
don't have the time to test now. I'll fix the FAQ.

	-Otto

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: fsck large filesystem, memory limit problem, David J. Stillman, (Thu May 8, 5:04 pm)
Re: fsck large filesystem, memory limit problem, Otto Moerbeek, (Fri May 9, 2:44 am)
Re: fsck large filesystem, memory limit problem, Otto Moerbeek, (Mon May 12, 11:49 am)
Re: fsck large filesystem, memory limit problem, Hannah Schroeter, (Mon May 19, 8:38 am)
Re: fsck large filesystem, memory limit problem, Ted Unangst, (Mon May 19, 4:20 pm)
Re: fsck large filesystem, memory limit problem, Otto Moerbeek, (Mon May 19, 9:00 am)
Re: fsck large filesystem, memory limit problem, Hannah Schroeter, (Mon May 19, 9:12 am)
Re: fsck large filesystem, memory limit problem, Otto Moerbeek, (Mon May 19, 9:48 am)
speck-geostationary