Re: kern/41215: cannot load miniroot as kmod, kernel heap full

[David Laight <david%l8s.co.uk@localhost>]

The following reply was made to PR kern/41215; it has been noted by GNATS.

From: David Laight <david%l8s.co.uk@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost, salo%Xtrmntr.org@localhost
Subject: Re: kern/41215: cannot load miniroot as kmod, kernel heap full
Date: Sat, 18 Apr 2009 15:03:00 +0100

 On Thu, Apr 16, 2009 at 10:50:04PM +0000, Lubomir Sedlacik wrote:
 > The following reply was made to PR kern/41215; it has been noted by GNATS.
 > 
 > From: Lubomir Sedlacik <salo%Xtrmntr.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: kern/41215: cannot load miniroot as kmod, kernel heap full
 > Date: Fri, 17 Apr 2009 00:49:00 +0200
 > 
 >  On Thu, Apr 16, 2009 at 06:40:03AM +0000, David Laight wrote:
 >  >  What is the filesystem block size ?
 >  >  Possibly the file code is leaking a large buffer.
 >  >  (It hadn't used to matter since only 1 file was ever processed)
 >  
 >  4096 bytes, according to dumpfs.
 
 That sounds like the fragment size - giving a block size of 32k,
 rather than the more likely defaults of 1k and 8k.
 The standalons fs code allocates block sized buffers for allocation
 maps and (IIRC inodes), so I'd guess it isn't freeing them.
 
 It ought to be possibly to only need disk block sized buffers - which
 is also necessary in order to load /boot from a fs with large blocks.
 But that requires a full understanding of the fs layout which isn't
 obvious from the current #defines.
 
        David
 
 -- 
 David Laight: david%l8s.co.uk@localhost