xfs
[Top] [All Lists]

Re: xfs file system in process of becoming corrupt; though xfs_repair th

To: Dave Chinner <david@xxxxxxxxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
Subject: Re: xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ (was xfs_dump problem...)
From: "Linda A. Walsh" <xfs@xxxxxxxxx>
Date: Tue, 29 Jun 2010 17:01:12 -0700
In-reply-to: <20100629232532.GA24712@dastard>
References: <4C26A51F.8020909@xxxxxxxxx> <20100628022744.GX6590@dastard> <4C2A749E.4060006@xxxxxxxxx> <20100629232532.GA24712@dastard>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666


Dave Chinner wrote:
---------------------------------------------------------------------------------------------------
Ishtar:/Torrents> 'ls' -ni bad*     ls: cannot access bad/30-Omoide
to Yakusoku (TV saizu|Reinaʼs Ver.).mp3: No such file or directory
ls: cannot access bad/31-Omoide to Yakusoku (TV saizu|Tomoeʼs Ver.).mp3: No 
such file or directory
ls: cannot access bad/32-Omoide to Yakusoku (TV saizu|Nanualʼs Ver.).mp3: No 
such file or directory
bad:
total 0
2359101 ?????????? ? ? ? ?                ? 30-Omoide to Yakusoku (TV 
saizu|Reinaʼs Ver.).mp3
2354946 ?????????? ? ? ? ?                ? 31-Omoide to Yakusoku (TV 
saizu|Tomoeʼs Ver.).mp3
2354949 ?????????? ? ? ? ?                ? 32-Omoide to Yakusoku (TV 
saizu|Nanualʼs Ver.).mp3
ls: cannot access bad2/30-Omoide to Yakusoku (TV saizu|Reinaʼs Ver.).mp3: No 
such file or directory
ls: cannot access bad2/31-Omoide to Yakusoku (TV saizu|Tomoeʼs Ver.).mp3: No 
such file or directory
ls: cannot access bad2/32-Omoide to Yakusoku (TV saizu|Nanualʼs Ver.).mp3: No 
such file or directory

Those file names have a weird character in them - are you sure that
the terminal supports that character set and is not mangling it and
hence not matching what is actually stored on disk?
-----
Those files were 'fine' before today.

I know it is not a terminal problem --
I told ls to list all files in the directory -- then it says "no such file".

Can you say that "*" shouldn't match everything?

Those question marks are in the place for the size!

There are no weird characters in those file names.

Here are the same files in another directory:
mp3> ll 3*
-rwx------ 1 3255702 2010-06-14 10:54 30-Omoide to Yakusoku (TV saizu|Reinaʼs 
Ver.).mp3*
-rwx------ 1 3272004 2010-06-14 10:54 31-Omoide to Yakusoku (TV saizu|Tomoeʼs 
Ver.).mp3*
-rwx------ 1 3234876 2010-06-14 10:54 32-Omoide to Yakusoku (TV saizu|Nanualʼs 
Ver.).mp3*


The fields it can't display are the file size, time and dates!  The names 
display ok!

How can file size, time and date be in unprintable characters that "ls" can't 
display?

<Prev in Thread] Current Thread [Next in Thread>