Summary: 12TB GEOM stripe, newfs, then fsck: cannot alloc 768053748 bytes for blockmap

2005-06-09 Thread Frantisek Rysanek
Thanks a lot to Mr. Zbyslaw. Being too lazy myself to fiddle with the soft limit via the shell or bootloader, I did the following in the kernel build config file: options MAXDSIZ=(1024UL*1024*1024) options DFLDSIZ=(1024UL*1024*1024) This way, fsck works just fine. To address

Re: Summary: 12TB GEOM stripe, newfs, then fsck: cannot alloc 768053748 bytes for blockmap

2005-06-09 Thread Frantisek Rysanek
On 9 Jun 2005 at 9:46, Alex Zbyslaw wrote: A local friend has suggested to increase the block size It ought also make sense if you are serving up *large* files (didn't you say video/audio?). ... I don't have anything on your scale (23Gb of document database pales into insignificance

12TB GEOM stripe, newfs, then fsck: cannot alloc 768053748 bytes for blockmap

2005-06-08 Thread Frantisek Rysanek
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).