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 device da0: 135.168MB/s transfers da0: 1430488MB (2929640988 512 byte sectors: 255H 63S/T 65535C) Mounting with option -f (force) seems to work, so I guess there is still hope :) Now I added this to the /boot/loader.conf: kern.maxdsiz="1073741824" # 1GB kern.dfldsiz="1073741824" # 1GB and I'm trying the fsck again, but I'm not sure it will help. Would you maybe have other suggestions? Regards, Olivier
* Olivier Mueller <om-lists-bsd@omx.ch> [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 and: > > da0: <COMPAQ RAID 5 VOLUME OK> Fixed Direct Access SCSI-4 device > da0: 135.168MB/s transfers > da0: 1430488MB (2929640988 512 byte sectors: 255H 63S/T 65535C) > > Mounting with option -f (force) seems to work, so I guess there is > still hope :) > > > Now I added this to the /boot/loader.conf: > kern.maxdsiz="1073741824" # 1GB > kern.dfldsiz="1073741824" # 1GB > and I'm trying the fsck again, but I'm not sure it will help. > > Would you maybe have other suggestions?See "limit/ulimit" to make sure you're giving the fsck process unlimited data size. you can also likely safely increase the maxdsiz to 1.5GB and still be ok, just make sure to turn on swapping. -Alfred
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 GB memory per 1 TB file
system size. That formular was posted some time ago on
the -fs mailing list. It only applies with the default
newfs parameters -- if you used other parameters (inode
density, bsize/fsize), fsck's memory requirements are
different.
> Now I added this to the /boot/loader.conf:
> kern.maxdsiz="1073741824" # 1GB
> kern.dfldsiz="1073741824" # 1GB
> and I'm trying the fsck again, but I'm not sure it will help.
Given the above formula, it's probably not enough, so you
might have to increase it further. Also make sure that
you have enough swap space.
If you have a spare box, it might be helpful to transplant
some RAM from it so fsck doesn't have to swap.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n-
chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"If you think C++ is not overly complicated, just what is a protected
abstract virtual base pure virtual private destructor, and when was the
last time you needed one?"
-- Tom Cargil, C++ Journal