From: Theodore Ts'o <tytso@mit.edu>
To: RAJESH DASARI <raajeshdasari@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: File system corruption after reboot, when rootfs in mounted over nfs
Date: Tue, 19 Sep 2017 09:25:18 -0400 [thread overview]
Message-ID: <20170919132518.krlzjckc4z46ichy@thunk.org> (raw)
In-Reply-To: <CAPXMrf_s10K_b+Eg0emNH_gdQDe-sScyDzgiUhnnj+SYzHK4EA@mail.gmail.com>
On Mon, Sep 18, 2017 at 04:14:35PM +0530, RAJESH DASARI wrote:
>
> 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.
The above commands include running e2fsck? Then it sounds like there
is some kind of device driver bug.
What if you include an e2fsck -f -y /dev/sda1 after the umount? Can
you capture the output from that e2fsck run?
> 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 .
Is it exactly the same kernel in both cases?
More detailed logs would certainly be helpful. There's not enough
detail in your description to do anything other than guess, since
we're not mind readers....
- Ted
next prev parent reply other threads:[~2017-09-19 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 10:44 File system corruption after reboot, when rootfs in mounted over nfs RAJESH DASARI
2017-09-19 13:25 ` Theodore Ts'o [this message]
2017-09-25 5:23 ` RAJESH DASARI
2017-09-25 5:35 ` RAJESH DASARI
2017-09-25 6:48 ` RAJESH DASARI
2017-09-25 14:23 ` Theodore Ts'o
2017-09-21 4:11 ` RAJESH DASARI
2017-09-21 8:24 ` Lukas Czerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170919132518.krlzjckc4z46ichy@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=raajeshdasari@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).