From owner-freebsd-fs@FreeBSD.ORG Sun Sep 22 22:43:28 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E96EDB3D; Sun, 22 Sep 2013 22:43:27 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 56D072BC5; Sun, 22 Sep 2013 22:43:27 +0000 (UTC) Received: by mail-ee0-f43.google.com with SMTP id e52so1335423eek.2 for ; Sun, 22 Sep 2013 15:43:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=faxSyFTHcfBmWLL3As2LoxHQbjZozqBsAx5FF74onu8=; b=Fs3f3HP9TYqm8BxVadjm7Gd027ACmn5mImjtvRLEqdPWbDVyE3tJXxSdt82DRkyMxD ILwn41DZWBHqrSywLqbeXBdp4R9UWgGvHxBRnYuvEm5IWVQuv2q9fayBdNIQg7Kb2PO6 yguXHjcqvcvGg8nBOtBbMY8RdRU4O6XZV6hjbF+TO9TLGI3X5cJXAPpFZ+P3fCgTccJf R8sr/kQxkyee3xbn6egiEi/htT4PYS83r4W1lnL9gOlmuMLjxI1HlaNUY+uCuWClVjfZ 1MHiCl+cze96b0p2r6Z/eNDBQQZQXdcVCbY/3YS4boEq9jYjp1pkx6VXN3PhKltnLrJc DLRg== X-Received: by 10.14.172.133 with SMTP id t5mr31323110eel.35.1379889804963; Sun, 22 Sep 2013 15:43:24 -0700 (PDT) Received: from [192.168.1.102] (addn239.neoplus.adsl.tpnet.pl. [79.184.65.239]) by mx.google.com with ESMTPSA id bn13sm37271036eeb.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 22 Sep 2013 15:43:24 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: Strange UFS write problem & SU+J "unexpected inconsistences" on 9.1-STABLE r253105 after it on OTHER filesystems. Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= X-Priority: 3 (Normal) In-Reply-To: <724152380.20130921144811@serebryakov.spb.ru> Date: Mon, 23 Sep 2013 00:43:23 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <0AA0A9CE-C692-4183-94FA-BC43837ADAE3@FreeBSD.org> References: <724152380.20130921144811@serebryakov.spb.ru> To: lev@FreeBSD.org X-Mailer: Apple Mail (2.1510) Cc: freebsd-fs , Kirk McKusick X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Sep 2013 22:43:28 -0000 Wiadomo=B6=E6 napisana przez Lev Serebryakov w dniu 21 = wrz 2013, o godz. 12:48: > Hello, freebsd-fs. >=20 > My server paniced tonight with UFS problem: >=20 > ufs/root[WRITE(offset=3D385499136, length=3D16384)]error =3D 22 > g_vfs_done():ufs/root[WRITE(offset=3D385564672, length=3D16384)]error = =3D 22 > g_vfs_done():ufs/root[WRITE(offset=3D385712128, length=3D16384)]error = =3D 22 > g_vfs_done():ufs/root[WRITE(offset=3D385826816, length=3D16384)]error = =3D 22 > g_vfs_done():ufs/root[WRITE(offset=3D770703360, length=3D16384)]error = =3D 22 > g_vfs_done():ufs/root[WRITE(offset=3D770719744, length=3D16384)]error = =3D 22 > g_vfs_done():ufs/var[WRITE(offset=3D268539904, length=3D2048)]error =3D = 22 > /var: got error 22 while accessing filesystem > panic: softdep_deallocate_dependencies: unrecovered I/O error > cpuid =3D 0 > KDB: stack backtrace: > #0 0xffffffff8047a836 at kdb_backtrace+0x66 > #1 0xffffffff8044382e at panic+0x1ce > #2 0xffffffff8059c040 at clear_remove+0 > #3 0xffffffff804bf835 at brelse+0x75 > #4 0xffffffff804c2258 at bufdone+0x68 > #5 0xffffffff804bcb0e at biodone+0xae > #6 0xffffffff803e289c at g_io_schedule_up+0xac > #7 0xffffffff803e2ffc at g_up_procbody+0x5c > #8 0xffffffff804144ef at fork_exit+0x11f > #9 0xffffffff805f53de at fork_trampoline+0xe >=20 > and "fsck_ffs" refused to fix two OTHER (/usr and /tmp) SU+J-enabled = FFSes with same messages: >=20 > Journal file sequence mismatch XXX !=3D YYY > UNEXPECTED SU+J INCONSISTENCY > INTERNAL ERROR: GOT TO reply() > UNIXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY >=20 > and exited with signal 11. >=20 > So, here are two questions: >=20 > (1) What does "error 22" mean? Disk doesn't show ANY errors in = S.M.A.R.T. > (and all internal tests are Ok). Also, here are NO ANY driver (AHCI) = errors > in post-mortem dump. It doesn't look like hardware problem. According to "man errno", 22 is EINVAL. Which is... weird, to say the = least. What's below the filesystem? I mean, what's the GEOM tree? > (2) How to avoid fsck refuses in such situations? Why OTHER (not ones = with > write errors) FSes get errors? It looks like one another problem with = SU+J. Try to make fsck _not_ use journal. Simply respond "n" when it asks if = you want it to use journal. > Please note, these FSes reside directly on SATA drive, without any = software or > hardware RAIDs. No labels, for example? [..]