Date: Fri, 10 Nov 1995 18:03:45 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> To: Terry Lambert <terry@lambert.org> Cc: current@FreeBSD.org Subject: Re: Filesystem becomes unstable in -current :-( Message-ID: <CtHdsemCq3@ache.dialup.demos.ru> In-Reply-To: <199511091837.LAA29380@phaeton.artisoft.com>; from Terry Lambert at Thu, 9 Nov 1995 11:37:01 -0700 (MST) References: <199511091837.LAA29380@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199511091837.LAA29380@phaeton.artisoft.com> Terry Lambert
writes:
>> I saw one panic in disksort() and dead process hang on
>> "getblk" channel, I never got them before -current...
>Are you using the async stuff?
No.
>Are you mounting read only, but attempting a write?
No.
>I think either of these might result in your problem, given recent patches.
It seems that integration of async stuff broke normal stuff somehow :-(
I restore my 10 days old kernel and all works right again.
It looks like the same problem which manifistated in 3 states:
1) Singe process hangs in "getblk". No signal reactions occurse.
If I attempt to read the same blocks from other process, first
one unhangs.
2) All process which attemts to read/write UFS hangs forever.
3) Disksort panic.
--
Andrey A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CtHdsemCq3>