Scott Long wrote: > 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. it's about right.. I've fsck'd 1TB filesystems and I think it depends on what blocksize you use etc. but I think it's about 700MB per TB for 16KB blocksize. it'd be good to set the result of a ulimit command > > > 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_at_freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe_at_freebsd.org" >>> >>> >> >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe_at_freebsd.org" >Received on Fri Jul 23 2004 - 17:59:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:03 UTC