Dmitry Morozovsky wrote:
On Mon, 26 Jun 2006, Eric Anderson wrote:
EA> > turning on bootverbose reveals additional info to
EA> > ad10: FAILURE - out of memory in start
EA> >
EA> > under load this machine (5 ata disks, most of their space allocated for 2
EA> > graid3's) many messages like
EA> >
EA> > ENOMEM 0xc6e834a4 on 0xc493c080(ad8)
EA> > ENOMEM 0xc703fdec on 0xc4960480(ad10)
EA> > ENOMEM 0xc6b49528 on 0xc4901400(ad0)
EA> > ENOMEM 0xc6c378c4 on 0xc493ca80(ad4g)
EA> > ENOMEM 0xc662b210 on 0xc4900b00(ad0f)
EA> > ENOMEM 0xc6b33630 on 0xc493c380(ad4)
EA> > ENOMEM 0xc7320d68 on 0xc4901400(ad0)
EA> > ENOMEM 0xc6bd6948 on 0xc493c380(ad4)
EA> > ENOMEM 0xc7299dec on 0xc493c200(ad6)
EA> > ENOMEM 0xc6d91528 on 0xc495f700(ad6g)
EA> > ENOMEM 0xc47b07bc on 0xc4960480(ad10)
EA> > ENOMEM 0xc7c22bdc on 0xc493c080(ad8)
EA> >
EA> > Machine is rather stable; however, it panics two or three times on /ftp:
EA> > bad dir ino 3454117 at offset 444: mangled entry
EA> > panic: ufs_dirbad: bad dir
EA> >
EA> > Any hints to debug?
EA>
EA> Are you sure the filesystem is clean? Can you try unmounting it, and
EA> running an fsck_ffs on it? Also, I think this has been discussed before on
EA> freebsd-geom@, did you check the archives?
Well, these two may not be linked together. (fsck does not report any errors
though)
As to ENOMEM/no memory in start, I'm fairly sure machine is not in generic
memory-shortage; and, these errors are generated only on machine with graid3.
What does your kernel config look like? Are you using (or did you ever
use) extended attributes on this fs?
Eric
--
------------------------------------------------------------------------
Eric Anderson Sr. Systems Administrator Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
