From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Philipp Gühring" <pg@futureware.at>,
"ReiserFS Development List" <reiserfs-devel@vger.kernel.org>
Subject: Re: ReiserFS Crash
Date: Wed, 21 Apr 2010 23:04:12 +0200 [thread overview]
Message-ID: <4BCF684C.2020609@gmail.com> (raw)
In-Reply-To: <4BCF6253.4040301@futureware.at>
Hello Philipp,
There were a number of fixups in the xattrs path since 2.6.25..
Could you consider upgrading your kernel?
Edward.
Philipp Gühring wrote:
> Hi,
>
> I am currently analyzing a production machine that has (un)regular
> troubles, and discovered a problem in ReiserFS, I think:
>
> http://www2.futureware.at/~philipp/reiserfs-crash.txt
>
> I guess that some more NULL checks might be helpful in and around
> sprintf_le_key.
>
> If you need any additional information from that server, please let me know.
> (I guess that there is probably a problem in the filesystem on the disk,
> but I think that kernel crash is superfluous anyway)
>
> Best regards,
> Philipp Gühring
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2010-04-21 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BCF6253.4040301@futureware.at>
2010-04-21 21:04 ` Edward Shishkin [this message]
2006-05-04 17:06 reiserfs crash Devel
2006-05-05 6:43 ` Vladimir V. Saveliev
2006-05-05 14:34 ` Devel
2006-05-06 7:43 ` Vladimir V. Saveliev
2006-05-09 9:16 ` Devel
2006-05-11 6:21 ` Vladimir V. Saveliev
-- strict thread matches above, loose matches on Subject: below --
2004-11-13 20:38 Brian Minton
2004-11-15 10:07 ` Vladimir Saveliev
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=4BCF684C.2020609@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=pg@futureware.at \
--cc=reiserfs-devel@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.