Date: Fri, 20 Mar 2015 11:28:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 198731] Generated ext3 filesystem is reported to have corrupted directory inodes Message-ID: <bug-198731-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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<y>? 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198731-8>