ENOMEM @ RELENG_6 graid3

[Pawel Jakub Dawidek]

On Mon, Jun 26, 2006 at 07:34:51PM +0400, Dmitry Morozovsky wrote:
> Dear colleagues,
> 
> turning on bootverbose reveals additional info to 
> 
> ad10: FAILURE - out of memory in start
> 
> under load this machine (5 ata disks, most of their space allocated for 2 
> graid3's) many messages like
> 
> ENOMEM 0xc6e834a4 on 0xc493c080(ad8)
> ENOMEM 0xc703fdec on 0xc4960480(ad10)
> ENOMEM 0xc6b49528 on 0xc4901400(ad0)
> ENOMEM 0xc6c378c4 on 0xc493ca80(ad4g)
> ENOMEM 0xc662b210 on 0xc4900b00(ad0f)
> ENOMEM 0xc6b33630 on 0xc493c380(ad4)
> ENOMEM 0xc7320d68 on 0xc4901400(ad0)
> ENOMEM 0xc6bd6948 on 0xc493c380(ad4)
> ENOMEM 0xc7299dec on 0xc493c200(ad6)
> ENOMEM 0xc6d91528 on 0xc495f700(ad6g)
> ENOMEM 0xc47b07bc on 0xc4960480(ad10)
> ENOMEM 0xc7c22bdc on 0xc493c080(ad8)
> 
> Machine is rather stable; however, it panics two or three times on 
> /ftp: bad dir ino 3454117 at offset 444: mangled entry
> panic: ufs_dirbad: bad dir
> 
> Any hints to debug?

I hope ENOMEM errors are not related to your panic, because on ENOMEM
GEOM should repeat the request a bit later.

Will be good to know if you have simlar panics without graid3. For
example on a plain disk, but with 2kB sector size (you can do it with
gnop(8)). You can also try gstripe(8) your disks with small stripesize,
eg. 512 bytes and use gnop(8) on top of it to change sector size, so all
disks will be used, in case there is a problem with your controller.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20060627/d01ee4c9/attachment.pgp