From: Axel Siebenwirth <axel@pearbough.net>
To: Patrick Gelin <patrick.gelin@free.fr>
Cc: linux-admin@vger.kernel.org
Subject: Re: Badblocs too long...
Date: Wed, 21 Jan 2004 02:35:40 +0100 [thread overview]
Message-ID: <20040121013540.GA7756@neon> (raw)
In-Reply-To: <buk55j$j4n$1@sea.gmane.org>
Hi Patrick!
On Tue, 20 Jan 2004, Patrick Gelin wrote:
> Hi,
>
> I suspect bad blocs in my Hard disk, so I try the commande:
>
> e2fsck -c /dev/hdb1 (hdb1 not mounted)
>
> it calls badblocks, but it's very very long... after half a day I've checked
> only 1/10 of my hard disk (IDE - 20 Go)
>
> 1. Is it normal?
Don't know for sure, but I guess that kinda depends on the filesystem
error thats being found?!
>
> 2. Can I do something else?
I'd wait for the e2fscking to finish, see whats going on, what kind of problem
turns out with the filesystem and then, in case you get it fixed,
think about migrating to a journaling filesytem.
But first let it finish the e2fsck even though it takes so long.
Any helpful kernel messages?
Axel
____________________________________________________________________________
Axel Siebenwirth phone +49 3641 776807 |
Am Birnstiel 3 axel at pearbough dot net |
07745 Jena |
Germany________________________________________________http://pearbough.net |
I either want less decadence or more chance to participate in it.
____________________________________________________________________________
next prev parent reply other threads:[~2004-01-21 1:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 21:10 Badblocs too long Patrick Gelin
2004-01-21 1:35 ` Axel Siebenwirth [this message]
2004-01-21 17:18 ` Patrick Gelin
2004-01-21 1:48 ` chuck gelm net
2004-01-21 17:15 ` Patrick Gelin
2004-01-22 21:24 ` chuck
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 17:34 Carrión Byron
2004-01-21 18:16 ` Patrick Gelin
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=20040121013540.GA7756@neon \
--to=axel@pearbough.net \
--cc=linux-admin@vger.kernel.org \
--cc=patrick.gelin@free.fr \
/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 NNTP newsgroup(s).