From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 43354] New: Corruption on a small loopback ext4 file system with Linux 3.4
Date: Fri, 8 Jun 2012 03:59:03 +0000 (UTC) [thread overview]
Message-ID: <bug-43354-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=43354
Summary: Corruption on a small loopback ext4 file system with
Linux 3.4
Product: File System
Version: 2.5
Kernel Version: 3.4.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: alecm@gmx.com
Regression: Yes
With Linux 3.4, I am getting major corruption on a loopback ext4 filesystem:
parts of files are randomly inserted into other files.
Below are steps to reproduce - I've been able to reproduce this on two
different systems. Both have ext4 root, using a plain kernel.org 3.4.1 kernel.
The problem does not reproduce when switching back to Linux 3.3.6.
If you need any additional info, I'll be happy to provide it.
# uname -r
3.4.1
# dd if=/dev/zero of=tree.ext4 bs=1M count=512
512+0 records in
512+0 records out
536870912 bytes (537 MB) copied, 0.589387 s, 911 MB/s
# mkfs.ext4 -T small -N 200000 tree.ext4
mke2fs 1.42.3 (14-May-2012)
tree.ext4 is not a block special device.
Proceed anyway? (y,n) y
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
200192 inodes, 524288 blocks
26214 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
64 block groups
8192 blocks per group, 8192 fragments per group
3128 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
# mkdir tree
# mount -o loop tree.ext4 tree
# tar xaf portage-20120607.tar.xz -C tree
# find tree -type f -exec sha1sum {} \; > checksums
# umount tree
# sync
# echo 3 > /proc/sys/vm/drop_caches # important! everything will seem fine
otherwise
# fsck.ext4 -f tree.ext4
e2fsck 1.42.3 (14-May-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
tree.ext4: 183722/200192 files (0.0% non-contiguous), 402575/524288 blocks
# mount -o loop tree.ext4 tree
# sha1sum --check --quiet checksums
tree/portage/net-firewall/conntrack-tools/ChangeLog: FAILED
tree/portage/net-firewall/conntrack-tools/files/conntrackd.initd-r1: FAILED
tree/portage/net-firewall/nufw/ChangeLog: FAILED
...
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2012-06-08 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 3:59 bugzilla-daemon [this message]
2012-06-08 4:18 ` [Bug 43354] Corruption on a small loopback ext4 file system with Linux 3.4 bugzilla-daemon
2012-06-08 4:58 ` bugzilla-daemon
2012-06-08 13:44 ` bugzilla-daemon
2012-06-08 17:46 ` bugzilla-daemon
2012-06-14 21:48 ` bugzilla-daemon
2012-07-28 14:33 ` bugzilla-daemon
2012-08-14 15:28 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-43354-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.