From: Christian Brandt <brandtc@psi5.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Ric Wheeler <rwheeler@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: fsck.ext4 taking months
Date: Tue, 29 Mar 2011 22:26:54 +0200 [thread overview]
Message-ID: <4D92408E.7090008@psi5.com> (raw)
In-Reply-To: <20110329060300.GA27142@bitwizard.nl>
Am 29.03.2011 08:03, schrieb Rogier Wolff:
>>> >>> Is the slow performance with lots of hard links a known issue?
> >
> > Yes, it is a known issue.
At least its not my fault :-) thanks for the info.
> > You get to test my patch. :-)
> >
> > I strongly suspect that (just like me) sometime in the past you've
> > seen e2fsck run out of memory and were advised to enable the
> > on-disk-databases.
Something like that... The drive has been formatted recently but a bad
controller corrupted vital information upon mount and some more on the
next fsck. I Ctrl-C pretty fast when I saw lots of rather confusing
kernel errors between fsck output. This could have left the drive in a
similiar state, couldn't it?
-- Christian Brandt
life is short and in most cases it ends with death but my tombstone
will carry the hiscore
next prev parent reply other threads:[~2011-03-29 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 11:28 fsck.ext4 taking months Christian Brandt
2011-03-28 14:43 ` Ric Wheeler
2011-03-29 6:03 ` Rogier Wolff
2011-03-29 20:26 ` Christian Brandt [this message]
2011-03-30 8:45 ` Rogier Wolff
2011-03-29 20:21 ` Christian Brandt
2011-03-28 15:07 ` Eric Sandeen
2011-03-28 15:47 ` Ted Ts'o
2011-03-29 22:02 ` Christian Brandt
2011-03-30 8:34 ` Rogier Wolff
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=4D92408E.7090008@psi5.com \
--to=brandtc@psi5.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@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 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.