Date: Tue, 24 Apr 2007 19:42:23 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-current@freebsd.org Cc: Ollivier Robert <roberto@keltia.freenix.fr>, current@freebsd.org, William Josephson <freebsd-current@morphisms.net> Subject: Re: ATA FLUSHCACHE Message-ID: <200704241942.40874.doconnor@gsoft.com.au> In-Reply-To: <20070424084409.GA98777@keltia.freenix.fr> References: <20070424051420.GA84831@mero.morphisms.net> <200704241554.12605.doconnor@gsoft.com.au> <20070424084409.GA98777@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tuesday 24 April 2007 18:14, Ollivier Robert wrote: > The main problem that I've found is that with a single disk > configuration, there is a timeout then the system recovers but with a > dual (or maybe more) disks involved, multiple/current timeouts make > the system panic and that is not nice. > > I suspect that changing the timeout may just hide the real problem. Hmm, it is a non fatal error for gjournal, I'm kind of surprised it's a fatal one for ZFS.. If the cache flush really failed (eg due to a stuffed disk) then there really is a problem, but IMO it is likely this is going to be caught by a read or a write operation very soon. If it is a transient error then panicing seems to be about the worse response :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBGLdgY5ZPcIHs/zowRArh2AKCQlKeArXs0ABVkMaT2n6/LBRBo8ACdENaP I1Murus0ODt0T5PIrHq+ivU= =3e2K -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704241942.40874.doconnor>