From: Heinz Diehl <htd+ml@fritha.org>
To: linux-xfs@vger.kernel.org
Subject: XFS journal corruption after every reboot/shutdown
Date: Thu, 11 Jan 2018 23:44:51 +0100 [thread overview]
Message-ID: <20180111224451.GA3413@fritha.org> (raw)
Hi,
the root partition on three different Fedora 27 based machines is
XFS-formatted. After every reboot or shutdown, dmesgs shows the following lines after
restarting:
[htd@kiera ~]$ dmesg | grep XFS
[ 2.773271] SGI XFS with ACLs, security attributes, no debug enabled
[ 2.774950] XFS (sda2): Mounting V4 Filesystem
[ 2.851266] XFS (sda2): Starting recovery (logdev: internal)
[ 2.876522] XFS (sda2): Ending recovery (logdev: internal)
/dev/sda2 is the root partition. /home, which also is XFS formatted, is
fine. The journal gets automatically recovered in the boot process and
root mounts just fine. But this happens after every single reboot or
shutdown - on three different machines with two different kernels
(4.14.4 and 4.14.12) and three different harddisks. And it's always
and solely the root partition which is affected.
To me, it looks like the root partition doesn't get properly unmounted
on reboot or shutdown, but I can not find anything in the logs that is
suspicious. I have also looked into systemd sourcecode and the systemd shutdown
process, but can not see that the root partition is actually unmounted.
Do you have any advice what to do further, or any hint on what could be
happening here? Is this behaviour intended?
I have also filed a bug report here because there's F27 on all machines:
https://bugzilla.redhat.com/show_bug.cgi?id=1533620
Many thanks in advance,
Heinz
next reply other threads:[~2018-01-11 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 22:44 Heinz Diehl [this message]
2018-01-11 23:13 ` XFS journal corruption after every reboot/shutdown Dave Chinner
2018-01-11 23:21 ` Eric Sandeen
2018-01-13 8:17 ` Heinz Diehl
2018-01-13 22:31 ` Chris Murphy
2018-01-14 8:41 ` Heinz Diehl
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=20180111224451.GA3413@fritha.org \
--to=htd+ml@fritha.org \
--cc=linux-xfs@vger.kernel.org \
/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