Date: Sat, 10 Aug 2002 15:23:54 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: bhlewis@wossname.net, freebsd-current@FreeBSD.ORG, bde@freebsd.org Subject: Re: Is anyone else having trouble with dump(8) on -current? Message-ID: <20020810152354.470317e4.Alexander@Leidinger.net> In-Reply-To: <200208100007.aa02493@salmon.maths.tcd.ie> References: <200205141034.g4EAYCJr024857@Magelan.Leidinger.net> <200208100007.aa02493@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Aug 2002 00:07:28 +0100 Ian Dowse <iedowse@maths.tcd.ie>
wrote:
> I was just looking at PR bin/18319 when I remembered this message.
> Many of the changes in your patch are not necessary I believe, as
> read(2) will restart after a signal by default. How about just
> fixing the open call that actually triggers the reported error? I
> suspect that many of the other cases are either impossible or
> extremely unlikely in practice. Could someone who can reproduce the
> "couldn't reopen disk" error try the following?
Have a look at Message-ID: <20020606063157.V8685-100000@gamplex.bde.org>
(should be in the archive of audit).
Short: open shouldn't be able to return EINTR in practice...
My assumptions:
- Bruce hasn't made a mistake
- something broke in the kernel (either for a "short" period of
time, or it's still broken), so we should look for the real
problem instead
Bye,
Alexander.
--
Intel: where Quality is job number 0.9998782345!
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020810152354.470317e4.Alexander>