Date: Fri, 23 Jul 2004 13:54:22 -0600 From: Scott Long <scottl@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org Subject: Re: Can't check large FS Message-ID: <41016CEE.6060806@freebsd.org> In-Reply-To: <41016BFC.5000708@elischer.org> References: <200407231632.i6NGWoeO084976@gate.multicom.lv> <41016BFC.5000708@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't know if I agree with that. I've fsck'd 1.9TB filesystems with no problem. 770MB is quite a bit to be allocating. Doug might be right about checking an alternate superblock. Scott Julian Elischer wrote: > the process needs to be able to allocate more RAM. > probably you need to increase its data limit. > > > Andris wrote: > >> Hi, >> >> I have a PC running 5.2.1-p9 with Promise SX6000 RAID and six 300Gb >> Maxtor >> HDD's configured as RAID 0+1 so the total FS size is about 850 Gb. >> >> After hardware failure and rebuilding array I can't check my FS, fsck >> always >> dump core with the message: >> >> cannot alloc 775104816 bytes for inoinfo >> fsck: /dev/pst0s1d: Segmentation fault >> >> >> Andris >> >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" >> >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41016CEE.6060806>