linux-ext4 - Re: File system corruption after reboot, when rootfs in mounted over nfs

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] [day] [month] [year] [list]

Date:   Mon, 25 Sep 2017 10:23:32 -0400
From:   Theodore Ts'o <tytso@....edu>
To:     RAJESH DASARI <raajeshdasari@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: File system corruption after reboot, when rootfs in mounted over
 nfs

On Mon, Sep 25, 2017 at 12:18:40PM +0530, RAJESH DASARI wrote:
> the below steps were executed in a loop for 100 times. I am seeing the
> issue after executing for around 40 iterations.
>     1) e2fsck -y -n /dev/sda1

Are you really using "e2fsck -y -n"?  That makes no sense.

The options "-f -y" would make sense; as would "-f -n".  I'm going to
assume it really was "-f -y" given your other comments, but being
precise is also really important.  You also didn't mention what
version of e2fsck/e2fsprogs you are using, which might be useful, but
given this is a flaky bug, it really doesn't matter, since it's almost
certainly a hardare problem or a device driver problem.

>      2) mount -t ext2 /dev/sda1 /mnt
>      3) touch /mnt/test.log
>      4) umount /mnt
>      5) e2fsck -y -n /dev/sda1
>      6)reboot
> i tried to mount the hard disk as ext2 as my hard disk partition was
> formatted as ext2 device.

I would suggest doing a series of differential diagnosis.  For
example, replacing the hard drive with another hard drive.  Moving
your hard drive to another system, and seeing if you can reproduce the
problem there.  Simply reseating the cables might help.

But this is not a software problem, but clearly a hardware problem,
and so you're probably better office finding someone local who can
help you walk through debugging a hardware problem.

Cheers,

					- Ted