linux-kernel - Re: Spurious Filesystem corruption with ext3 + large (<400GB) hw RAID partition + SMP

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 31 Jan 2009 18:26:51 +0100
From:	Manfred Wassmann <tux.wassmann@...glemail.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Spurious Filesystem corruption with ext3 + large (<400GB) hw RAID 
	partition + SMP

On Sat, Jan 31, 2009 at 4:19 PM, Henrique de Moraes Holschuh
<hmh@....eng.br> wrote:
> Please reply to the list... and it is probably useful to add which kind of SATA chip the 3Ware card uses.
> I only asked for some information I knew would be required, but probably I won't be able to help much.

Thank you very much and sorry, my reply was intended to go to the list
but it's the first time I use google mail with a list and it is much
different.

Well I have neither hardware nor documents around here and the dmesg
output doesn't tell me anything more than I already stated :(

>> I didn't think it could be the memory because the problem occurs with
>> the 32bit kernel alone but what do you suggest? I only have remote
>> access to the system over the weekend.
>
> Try one of the memtest utils that don't need to run from the boot over the weekend. If nothing fails, run the real thing on Monday.

OK memtest is running but there is one other thing I forgot to
mention, we had the same problem on two different machines.

Furthermore it always affects the ext3 filesystem and not the ext2
partition which is much smaller with only 1GB and mounted r/o on the
final system, but that is where most of the software gets installed.
And the problem is triggered at installation time so don't you think
it should more likely hit the ext2 partition if it is not an ext3
problem?

regards Manfred Wassmann
-- 
Unix "Birthday" on 2009-02-13 23:31:30 UTC
...it's 1234567890 seconds since the epoch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/