linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LKML <linux-fsdevel@vger.kernel.org>
Subject: ext3 filesystem which can't be corrected?
Date: Wed, 02 Apr 2008 17:03:34 +0200	[thread overview]
Message-ID: <47F3A046.7020301@wpkg.org> (raw)

I have a ext3 filesystem which can't (?) be corrected with e2fsck - it 
shows files having the same inode, with the same names in the same 
directory.


e2fsck passes the check and does not find any errors (well, the first 
pass showed lots of errors). The filesystem is iSCSI-connected with 
commit=60 mount option, and initiator was brutally disconnected from the 
target several times.


However:

# cd /mnt/1/lost+found/


These are the directories I can't remove:

# ls
#83363275/  #83378623/  #83379228/  #83379558/  #83380843/  #83380850/ 
#83380938/

# cd \#83378623/


Let's see what we have there - four files with exactly the same name and 
inode:

# ls -li
total 16
73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib
73793642 -rw-r----- 179 backuppc backuppc 46 May 14  2007 attrib


Let's remove "attrib" file:

# rm -f attrib

Ouch:

# ls
ls: attrib: No such file or directory
ls: attrib: No such file or directory
ls: attrib: No such file or directory

When I want to browse the directory i.e. in midnight commander (mc), it 
shows me three files in red called "?attrib", dated 1 Jan 1970.


# cd /
# umount /mnt/1
# mount /dev/sda /mnt/1
# cd /mnt/1/lost+found/#83378623/
# ls
attrib  attrib  attrib
# rm attrib
rm: remove regular file `attrib'? y
# ls
ls: attrib: No such file or directory
ls: attrib: No such file or directory


OK, mounting and unmounting just to delete one file is boring, so let's 
try it another way:

# ls
ls: cannot access attrib: No such file or directory
attrib
# echo 3 > /proc/sys/vm/drop_caches
# ls
attrib
# rm attrib
rm: remove regular file `attrib'? y
# ls
#


e2fsck comes from e2fsprogs 1.39 - should I try something newer?


-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2008-04-02 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 15:03 Tomasz Chmielewski [this message]
2008-04-10 16:41 ` ext3 filesystem which can't be corrected? Andreas Dilger
2008-04-10 16:50   ` Tomasz Chmielewski

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=47F3A046.7020301@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-fsdevel@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).