From: Peter Chant <pete@petezilla.co.uk>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Mount failure with 5.2.7 but mounts with 5.1.4
Date: Sat, 10 Aug 2019 16:54:59 +0100 [thread overview]
Message-ID: <13654030-d9c5-ad3f-283e-16e6ef6c7bcf@petezilla.co.uk> (raw)
I attempted update an i5 machine today with kernel 5.2.7. Unfortunately
I could not mount the file system. However, reverting the kernel back
to 5.1.4 allowed it to mount with no issue.
This issue is not critical to me, machine boots with older kernel, I
have a backup and the machine is only lightly used anyway. However, I
wonder whether this info is useful to anyone?
I have a spare ext4 root partition on the hard drive of the affected
machine, so I booted to that, with 5.2.7, and got the following behaviour.
dmesg:
[ 55.139154] BTRFS: device fsid 5128caf4-b518-4b65-ae46-b5505281e500
devid 1 transid 66785 /dev/sda4
[ 55.139623] BTRFS info (device sda4): disk space caching is enabled
[ 55.813959] BTRFS critical (device sda4): corrupt leaf: root=5
block=38884884480 slot=1 ino=45745394, invalid inode generation: has
18446744073709551492 expect [0, 66786]
[ 55.817296] BTRFS error (device sda4): block=38884884480 read time
tree block corruption detected
[ 55.817342] BTRFS warning (device sda4): failed to read fs tree: -5
[ 55.834802] BTRFS error (device sda4): open_ctree failed
/var/log/messages:
Aug 10 11:59:05 retreat dbus[903]: [system] Activating service
name='org.freedesktop.PolicyKit1' (using servicehelper)
Aug 10 11:59:05 retreat polkitd[975]: started daemon version 0.105 using
authority implementation `local' version `0.105'
Aug 10 11:59:05 retreat dbus[903]: [system] Successfully activated
service 'org.freedesktop.PolicyKit1'
Aug 10 11:59:31 retreat kernel: [ 55.139154] BTRFS: device fsid
5128caf4-b518-4b65-ae46-b5505281e500 devid 1 transid 66785 /dev/sda4
Aug 10 11:59:31 retreat kernel: [ 55.139623] BTRFS info (device sda4):
disk space caching is enabled
uname -a:
Linux retreat 5.2.7 #1 SMP Wed Aug 7 23:53:42 BST 2019 x86_64 Intel(R)
Core(TM) i5-4430 CPU @ 3.00GHz GenuineIntel GNU/Linux
Rebooting with 5.1.4 showed no problems.
A very similar kernel, with AMD rather than Intel processor options, is
running on the Ryzen machine I am typing this on. I did have my hdd
file system seem to hang, but not sure if that is related.
I have not tried the intel kernel on my laptop, but the laptop is a lot
older, as it is a core2duo.
Seems a bit odd to me that 5.2.7 should show such an issue but 5.1.4 be
OK with it.
Pete
next reply other threads:[~2019-08-10 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 15:54 Peter Chant [this message]
2019-08-10 17:53 ` Mount failure with 5.2.7 but mounts with 5.1.4 Nikolay Borisov
2019-08-10 18:19 ` Pete
2019-08-11 0:13 ` Qu Wenruo
2019-08-11 16:23 ` Pete
2019-08-12 0:21 ` Qu Wenruo
2019-08-13 7:02 ` Pete
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=13654030-d9c5-ad3f-283e-16e6ef6c7bcf@petezilla.co.uk \
--to=pete@petezilla.co.uk \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).