From: Andreas Dilger <adilger@sun.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: LKML <linux-fsdevel@vger.kernel.org>
Subject: Re: ext3 filesystem which can't be corrected?
Date: Thu, 10 Apr 2008 10:41:00 -0600 [thread overview]
Message-ID: <20080410164100.GB5693@webber.adilger.int> (raw)
In-Reply-To: <47F3A046.7020301@wpkg.org>
On Apr 02, 2008 17:03 +0200, Tomasz Chmielewski wrote:
> 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.
Looks like it has unprinting characters. Try
find . -print0 | xargs -0 rm
> e2fsck comes from e2fsprogs 1.39 - should I try something newer?
It is usually best to use the latest version.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-04-10 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 15:03 ext3 filesystem which can't be corrected? Tomasz Chmielewski
2008-04-10 16:41 ` Andreas Dilger [this message]
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=20080410164100.GB5693@webber.adilger.int \
--to=adilger@sun.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mangoo@wpkg.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).