From: Christopher Faylor <cgf@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: overseers@sources.redhat.com
Subject: Re: hard disk recovered?
Date: Sat, 07 Apr 2001 20:04:00 -0000 [thread overview]
Message-ID: <20010407230408.A18504@redhat.com> (raw)
Message-ID: <20010407200400.KUV0F6arpzObP4bFfbZ95m3sqy0wlvnQybaqZTzjY-8@z> (raw)
In-Reply-To: <Pine.BSF.4.30.0104072243550.77238-100000@dair.pair.com>
On Sat, Apr 07, 2001 at 10:55:16PM -0400, Hans-Peter Nilsson wrote:
>On Sat, 7 Apr 2001, Christopher Faylor wrote:
>> I was going to bring down the htdig partition for one more fruitless
>> attempt at fixing this problem
>
>I stumbled on "/sbin/badblocks" which may or may not be useful; I've never
>run it.
Hmm. fsck should run this automatically if you give it the -c option,
or at least that is how I'm interpreting what I've read. I guess I'll
try that next. Thanks for the pointer.
>> but it looks like htdig is running on it
>> now.
>
>Yep. Please wait a little while, it's in the word-sorting phase. See
>"~htdigid/gcc/update-log.failed.2001-04-07d". It might just succeed this
>time; fingers crossed. It's soon over anyway...
>
>> If I wanted to just stop everything htdig related for a while, do I have
>> to do more than just umount the partition? I'm thinking about backing
>> up and mkfs'ing the partition again to see if that solves things.
>
>See <URL: http://sources.redhat.com/ml/overseers/2001-q2/msg00001.html >,
>last paragraph.
Thanks for the reference. Sorry that I didn't recall reading this before.
I'm watching the process now. I hope that the fact that the seconds are
ticking and there are no apparent errors in /var/log/messages is a good
sign.
Once this completes, I'll umount the partition and run fsck again. I
just upgraded e2fsck on sourceware. Maybe the new version will find
something that previously was missed.
cgf
next prev parent reply other threads:[~2001-04-07 20:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Christopher Faylor
2001-04-07 18:49 ` Christopher Faylor
2001-04-12 11:48 ` law
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-07 19:23 ` Hans-Peter Nilsson
2001-12-31 19:40 ` Christopher Faylor
2001-04-07 19:30 ` Christopher Faylor
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-07 19:55 ` Hans-Peter Nilsson
2001-12-31 19:40 ` Christopher Faylor [this message]
2001-04-07 20:04 ` Christopher Faylor
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-07 20:14 ` Hans-Peter Nilsson
2001-04-17 11:52 ` htdig crontab on sourceware Jason Molenda
2001-04-17 13:28 ` Hans-Peter Nilsson
2001-04-17 14:28 ` Christopher Faylor
[not found] ` <20010417133358.A4238@shell17.ba.best.com>
2001-04-18 8:20 ` Jason Molenda
-- strict thread matches above, loose matches on Subject: below --
2001-12-31 19:40 hard disk recovered? Angela Marie Thomas
2001-04-07 21:21 ` Angela Marie Thomas
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=20010407230408.A18504@redhat.com \
--to=cgf@redhat.com \
--cc=hp@bitrange.com \
--cc=overseers@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).