Olivier Mueller wrote:
fsck_ufs: cannot alloc 94208 bytes for inoinfo
This is what I get after about one hour while trying a fsck on a large
(1.4TB) partition broken since a power outage.
HW: HP DL380G5, under freebsd 6.1/i386, with 1GB of RAM and:
Your fsck will need roughly 1
fsck's memory usage is directly related to the number of inodes and
the number of directories in the filesystem. Directories are
particularly memory intensive.
I've found on my backup system that a UFS1 filesystem with 40 million
inodes is about the limit that can be
On Wed, Feb 27, 2008 at 11:53:01AM -0800, Matthew Dillon wrote:
You can also reduce fsck time by reducing the number of cylinder
groups on the disk. I usually max them out (-c 999 and newfs then
sets it to the maximum, usually in the 50-80 range). This will
improve
Hello,
fsck_ufs: cannot alloc 94208 bytes for inoinfo
This is what I get after about one hour while trying a fsck on a large
(1.4TB) partition broken since a power outage.
HW: HP DL380G5, under freebsd 6.1/i386, with 1GB of RAM and:
da0: COMPAQ RAID 5 VOLUME OK Fixed Direct Access SCSI-4
* Olivier Mueller [EMAIL PROTECTED] [080226 14:32] wrote:
Hello,
fsck_ufs: cannot alloc 94208 bytes for inoinfo
This is what I get after about one hour while trying a fsck on a large
(1.4TB) partition broken since a power outage.
HW: HP DL380G5, under freebsd 6.1/i386, with 1GB of RAM
