linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12821] filesystem corrupts on heavy I/O
Date: Thu,  5 Mar 2009 09:46:12 -0800 (PST)	[thread overview]
Message-ID: <20090305174612.46122108042@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12821-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=12821





------- Comment #2 from ddi@dubex.dk  2009-03-05 09:46 -------
It continually spews messages in syslog while it's powered on, but that's not
exactly "reproduction" I guess.

Tried to find the inode in question with debugfs, it said that this particular
inode does not belong to any file - maybe because the inode contains filesystem
metadata, not file data?  Anyhow, no useful output - probably in no small part
because I have no clue what I'm doing with debugfs ;-)

New kernel: Okay, upgraded to the latest available Ubuntu Server kernel.  Had
to yank the power; the sync would never finish (vmstat says it synced about
1kB/s).  Looks like the filesystem is also super-slow for some reason.

(Possible that a logging daemon was putting error messages in the buffer cache
while the sync got farther and farther behind trying to sync those, not sure. 
Did kill all loggers at one point, but didn't help much.  Hmm.)

It came up with the new kernel, did a fsck, which finished off with "fsck died
with exit status 1".

Will try e2image in a moment..


-- 
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.

  parent reply	other threads:[~2009-03-05 17:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 16:42 [Bug 12821] New: filesystem corrupts on heavy I/O bugme-daemon
2009-03-05 17:26 ` [Bug 12821] " bugme-daemon
2009-03-05 17:46 ` bugme-daemon [this message]
2009-03-05 18:06 ` bugme-daemon
2009-03-05 18:13 ` bugme-daemon
2009-03-05 18:59 ` bugme-daemon
2009-03-05 19:06 ` bugme-daemon
2009-03-05 19:25 ` bugme-daemon
2009-03-06  6:11 ` bugme-daemon
2009-03-06  7:16 ` bugme-daemon
2009-03-06 14:18 ` bugme-daemon
2009-03-06 20:21 ` bugme-daemon
2009-03-06 20:30 ` bugme-daemon
2009-03-10 10:03 ` bugme-daemon
2009-03-13  7:11 ` bugme-daemon
2009-03-13 15:03 ` bugme-daemon
2009-03-15  4:56 ` bugme-daemon
2009-03-15  5:23 ` bugme-daemon
2009-03-17  6:07 ` bugme-daemon
2009-03-17  6:07 ` bugme-daemon
2009-03-17  6:30 ` bugme-daemon
2009-03-17 15:28 ` 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=20090305174612.46122108042@picon.linux-foundation.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).