From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: BUG at fs/ext4/inode.c:1590!
Date: Mon, 20 May 2013 09:51:49 +0200 [thread overview]
Message-ID: <5199D615.20106@gmx.de> (raw)
In-Reply-To: <51998A31.7060200@redhat.com>
On 05/20/2013 04:28 AM, Eric Sandeen wrote:
> It's probably possible that it's memory corruption too.
>
>> > Can you replicate it? Do you have the corrupted file system?
> Right, these bugs need to be narrowed down to be useful.
>
When the bug occurred I was neither able to cd into the directory where
the log files resides nor I could do a sync. psgrep and friends hang too.
On the other hand I was able to write an email with thunderbird and send
it out before I had to power off the system - sysrq key alt+print+b
didn't worked too.
> Does trinity start w/ a random seed, so you can restart? Or better
> yet, restart w/ that seed and show the last 20 syscalls before the
> bug, etc?
yes - trinity uses a randomly choosen seed. SO a replay is possible later.
But because the bug occurred after 3 hours /me thinks that a simple
replay with just few syscalls won't work.
> "I threw random garbage at the kernel and something fell off after a
> few hours" is a bit vague. ;)
yes - I do know that the bug report lacks data to easy reproduce it -
OTOH I thought it is better to report that then to ignore.
To speed up things for fuzzy tests I do use file systems living in a
tempfs. I'll change my scripts to hold at least the main log file of
trinity on a hard disk and came back if I do have useful log data too.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-20 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 22:25 BUG at fs/ext4/inode.c:1590! Toralf Förster
2013-05-19 23:55 ` Theodore Ts'o
2013-05-20 2:28 ` Eric Sandeen
2013-05-20 7:51 ` Toralf Förster [this message]
2013-05-20 12:32 ` Eric Sandeen
2013-05-26 12:42 ` Toralf Förster
2013-05-20 15:27 ` Trinity: " Eric Sandeen
2013-05-21 17:07 ` Dave Jones
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=5199D615.20106@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).