From owner-freebsd-fs@freebsd.org  Tue Nov 17 19:57:46 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A87CCA3174D
 for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 17 Nov 2015 19:57:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 94B221793
 for <freebsd-fs@FreeBSD.org>; Tue, 17 Nov 2015 19:57:46 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAHJvk4e012071
 for <freebsd-fs@FreeBSD.org>; Tue, 17 Nov 2015 19:57:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 203588] [ufs] fsck_ufs segfaults during journals after powerloss
Date: Tue, 17 Nov 2015 19:57:45 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: amvandemore@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-203588-3630-IvOM41YK7m@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203588-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-203588-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2015 19:57:46 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203588

amvandemore@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amvandemore@gmail.com

--- Comment #1 from amvandemore@gmail.com ---
Yes this is a bug.  Unfortunately, this type of PR is almost useless since
there is no actionable information included.  I don't know any devs who love
wild goose chases.

If it happens again, better ways to handle this are:

1.  Snapshot the underlying block device so there is always access to the
problematic state.
2.  Run "fsck_ffs -d" and "fsck_ffs -f -d" and ensure the output is saved eg
script(1).

See bug #187221 for an example of an actionable PR.

Also what does this "A full fsck hopefully worked .." mean?  Did a full fsck
work?  If yes then there is no need to mention it and if no it needs to be in
the PR.

-- 
You are receiving this mail because:
You are the assignee for the bug.