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-next>] [day] [month] [year] [list]
Date:   Mon, 18 Sep 2017 16:14:35 +0530
From:   RAJESH DASARI <raajeshdasari@...il.com>
To:     linux-ext4@...r.kernel.org
Subject: File system corruption after reboot, when rootfs in mounted over nfs

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ