12TB GEOM stripe, newfs, then fsck: cannot alloc 768053748 bytes
tshadwick at goinet.com
Wed Jun 8 14:33:41 GMT 2005
Just curious, what happens if you run the fsck with -f? Since it isn't
production I won't feel bad if it clobbers something. ;)
On Wed, 8 Jun 2005, Frantisek Rysanek wrote:
> Dear everyone,
> this is not an important issue, but I'd like to ask anyway,
> just in case the solution was obvious:
> I've bundled three 4TB RAID boxes using GEOM::stripe into a
> single 12TB volume. I didn't partition it, I just created UFS
> on it using newfs (a "dangerously dedicated" volume).
> This is not a production setup, I'm just testing the hardware.
> I thought "fsck" would be a plausible benchmarking tool.
> -bash-2.05b# fsck_ufs /dev/stripe/data
> ** /dev/stripe/data
> cannot alloc 768053748 bytes for blockmap
> ***** FILE SYSTEM MARKED DIRTY *****
> After a forced mount, the 12TB volume works fine. It just
> can't be fsck'ed.
> The machine is a dual Xeon/Nocona + i7520, with 2 GB of RAM,
> running FreeBSD 5.4-RELEASE with an SMP kernel.
> Any ideas are welcome :-)
> Frank Rysanek
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions