Date: Sat, 13 Jan 2007 00:57:51 -0800 (PST) From: "R. B. Riddick" <arne_woerner@yahoo.com> To: CyberLeo Kitsana <cyberleo@cyberleo.net> Cc: FreeBSD Geom <freebsd-geom@freebsd.org> Subject: Re: geom_raid5 livelock? Message-ID: <835894.31143.qm@web30309.mail.mud.yahoo.com> In-Reply-To: <45A830CE.2050506@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--- CyberLeo Kitsana <cyberleo@cyberleo.net> wrote: > R. B. Riddick wrote: > http://home.cyberleo.net/cyberleo/workspace/Zip/graid5-all.log > > That log contains two full seconds of requests, under the same > circumstances as before (rsync and find processes stuck in wait, along > with an 'ls' or two). If you need more, I can produce it. > > It appears to be completing requests, but always the same requests over > and over. Watching the log for about a minute doesn't show any other > requests during this time. > > [start] raid5/raid5[READ(offset=779825545216, length=16384)] > [start] raid5/raid5[READ(offset=764410200064, length=16384)] > Hmm... Thats strange... Possibly there happens an ENOMEM error, which would explain the repititions... A further debug line (it is again at debug level 2) before the current line 1165 (inside the inbed==children IF but in the end of it): G_RAID5_LOGREQ(bp, "[ready err%d cmp%jd]", obp->bio_error, obp->bio_completed); Or turn on "bootverbose"... For better data safety (e. g. in case of a power loss), I would recommend to reduce kern.geom.raid5.wdt to 0 or 1 (the lower the safer). For less memory consumtion I would use lower values for .maxmem and for .maxwql... -Arne ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?835894.31143.qm>