Message-ID: <4C2A87FF.7090804@dermichi.com>
Date: Wed, 30 Jun 2010 01:55:43 +0200
From: Michael Weissenbacher <mw@dermichi.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4
MIME-Version: 1.0
To: xfs@oss.sgi.com
Subject: Re: xfs file system in process of becoming corrupt; though	xfs_repair
 thinks it's fine! ;-/ (was xfs_dump problem...)
References: <4C26A51F.8020909@tlinx.org> <20100628022744.GX6590@dastard>	<4C2A749E.4060006@tlinx.org> <20100629232532.GA24712@dastard>
In-Reply-To: <20100629232532.GA24712@dastard>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi!
>> 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
> 
> ...
>
> If there are no problems reported by repair, then I suspect that
> it's a terminal level problem...
> 
Looking at this i remember having similar problems when my filesystems
was mounted with inode64 before and after i left out that parameter. So
Linda, could you re-try mounting the fs with "inode64".

cheers,
Michael