From owner-freebsd-bugs@FreeBSD.ORG Fri Mar 20 11:28:10 2015 Return-Path: Delivered-To: freebsd-bugs@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 5DFD88AA for ; Fri, 20 Mar 2015 11:28:10 +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 29FB9D50 for ; Fri, 20 Mar 2015 11:28:10 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2KBSALx021764 for ; Fri, 20 Mar 2015 11:28:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198731] Generated ext3 filesystem is reported to have corrupted directory inodes Date: Fri, 20 Mar 2015 11:28:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new 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-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2015 11:28:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198731 Bug ID: 198731 Summary: Generated ext3 filesystem is reported to have corrupted directory inodes Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ardovm@yahoo.it Under ``special'' circumstances, the kernel support for ext2fs generates a filesystem that is corrupted, according to fsck.ext3. Systems: - FreeBSD myhost1 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Tue Feb 24 19:00:21 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 - FreeBSD myhost2 9.3-STABLE FreeBSD 9.3-STABLE #111 r280132M: Mon Mar 16 10:02:12 CET 2015 root@myhost2:/usr/obj/usr/src/sys/GENERIC i386 Steps to reproduce: Create a dummy filesystem, extract a certain archive inside it, unmount it and fsck it. In steps: # dd if=/dev/zero of=disk.img bs=512M count=1 # mdconfig -a -t vnode -f disk.img # suppose it returns 'md0' # mkfs.ext3 /dev/md0 # mount -t ext2fs /dev/md0 /mnt # tar -C /mnt -xjf bugraising.tar.bz2 # umount /mnt/ # fsck.ext3 -f /dev/md0 e2fsck 1.42.12 (29-Aug-2014) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Directory inode 8262, block #1, offset 2020: directory corrupted Salvage? The file 'bugraising.tar.bz2' contains private data; I would rather send it to individual e-mail addresses if you don't mind, instead of making it publicly available. It's only 1.2 megabytes. On 9-STABLE, it looks like there is a difference if I wait for some seconds between the 'tar' and 'umount' commands: the longer I wait, the more likely is the filesystem to be corrupted. The corruption of the filesystem is confirmed by a Linux system, on which the filesystem was initially to be used. After fixing the filesystem inconsistencies, it looks like that the ls -lR output remains the same; i.e. there is no visible difference in the file layout. Please tell me how and where can I send/submit the ``bug-raising'' archive, or if what I am doing is by any means unsupported. -- You are receiving this mail because: You are the assignee for the bug.