From: Jeff Mahoney <jeffm@suse.com>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: Jaroslav Fojtik <JaFojtik@seznam.cz>,
Reiserfs mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: Re2: Reiserfs3 is crashing - where/whom to report?
Date: Tue, 20 Jan 2009 09:54:05 -0500 [thread overview]
Message-ID: <4975E58D.6040503@suse.com> (raw)
In-Reply-To: <4975AB4A.4070607@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Edward Shishkin wrote:
> Jaroslav Fojtik wrote:
>> Dear Shishkin,
>>
>>
>>> would you please check your partition with fsck,
>>> and, please, upgrade the kernel, if possible.
>>>
>> Yes, I can. Now I have a new format of HDD, so fschk is meaningless.
>> If it is neccessary, I could reproduce a bug again, change format
>> (mkreiserfs) and do a hard load until reiserfs crash. Do you want
>> me to do this?
>> HDD is still clean and free for experiments. After while, I will
>> use HDD for regular data storage.
>>
>> I am using linux-2.6.21.5 now. I cannot upgrade to >linux-2.6.24.7,
>> because MadWiFi stops to be compiled.
>>
>>
>
> Ok, please, have the 2.6.24.7 kernel and reiserfsprogs-3.6.21
> to format a partition:
> http://www.kernel.org/pub/linux/utils/fs/reiserfs/reiserfsprogs-3.6.21.tar.gz
> Catch all kernel messages and describe steps to reproduce the crash.
Since reiserfsprogs 3.6.21 doesn't support block sizes < 4k, he'll be
unable to.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkl15Y0ACgkQLPWxlyuTD7J4NwCeJZIE14DxckwOYs/bmKNZyGcu
PGYAniu8tNmqTlGP0DOKG92vR98uqgzy
=syVJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-01-20 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49750FC1.23700.2C929@JaFojtik.seznam.cz>
2009-01-20 0:20 ` Reiserfs3 is crashing - where/whom to report? Edward Shishkin
2009-01-20 4:49 ` Jeff Mahoney
2009-01-20 9:09 ` Re2: " Jaroslav Fojtik
[not found] ` <49759410.20384.D37CA@JaFojtik.seznam.cz>
2009-01-20 10:45 ` Edward Shishkin
2009-01-20 14:54 ` Jeff Mahoney [this message]
2009-01-20 17:49 ` Re4: " Jaroslav Fojtik
2009-01-20 18:19 ` Edward Shishkin
2009-01-20 18:49 ` Re6: " Jaroslav Fojtik
2009-01-20 18:54 ` Edward Shishkin
2009-01-20 21:20 ` Re8: " Jaroslav Fojtik
2009-01-20 23:07 ` Jeff Mahoney
2009-01-21 19:34 ` Re10: " Jaroslav Fojtik
2009-01-21 19:25 ` Jeff Mahoney
2009-01-27 21:30 ` Re12: " Jaroslav Fojtik
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=4975E58D.6040503@suse.com \
--to=jeffm@suse.com \
--cc=JaFojtik@seznam.cz \
--cc=edward.shishkin@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox