From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12594] New: filesystem corruption while running bonnie
Date: Sun, 1 Feb 2009 06:59:52 -0800 (PST) [thread overview]
Message-ID: <bug-12594-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12594
Summary: filesystem corruption while running bonnie
Product: File System
Version: 2.5
KernelVersion: 2.6.28.1
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext3
AssignedTo: fs_ext3@kernel-bugs.osdl.org
ReportedBy: folkert@vanheusden.com
mkdir /mnt/tmp /tmp/tmp ; mount -t tmpfs /dev/null /mnt
chown folkert /mnt/tmp /tmp/tmp
and then in parallel:
while [ 1 ] ; do bonnie++ -d /tmp/tmp -s 128 -r 64 -x 1 -u folkert ; done
while [ 1 ] ; do bonnie++ -d /mnt/tmp -s 128 -r 64 -x 1 -u folkert ; done
then after say 15 minutes i run the reboot command (normal via init) during the
fsck (I always do a touch /forcefsck) I get:
fsck 1.41.3 (12-Oct-2008)
/dev/mapper/VGODR-tmp contains a file system with errors, check forced.
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (1) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (1) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (2) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (2) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (3) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (3) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (4) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (4) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (5) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (5) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (6) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (6) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (7) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (7) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (8) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (8) has bad
max hash
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (8) not
referenced
...
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (523) not
referenced
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (524) has
invalid depth (2)
/dev/mapper/VGODR-tmp: Problem in HTREE directory inode 69634: node (524) not
referenced
/dev/mapper/VGODR-tmp: Invalid HTREE directory inode 69634 (/tmp/Bonnie.3813).
I've got a gzip'ed dump of /tmp available on request.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-01 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 14:59 bugme-daemon [this message]
2009-02-01 16:14 ` [Bug 12594] New: filesystem corruption while running bonnie Eric Sandeen
2009-02-01 16:14 ` [Bug 12594] " bugme-daemon
2009-02-01 20:50 ` bugme-daemon
2009-02-04 12:11 ` bugme-daemon
2009-02-05 20:00 ` bugme-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-12594-13602@http.bugzilla.kernel.org/ \
--to=bugme-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).