From: evilninja <evilninja@gmx.net>
To: reiserfs-list@namesys.com
Cc: Paul Gear <paul@gear.dyndns.org>
Subject: Re: Corrupt reiser3 fs
Date: Sun, 12 Jun 2005 19:35:32 +0200 [thread overview]
Message-ID: <42AC7264.8000503@gmx.net> (raw)
In-Reply-To: <42AB68F2.8030904@gear.dyndns.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul Gear schrieb:
> The problem has occurred looks like a hardware problem (perhaps
> memory). Send us the bug report only if the second run dies at
> the same place with the same block number.
so....does it? is it reproduceable on a 2nd run? also with a different
(maybe vanilla) kernel?
before trashing the fs, you could do
debugreiserfs -p /dev/HDD | bzip2 -c > HDD-meta.bz2
then some reiserfs-guru could use it for debugging.
- --
BOFH excuse #316:
Elves on strike. (Why do they call EMAG Elf Magic)
- --
BOFH excuse #316:
Elves on strike. (Why do they call EMAG Elf Magic)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCrHJkC/PVm5+NVoYRAms/AKC3Nhrq8iRUxjU+PQzI9IXpGVtNOgCfcZ0F
gQBaoD9ga8lKfr1qgB24T7U=
=V18Z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-06-12 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 22:42 Corrupt reiser3 fs Paul Gear
2005-06-12 17:35 ` evilninja [this message]
2005-06-13 9:46 ` Vitaly Fertman
2005-06-13 18:08 ` Hans Reiser
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=42AC7264.8000503@gmx.net \
--to=evilninja@gmx.net \
--cc=paul@gear.dyndns.org \
--cc=reiserfs-list@namesys.com \
/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.