From owner-freebsd-stable@FreeBSD.ORG Fri Aug 30 22:09:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5731B14B; Fri, 30 Aug 2013 22:09:49 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E474D22D0; Fri, 30 Aug 2013 22:09:48 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id gf11so1649271vcb.25 for ; Fri, 30 Aug 2013 15:09:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SgV1EjuxCjkiLEB0sKZ8+5Gg4os8L49rH/A8kkgeGtU=; b=XYA2gLnFkg3ps/eFwHeQRaSe3BhqjKokOD0b+hMd1ATX+3mUijVdU6lqOpzkIdr2Dv BjpLthQ8gyMYk8lsB8FcEtkjtd2bI2wu4up4CYVv0bXGoLF3eBoQQ3EUOOMN9PNTET3t C//d/YE6EHW35CuyAkV0x8nvbSeG2Ff6M06IHpeAKCWexTGdq6W7e/t4Jg/3gA7QAwcs mlPT0S2hvNVG7rSAGOA2lQs7K0mJ4xnqbSAHm7mI1jJMMLuLI9xchMMne5/yOA/tBTZ1 qtdTGh8Fp50dnzbdVI66jD4az9nKnt/Ys2xWj110Monrlfafmc2A1kdvnA64jmH9c1Ob P/Bw== MIME-Version: 1.0 X-Received: by 10.221.55.4 with SMTP id vw4mr17642vcb.37.1377900587991; Fri, 30 Aug 2013 15:09:47 -0700 (PDT) Received: by 10.220.122.1 with HTTP; Fri, 30 Aug 2013 15:09:47 -0700 (PDT) In-Reply-To: <1377895898.1111.341.camel@revolution.hippie.lan> References: <370A25C8-7747-4B96-A506-EB92FD0F77CF@FreeBSD.org> <1377895898.1111.341.camel@revolution.hippie.lan> Date: Fri, 30 Aug 2013 18:09:47 -0400 Message-ID: Subject: Re: gmirror crash writing to disk? Or is it su+j crash? From: Zaphod Beeblebrox To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable , =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2013 22:09:49 -0000 My bad. New link for the core.txt.4: https://uk.eicat.ca/owncloud/public.php?service=3Dfiles&t=3Df471e5afae48334= 2cd20dc390e9c2dd7 On Fri, Aug 30, 2013 at 4:51 PM, Ian Lepore wrote: > On Fri, 2013-08-30 at 21:50 +0200, Edward Tomasz Napiera=B3a wrote: > > Wiadomo=B6=E6 napisana przez Zaphod Beeblebrox w dn= iu > 29 sie 2013, o godz. 23:35: > > > So I have a system running: > > > > > > 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 > > > > > > and it has two 2T SATA disks. To keep this post short, the crash.txt > is > > > here. > > > > > > > https://uk.eicat.ca/owncloud/public.php?service=3Dfiles&t=3Dfea9d25579fe0= c4afb808859e80e1493 > > > > Login error. > > > > > now curiously, while running a "make -j4 buildkernel" ... almost ever= y > time > > > ... it crashes with: > > > > > > 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 > > > > This is softupdates panic caused by write operation returning error 11, > which, > > according to 'man errno', is EDEADLK. > > > > To be honest, I have no idea why gmirror might be returning this error. > > > > > ... no error report from the hard drives, simply an error report from > the > > > mirror. > > > > Note that ahci(4) does not log errors unless you're running with > bootverbose. > > > > > The filesystem is ufs with su+j... but I'm not sure this matters here= . > > > > It does, kind of - without soft updates/SUJ, the error would be > non-fatal - 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 > > >