cephfs mounting error after kernel image update on ubuntu 16.04 LTS
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-aws (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I experienced an issue with mounting CephFS shares after upgrading linux-image to linux-image-
After rollback and downgrade back to linux-images linux-image-
While having booted with the updated kernel image and while the mount error was present (error message on console: input/output error) I noticed the following logging in syslog - maybe that helps:
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.949106] FS-Cache: Loaded
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.960194] Key type ceph registered
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.960267] libceph: loaded (mon/osd proto 15/24)
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.972192] FS-Cache: Netfs 'ceph' registered for caching
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.972201] ceph: loaded (mds proto 32)
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.995058] libceph: client582051 fsid 0860999e-
Dec 8 08:42:00 ip-172-31-29-78 kernel: [ 9.997806] libceph: mon0 172.31.10.252:6789 session established
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.005674] ceph: problem parsing mds trace -5
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.010254] ceph: mds parse_reply err -5
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.020073] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031179] header: 00000000: 02 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031181] header: 00000010: 1a 00 7f 00 01 00 4c 01 00 00 00 00 00 00 00 00 ......L.........
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031183] header: 00000020: 00 00 00 00 02 00 00 00 00 00 00 00 00 01 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031184] header: 00000030: 00 27 ed 97 95 .'...
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031185] front: 00000000: 01 01 00 00 00 00 00 00 8f 00 00 00 01 00 01 01 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031186] front: 00000010: 01 00 00 01 00 00 00 00 00 00 00 fe ff ff ff ff ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031187] front: 00000020: ff ff ff 00 00 00 00 e0 c5 15 00 00 00 00 00 01 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031188] front: 00000030: 00 00 00 00 00 00 00 55 01 00 00 00 00 00 00 32 .......U.......2
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031189] front: 00000040: 1d 33 00 00 00 00 00 01 00 00 00 00 00 00 00 01 .3..............
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031190] front: 00000050: 00 00 00 00 00 00 00 01 00 00 40 00 01 00 00 00 ..........@.....
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031191] front: 00000060: 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 ..@.............
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031192] front: 00000070: 01 00 00 00 44 bc 16 5a b7 99 78 06 44 bc 16 5a ....D..Z..x.D..Z
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031193] front: 00000080: b7 99 78 06 00 00 00 00 00 00 00 00 00 00 00 00 ..x.............
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031194] front: 00000090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031195] front: 000000a0: ff ff ff ff ff ff ff ff 00 00 00 00 ed 41 00 00 .............A..
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031196] front: 000000b0: f2 01 00 00 f0 01 00 00 01 00 00 00 00 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031197] front: 000000c0: 00 00 00 00 05 00 00 00 00 00 00 00 a1 72 a3 34 .............r.4
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031198] front: 000000d0: 03 00 00 00 b3 1b 01 00 00 00 00 00 6c 3a 00 00 ............l:..
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031199] front: 000000e0: 00 00 00 00 56 50 2a 5a d2 06 94 3b 00 00 00 00 ....VP*Z...;....
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031200] front: 000000f0: 00 00 00 00 02 00 00 00 00 00 00 00 04 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031201] front: 00000100: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031202] front: 00000110: 00 00 00 00 00 00 00 00 30 00 00 00 01 00 00 00 ........0.......
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031203] front: 00000120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031204] front: 00000130: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 ................
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031205] front: 00000140: 00 00 00 00 00 00 00 00 00 00 00 00 ............
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031206] footer: 00000000: c6 c2 b6 a6 00 00 00 00 00 00 00 00 9d 1f 2d f1 ..............-.
Dec 8 08:42:01 ip-172-31-29-78 kernel: [ 10.031207] footer: 00000010: 44 a5 8c c9 05 D....
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.4.0-1043-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
Date: Mon Dec 11 09:26:11 2017
Ec2AMI: ami-8504fdea
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: t2.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-aws
UpgradeStatus: No upgrade log present (probably fresh install)
| Thomas Blick (thbl) wrote | #1 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in linux-aws (Ubuntu): | |
| status: | New → Confirmed |
| Tim (timw-suqld) wrote | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.