From owner-freebsd-fs@FreeBSD.ORG  Sun Mar 22 09:22:24 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 101B6263
 for <freebsd-fs@FreeBSD.org>; Sun, 22 Mar 2015 09:22:24 +0000 (UTC)
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 E9B3B7E0
 for <freebsd-fs@FreeBSD.org>; Sun, 22 Mar 2015 09:22:23 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2M9MNoD053573
 for <freebsd-fs@FreeBSD.org>; Sun, 22 Mar 2015 09:22:23 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 198731] Generated ext2/ext3 filesystem is reported to have
 corrupted directory inodes
Date: Sun, 22 Mar 2015 09:22:23 +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.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ardovm@yahoo.it
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: 
Message-ID: <bug-198731-3630-lG9vB5HVdR@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198731-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-198731-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.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2015 09:22:24 -0000

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

--- Comment #3 from Arrigo Marchiori <ardovm@yahoo.it> ---
(In reply to Pedro F. Giffuni from comment #2)
Ciao Pedro!

Thank you for your answer.

It seems that clearing the "dir_index" feature makes the problem disappear!
I tested it on the 10.1-release-p6 system using the ad-hoc tarball.

I will try this setting tomorrow, on my 9-STABLE system, with the full ext2
filesystem on real hardware. I will keep you updated.

Thank you again and have a nice Sunday.

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