From: "markus hansen" <hansenmarkus@gmx.de>
To: linux-ext4@vger.kernel.org
Subject: fsck.ext4 multiply-claimed blocks
Date: Wed, 03 Aug 2011 11:10:53 +0200 [thread overview]
Message-ID: <20110803091053.316860@gmx.net> (raw)
Hi,
I have a huge crashed ext4 filesystem with lots of Hardlinks in it. fsck.ext4 has not completed after 24h, handling "multiply-claimed blocks" eats the time. Stupid beginner question: Are the offered two Options (a) "copy multiply claimed blocks" (b) "delete inodes" useful in case multiple hardlinks point to same blocks? Isnt it ok in that case, that blocks are multiply claimed?
regards,
Markus
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
--
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-08-03 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 9:10 markus hansen [this message]
2011-08-03 16:02 ` fsck.ext4 multiply-claimed blocks Andreas Dilger
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=20110803091053.316860@gmx.net \
--to=hansenmarkus@gmx.de \
--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