From owner-freebsd-fs@freebsd.org  Sun Jan  3 14:36:07 2016
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 F10C2A605C1
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sun,  3 Jan 2016 14:36:07 +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 E200C1BA7
 for <freebsd-fs@FreeBSD.org>; Sun,  3 Jan 2016 14:36:07 +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 u03Ea7LP060898
 for <freebsd-fs@FreeBSD.org>; Sun, 3 Jan 2016 14:36:07 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 205668] [ext2fs] [patch] cannot mount EXT4 filesystems which
 weren't cleanly unmounted
Date: Sun, 03 Jan 2016 14:36:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: pfg@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: pfg@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-205668-3630-wJo80N5OdN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205668-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-205668-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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: Sun, 03 Jan 2016 14:36:08 -0000

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

--- Comment #5 from Pedro F. Giffuni <pfg@FreeBSD.org> ---
(In reply to Damjan Jovanovic from comment #4)
Hi Damjan;

Yes, this is consistent with us ignoring the feature: read-only operation
should not touch the disk and warning only when unmounting would give the
impression that *we* somehow corrupted the information. Let the rw
implementation (in linux) deal with it.

An alternative would have been to simply not mount the disk and let the user
deal with ext4 fsck (I think that was what was happening originally).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=