linux-ext4 - Re: help about ext3 read-only issue on ext3(2.6.16.30)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEjEV8A52CHDC9FD9SV+FuuScGe0mJAk69z8o6OHE8kF0bdz_Q@mail.gmail.com>
Date:	Fri, 7 Dec 2012 00:26:26 +0800
From:	qixuan wu <wuqixuan@...il.com>
To:	Yongqiang Yang <xiaoqiangnk@...il.com>
Cc:	Tao Ma <tm@....ma>, Li Zefan <lizefan@...wei.com>,
	Eric Sandeen <sandeen@...hat.com>,
	Yafang Shao <laoar.shao@...il.com>,
	Linux Filesystem Mailing List <linux-fsdevel@...r.kernel.org>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>,
	wuqixuan@...wei.com
Subject: Re: help about ext3 read-only issue on ext3(2.6.16.30)

Hi yongqiang,

On Thu, Dec 6, 2012 at 10:58 AM, Yongqiang Yang <xiaoqiangnk@...il.com> wrote:
> Hi quxuan,
>
> Could you have a test with ext3's journal disabled?   In our
> production, I encountered several cases where deleting on a deleted
> entry happened in ext2, however it doesn''t bother apps, so we didn't
> dig the cause.

We did not test by disable journal. Our customer is usring default
journal mode. Because journal is concern only if the system power off.
If system is continously running and give readonly error, we thought
it's nothing about journal. I am not very clear what about the issue
"deleting on a deleted entry", seems not same as our issue. If you can
more detail about it,  it will be welcomed. :)

> Yongqiang.
>
> On Wed, Dec 5, 2012 at 11:46 PM, qixuan wu <wuqixuan@...il.com> wrote:
>> 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
>
>
>
> --
> Best Wishes
> Yongqiang Yang

Thanks
wuqixuan
--
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