From: Francois-Rene Rideau <fare@tunes.org>
To: reiserfs-list@namesys.com
Subject: Oh no! Not again!
Date: Tue, 28 Jan 2003 03:41:58 +0100 [thread overview]
Message-ID: <20030128024158.GA19336@hell.mine.nu> (raw)
In-Reply-To: <20030124222823.GA15643@hell.mine.nu>
Dear all,
to determine whether my DMA problem was due to the disk or the motherboard,
I moved the disk to another machine, where I could successfully
hdparm -Tt /dev/hdc without crashing linux while in udma2.
However, when I put the disk back into its rightful place,
linux died horribly with lots of error messages from reiserfs.
I booted on /boot where I had kept a minimal runtime, and used reiserfsck.
Reiserfsck reported an inconsistency that required using --rebuild-tree.
And after approximately two hours, reiserfsck --rebuild-tree entered
an endless loop, printing
do_pass_2: The block (27179935) is in the tree already. Should not happen.
Is there anything I can do about that, to put it in working order,
or should I reformat and restore what I can from backup?
I've got a distinct feeling this disk will soon go back to MAXTOR,
just like its twin brother.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
[ TUNES project for a Free Reflective Computing System | http://tunes.org ]
http://Bastiat.org/ - debunking economic sophisms since 1845.
next prev parent reply other threads:[~2003-01-28 2:41 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 ` Francois-Rene Rideau [this message]
2003-01-28 11:00 ` Oh no! Not again! Vitaly Fertman
2003-01-29 19:31 ` Francois-Rene Rideau
2003-01-29 20:17 ` Vitaly Fertman
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=20030128024158.GA19336@hell.mine.nu \
--to=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.