From owner-freebsd-fs@freebsd.org  Sat Jan 23 18:47:10 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 92670A8FDA7
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sat, 23 Jan 2016 18:47:10 +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 7F8401772
 for <freebsd-fs@FreeBSD.org>; Sat, 23 Jan 2016 18:47:10 +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 u0NIlAQH080556
 for <freebsd-fs@FreeBSD.org>; Sat, 23 Jan 2016 18:47:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 206530] ext2fs: fsck.ext3 reports "Inode 157938 has INDEX_FL
 flag set but is not a directory"
Date: Sat, 23 Jan 2016 18:47:10 +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-206530-3630-y8Af1LU1Eh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206530-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-206530-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: Sat, 23 Jan 2016 18:47:10 -0000

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

--- Comment #2 from Pedro F. Giffuni <pfg@FreeBSD.org> ---
(In reply to Damjan Jovanovic from comment #0)

While your patch is not wrong, the root cause is elsewhere.
IN_E4INDEX and IN_E4EXTENTS are Ext4 attributes that we hide in i_flag
but they should never get written since we don't have Ext4 write support.

Curiously, it appears the situation also happened at some point on linux:
http://sourceforge.net/p/e2fsprogs/bugs/41/

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