Date: Tue, 27 Jun 2006 11:17:05 +0400 (MSD) From: Dmitry Morozovsky <marck@rinet.ru> To: Eric Anderson <anderson@centtech.com> Cc: hackers@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org> Subject: Re: ENOMEM @ RELENG_6 graid3 Message-ID: <20060627110802.X39639@woozle.rinet.ru> In-Reply-To: <44A01A6D.7030000@centtech.com> References: <20060626193005.U9063@woozle.rinet.ru> <44A01A6D.7030000@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Maybe volume size (slightly larged than 1T) is relevant as well: root@kucha:/pub/FreeBSD# graid3 list r0g Geom name: r0g State: COMPLETE Components: 5 Flags: ROUND-ROBIN GenID: 0 SyncID: 9 ID: 2611540979 Zone64kFailed: 35144 Zone64kRequested: 18641827 Zone16kFailed: 388 Zone16kRequested: 246907 Zone4kFailed: 19793 Zone4kRequested: 5651352 Providers: 1. Name: raid3/r0g Mediasize: 1118758531072 (1.0T) Sectorsize: 2048 Mode: r1w1e1 Consumers: 1. Name: ad0g Mediasize: 279689633280 (260G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY GenID: 0 SyncID: 9 Number: 4 Type: PARITY 2. Name: ad4g Mediasize: 279689633280 (260G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY GenID: 0 SyncID: 9 Number: 1 Type: DATA 3. Name: ad6g Mediasize: 279689633280 (260G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY GenID: 0 SyncID: 9 Number: 0 Type: DATA 4. Name: ad8g Mediasize: 279689633280 (260G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY GenID: 0 SyncID: 9 Number: 2 Type: DATA 5. Name: ad10g Mediasize: 279689633280 (260G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Flags: DIRTY GenID: 0 SyncID: 9 Number: 3 Type: DATA Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060627110802.X39639>