From: Mark Casey <markc@unifiedgroup.com>
To: linux-ext4@vger.kernel.org
Subject: e2fsck repeatedly asks to clear the same entry?
Date: Fri, 23 Nov 2012 12:26:52 -0600 [thread overview]
Message-ID: <k8of5a$sjb$1@ger.gmane.org> (raw)
Hello list,
I'm in a bit of a loop trying to fix my ext4 filesystem; it always goes
like this even after several passes.
> root@host:/home/luser# /root/latest/sbin/e2fsck -f /dev/vgdalr6/lv1
> e2fsck 1.42.5 (29-Jul-2012)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Entry 'A5 11-3' in /share/path/09/Brett/Pines/Flynt's Side Drive - Complete Archive Copy/SA Version Pines/Chris Pics 11-2-10 (268533857) has deleted/unused inode 15115. Clear<y>? yes
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
>
> /dev/vgdalr6/lv1: ***** FILE SYSTEM WAS MODIFIED *****
> /dev/vgdalr6/lv1: 8993801/268697600 files (0.8% non-contiguous), 2152234742/4299161600 blocks
> root@host:/home/luser#
Would anyone have any suggestions how to proceed?
The cause of this is that I did an unsupported resize (a shrink) by
commenting out one of resize2fs' checks...as described here: (note I'm
not claiming this as "permission"; I knew it might not work)
http://article.gmane.org/gmane.comp.file-systems.ext4/35375
resize2fs gave no indication of trouble but the check that followed
didn't go perfectly. 6 or 7 directory entries needed to be cleared and
I've restored ~10gb from backup, but otherwise this current issue with
the directory 'A5 11-3' is the only symptom presenting. I have most of
the e2fsck log that followed the resize in case that would be of use.
Thank you,
Mark
next reply other threads:[~2012-11-23 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 18:26 Mark Casey [this message]
2012-11-23 19:18 ` e2fsck repeatedly asks to clear the same entry? Andreas Dilger
2012-11-24 6:27 ` Mark Casey
2012-11-24 19:17 ` Andreas Dilger
2012-11-26 3:52 ` Mark Casey
2012-11-24 17:34 ` Eric Sandeen
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='k8of5a$sjb$1@ger.gmane.org' \
--to=markc@unifiedgroup.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).