> Steve Lord wrote:
> > The freeze was a raid5 specific thing, and the only way out of it at
> I assume you mean software RAID5, right? I've got a RAID50 array: 2 8-port
> 3ware cards in hw raid5, then those two devices combined software raid0. I
> didn't bother to make the log on a separate device, but I could, if need be.
Yes, software raid5, this should not be an issue for hardware raid - unless
it is broken....
> > this kernel revision is to use an external log device with raid5. You
> > must also make sure to use an inode size larger than the default with
> > a filesystem this big (mkfs ... -i size=512 ...). Without getting to
> > technical, this will stop your inode numbers from overflowing 32 bits.
> > >
> > > Now there's rumors on l-k that the FS size might be limited by the
> > > signedness of something in the block layer, effectively limiting us to 1T
> > We appear to have people working successfully beyond the 1Tbyte boundary,
> > the 1Tb limit may be specific to some device drivers which are not as
> > cleanly coded.
> I haven't been terribly happy with the 3ware drivers/cards in general, so
> we'll see. FWIW, I tried upgrading to their latest driver on an smp system
> and simply insmod-ing the newly compiled driver tickles the NMI watchdog
> which dumps me directly into kdb. Fun stuff. :-/
> Dan Yocum
> Sloan Digital Sky Survey, Fermilab 630.840.6509
> yocum@xxxxxxxx, http://www.sdss.org
> SDSS. Mapping the Universe.