From: Patrick Gelin <patrick.gelin@free.fr>
To: linux-admin@vger.kernel.org
Subject: Re: Badblocs too long...
Date: Wed, 21 Jan 2004 18:18:35 +0100 [thread overview]
Message-ID: <bumbur$dkd$2@sea.gmane.org> (raw)
In-Reply-To: 20040121013540.GA7756@neon
Axel Siebenwirth wrote:
>> 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.
>
Firstly, I was using a journaling file system, but I've got same problems...
> But first let it finish the e2fsck even though it takes so long.
Sorry, but I can't wait for one week...
> Any helpful kernel messages?
I found nothing, but I don't know what to look for...
--
Patrick GELIN
rue du Beau-Site, 3
CH-2300 La Chaux-de-Fonds
Tel: +41 (0)32 / 913 41 48
Email: patrick.gelin@free.fr
next prev parent reply other threads:[~2004-01-21 17:18 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
2004-01-21 17:18 ` Patrick Gelin [this message]
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='bumbur$dkd$2@sea.gmane.org' \
--to=patrick.gelin@free.fr \
--cc=linux-admin@vger.kernel.org \
/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.