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

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

Message-ID: <20170921082438.qpttlfzkbduzm4i3@rh_laptop>
Date:   Thu, 21 Sep 2017 10:24:38 +0200
From:   Lukas Czerner <lczerner@...hat.com>
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 Thu, Sep 21, 2017 at 09:41:57AM +0530, RAJESH DASARI wrote:
> Could someone please respond to my query.

Hi,

Ted already did, with some questions.

https://www.spinics.net/lists/linux-ext4/msg58327.html

-Lukas

> 
> Thanks,
> Rajesh Dasari.
> 
> 
> On Mon, Sep 18, 2017 at 4:14 PM, RAJESH DASARI <raajeshdasari@...il.com> wrote:
> > Hi ,
> >
> > Could some one please help me with the below issue.
> >
> > I have  booted a mips based hardware with linux (4.4.36 kernel
> > )image(over tftp) and rootfs over nfs by passing nfsroot command line
> > option to the kernel.
> >
> > rootfs is mounted under / in my hardware environment.
> >
> > 192.168.113.254:/rootfs / type nfs
> > (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.113.254,mountvers=3,mountproto=tcp,local_lock=all,addr=192.168.113.254)
> >
> > I have a hard disk and i am mounting  it on /mnt , this /mnt directory
> > is part of nfsroot.
> >
> > e2fsck -f -y /dev/sda1 -> disk is clean with no errors.
> >
> > mount -t ext2 /dev/sda1 /mnt  (mount was successful ,mounting ext2 using ext4)
> > touch /mnt/test.log  -> this command is failing.
> > umount /mnt
> > reboot
> >
> > when i was executing the above commands in a loop i see that /dev/sda1
> > file system is getting corrupted. touch command is failing with
> > "ext4_find_dest_de:1809: inode #2: block 771: comm touch: bad entry in
> > directory: rec_len %4 !=0 -offset =0(0),
> > inode=4278190080,rec_len=54507,name_len=229 touch : cannot touch
> > /mnt/test.log structure needs clearing" error. I am able to reproduce
> > this issue always when i boot rootfs over nfs , if i boot from hard
> > disk , i am not noticing the issue .
> >
> >
> >
> > Could someone please help me on this , what could cause the ext4 file
> > system corruption.
> >
> > Thanks,
> > Rajesh Dasari.