From: Christian Brandt <brandtc@psi5.com>
To: linux-ext4@vger.kernel.org
Subject: fsck.ext4 taking months
Date: Sun, 27 Mar 2011 13:28:53 +0200 [thread overview]
Message-ID: <4D8F1F75.8010201@psi5.com> (raw)
Situation: External 500GB drive holds lots of snapshots using lots of
hard links made by rsync --link-dest. The controller went bad and
destroyed superblock and directory structures. The drive contains
roughly a million files and four complete directory-tree-snapshots with
each roughly a million hardlinks.
Tried
e2fsck 1.41.12 (17-May-2010)
Benutze EXT2FS Library version 1.41.12, 17-May-2010
e2fsck 1.41.11 (14-Mar-2010)
Benutze EXT2FS Library version 1.41.11, 14-Mar-2010
Symptoms: fsck.ext4 -y -f takes nearly a month to fix the structures on
a P4@2,8Ghz, with very little access to the drive and 100% cpu use.
output of fsck looks much like this:
File ??? (Inode #123456, modify time Wed Jul 22 16:20:23 2009)
block Nr. 6144 double block(s), used with four file(s):
<filesystem metadata>
??? (Inode #123457, mod time Wed Jul 22 16:20:23 2009)
??? (Inode #123458, mod time Wed Jul 22 16:20:23 2009)
...
multiply claimed block map? Yes
Is there an adhoc method of getting my data back faster?
Is the slow performance with lots of hard links a known issue?
--
mit freundlichen Grüßen,
Christian Brandt EDV-Dienstleistungen
Tel 089/89427711, Fax 089/89427712
Kreuzlinger Str.37 82110 Germering
St.Nr. 117/206/91819 Ust-ID DE233256795
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-03-27 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 11:28 Christian Brandt [this message]
2011-03-28 14:43 ` fsck.ext4 taking months Ric Wheeler
2011-03-29 6:03 ` Rogier Wolff
2011-03-29 20:26 ` Christian Brandt
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=4D8F1F75.8010201@psi5.com \
--to=brandtc@psi5.com \
--cc=linux-ext4@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 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).