Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Aug 2013 14:51:38 -0600
From:      Ian Lepore <ian@FreeBSD.org>
To:        Edward Tomasz =?iso-8859-2?Q?Napiera=B3a?= <trasz@FreeBSD.org>
Cc:        Zaphod Beeblebrox <zbeeble@gmail.com>, FreeBSD Stable <freebsd-stable@FreeBSD.org>
Subject:   Re: gmirror crash writing to disk? Or is it su+j crash?
Message-ID:  <1377895898.1111.341.camel@revolution.hippie.lan>
In-Reply-To: <370A25C8-7747-4B96-A506-EB92FD0F77CF@FreeBSD.org>
References:  <CACpH0MdU5NMi=GvYbG5W-F-UkH=s89d8Docvz8_KS0%2BfqNH1cQ@mail.gmail.com> <370A25C8-7747-4B96-A506-EB92FD0F77CF@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2013-08-30 at 21:50 +0200, Edward Tomasz Napiera=B3a wrote:
> Wiadomo=B6=E6 napisana przez Zaphod Beeblebrox <zbeeble@gmail.com> w dn=
iu 29 sie 2013, o godz. 23:35:
> > So I have a system running:
> >=20
> > FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03=
:02:55
> > EDT 2013     root@walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE  i386
> >=20
> > and it has two 2T SATA disks.  To keep this post short, the crash.txt=
 is
> > here.
> >=20
> > https://uk.eicat.ca/owncloud/public.php?service=3Dfiles&t=3Dfea9d2557=
9fe0c4afb808859e80e1493
>=20
> Login error.
>=20
> > now curiously, while running a "make -j4 buildkernel" ... almost ever=
y time
> > ... it crashes with:
> >=20
> > g_vfs_done():mirror/walke[WRITE(offset=3D516764794880, length=3D65536=
)]error =3D
> > 11
> > /usr: got error 11 while accessing filesystem
> > panic: softdep_deallocate_dependencies: unrecovered I/O error
>=20
> This is softupdates panic caused by write operation returning error 11,=
 which,
> according to 'man errno', is EDEADLK.
>=20
> To be honest, I have no idea why gmirror might be returning this error.
>=20
> > ... no error report from the hard drives, simply an error report from=
 the
> > mirror.
>=20
> Note that ahci(4) does not log errors unless you're running with bootve=
rbose.
>=20
> > The filesystem is ufs with su+j... but I'm not sure this matters here.
>=20
> It does, kind of - without soft updates/SUJ, the error would be non-fat=
al - it
> wouldn't panic the box, but it would (probably) cause data corruption.

One of the few places in the kernel that uses EDEADLK is in geom_io.c
(line 642 in -current) in g_io_transient_map_bio()...

		g_io_deliver(bp, EDEADLK/* XXXKIB */);

-- Ian





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1377895898.1111.341.camel>