From: Vitaly Fertman <vitaly@namesys.com>
To: Francois-Rene Rideau <fare@tunes.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Oh no! Not again!
Date: Wed, 29 Jan 2003 23:17:25 +0300 [thread overview]
Message-ID: <200301292317.25045.vitaly@namesys.com> (raw)
In-Reply-To: <20030129193126.GA1367@ZhengHe.augustin.thierry>
On Wednesday 29 January 2003 22:31, Francois-Rene Rideau wrote:
> OK. So I built the latest reiserfsck as a static binary,
> and ran it with --rebuild-tree, and I got an infinite loop
> just like previously. In case anyone cares, I have kept the logfile for it.
> Is there anything that interests you about that failure,
> or should I promptly reformat the disk?
Did you run the fsck (booted from /boot) when the drive was in that other
mashine you had no problem with or in the problem one? It is a bad idea to
run reiserfsck on a broken hardware - the result is unpredictable.
> Also, does any of you have any hint as to how to identify the failure
> that led to this crash? I suspect either the disk or the motherboard,
If you do not see any problem with the disk when you put it into another
computer - it is not the disk. It can be IDE controller, cable...
> but it's hard to tell: booting on my 80MB rescue disk works well,
> whereas the disk looks like it works correctly on another machine,
> and does not issue errors even on that machine, if I don't use DMA.
> Really weird. What scares me is that if I don't identify the problem,
> a similar crash may happen again...
>
> Cheers!
>
> [ François-René ÐVB Rideau | Reflection&Cybernethics |
> http://fare.tunes.org ] [ TUNES project for a Free Reflective Computing
> System | http://tunes.org ] Demand the establishment of the government in
> its rightful home at Disneyland.
--
Thanks,
Vitaly Fertman
prev parent reply other threads:[~2003-01-29 20:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 22:15 recovery of crashed reiserfs disk? Francois-Rene Rideau
2003-01-18 7:09 ` Ookhoi
2003-01-18 8:51 ` Oleg Drokin
2003-01-18 9:01 ` Ookhoi
2003-01-18 11:57 ` Francois-Rene Rideau
2003-01-20 14:20 ` Francois-Rene Rideau
2003-01-21 21:33 ` Crash again! Francois-Rene Rideau
2003-01-22 5:57 ` Ookhoi
2003-01-22 10:03 ` Francois-Rene Rideau
2003-01-24 22:28 ` Crash: the problem was DMA! Francois-Rene Rideau
2003-01-25 16:15 ` Manuel Krause
2003-01-26 18:18 ` mkreiserfs -s 1024 makes unmountable partitions Francois-Rene Rideau
2003-01-27 4:49 ` Ookhoi
2003-01-27 5:23 ` Brian Tinsley
2003-01-27 6:59 ` Oleg Drokin
2003-01-27 7:20 ` Scott R. Every
2003-01-27 7:25 ` Oleg Drokin
2003-01-27 7:37 ` Scott R. Every
2003-01-27 7:42 ` Oleg Drokin
2003-01-29 11:37 ` Hans Reiser
2003-01-27 11:26 ` Francois-Rene Rideau
2003-01-27 11:33 ` Oleg Drokin
2003-01-27 11:42 ` Francois-Rene Rideau
2003-01-27 12:46 ` Francois-Rene Rideau
2003-01-27 14:20 ` Manuel Krause
2003-01-28 2:41 ` Oh no! Not again! Francois-Rene Rideau
2003-01-28 11:00 ` Vitaly Fertman
2003-01-29 19:31 ` Francois-Rene Rideau
2003-01-29 20:17 ` Vitaly Fertman [this message]
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=200301292317.25045.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=fare@tunes.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.