[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEjEV8A=VNY6tSwzJPG32WqO0yNzvgcv8QsqBYEy6KiX7WVgSA@mail.gmail.com>
Date: Wed, 5 Dec 2012 23:46:03 +0800
From: qixuan wu <wuqixuan@...il.com>
To: Tao Ma <tm@....ma>
Cc: Li Zefan <lizefan@...wei.com>, Eric Sandeen <sandeen@...hat.com>,
Yafang Shao <laoar.shao@...il.com>,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
wuqixuan@...wei.com
Subject: Re: help about ext3 read-only issue on ext3(2.6.16.30)
Hi Tao,
On Wed, Dec 5, 2012 at 9:58 PM, Tao Ma <tm@....ma> wrote:
> Hi qixuan,
> On 12/05/2012 12:16 AM, qixuan wu wrote:
>> Hi Tao, all,
>>
>> I guess it's a memory(or ext3/kenrel) issue. Beause in one
>> machine, after report this issue, the partition is made to readonly,
>> we use debugfs to "ls dir", and it's fine. It can list all files
>> without error. If the disk has issue, when we using ls command, it
>> will give error also. (The dir name is also using debugfs to get by
>> issue inode ID.)
> Are you sure the disk is good? I just checked the code in e2fsprogs, it
> seems that it will not complain if rec_len = 0, and the dir iteration
> just aborts. I guess the right way should be dd the corresponding block
> out, decode and read it in binary format. :(
Good idea, will do it.
Thanks
wuqixuan
> Thanks
> Tao
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists