[Kernel-packages] [Bug 1596550] [NEW] Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0
Public bug reported: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,nobarrier,logbufs=8,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: New Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,nobarrier,logbufs=8,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] Re: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0
** Description changed: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: - [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address - = 0xc06bdda2 + = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. - This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,nobarrier,logbufs=8,noquota + This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a + XFS filesystem formatted with 1024 as inode size and mounted with + + rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota + + For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Incomplete Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691140/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691137/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691141/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691135/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691136/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691134/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691133/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691139/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691138/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] Re: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0
apport information ** Tags added: apport-collected ** Description changed: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 10 13:19 seq + crw-rw 1 root audio 116, 33 Jun 10 13:19 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + IwConfig: Error: [Errno 2] No such file or directory + MachineType: HP ProLiant DL380 Gen9 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M + ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-22-generic N/A + linux-backports-modules-4.4.0-22-generic N/A + linux-firmware1.127.15 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty + Uname: Linux 4.4.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/20/2015 + dmi.bios.vendor: HP + dmi.bios.version: P89 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL380 Gen9 + dmi.sys.vendor: HP ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1596550/+attachment/4691132/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Confirmed Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs
[Kernel-packages] [Bug 1596550] Re: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0
Hi Joseph, we only stress tested from the beginning with a 4.4 kernel so I can not rule out if the was introduced past 3.13 or persisted in earlier versions already. I'll look if I can test this in a smaller scale with a 4.7 kernel, we can not switch for 4.7 on our current system yet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Incomplete Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1482304] Re: Upgrade i40e and i40evf driver to latest
FYI, this combination seem to work now: Kernel 3.13.0-96-generic i40e NIC Driver 1.4.25 NVM Firmware package 5.04 have not done any extensive testing yet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1482304 Title: Upgrade i40e and i40evf driver to latest Status in linux package in Ubuntu: Confirmed Bug description: It appears that the latest i40e driver in Trusty is 0.3.36-k. We've been experiencing some kernel panics with this driver and have found that it looks like bringing the driver up to the latest 1.2.48 has alleviated some of the kernel panics on boot. Is this something we could look at getting upgraded to a more modern revision of the driver? Thanks Output of Panic (Using Intel x710) [3.143088] i40e :05:00.0 p1p1: NIC Link is Up [3.301138] Switched to clocksource tsc [6.216639] random: nonblocking pool is initialized [8.934783] [ cut here ] [8.934805] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [8.934808] NETDEV WATCHDOG: p1p1 (i40e): transmit queue 0 timed out [8.934828] Modules linked in: joydev hid_generic gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw usbhid hid lpc_ich hpilo ioatdma dca ipmi_si shpchp wmi acpi_power_meter mac_hid lp parport psmouse i40e vxlan ip_tunnel ptp hpsa pps_core [8.934874] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-57-generic #95-Ubuntu [8.934877] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 05/06/2015 [8.934878] 0009 88103fc03d98 817232f0 88103fc03de0 [8.934891] 88103fc03dd0 8106784d 881028d18000 [8.934895] 881023734f40 0040 88103fc03e30 [8.934904] Call Trace: [8.934905][] dump_stack+0x45/0x56 [8.934921] [] warn_slowpath_common+0x7d/0xa0 [8.934925] [] warn_slowpath_fmt+0x4c/0x50 [8.934928] [] dev_watchdog+0x276/0x280 [8.934935] [] ? dev_graft_qdisc+0x80/0x80 [8.934942] [] call_timer_fn+0x36/0x100 [8.934946] [] ? dev_graft_qdisc+0x80/0x80 [8.934950] [] run_timer_softirq+0x1ef/0x2f0 [8.934957] [] __do_softirq+0xec/0x2c0 [8.934961] [] irq_exit+0x105/0x110 [8.934971] [] smp_apic_timer_interrupt+0x45/0x60 [8.934976] [] apic_timer_interrupt+0x6d/0x80 [8.934977][] ? cpuidle_enter_state+0x52/0xc0 [8.934986] [] cpuidle_idle_call+0xb9/0x1f0 [8.934994] [] arch_cpu_idle+0xe/0x30 [8.935000] [] cpu_startup_entry+0xc5/0x290 [8.935008] [] rest_init+0x77/0x80 [8.935016] [] start_kernel+0x438/0x443 [8.935021] [] ? repair_env_string+0x5c/0x5c [8.935023] [] ? early_idt_handlers+0x120/0x120 [8.935027] [] x86_64_start_reservations+0x2a/0x2c [8.935030] [] x86_64_start_kernel+0x143/0x152 [8.935034] ---[ end trace fabec2b76d314b12 ]--- [8.935037] i40e :05:00.0 p1p1: tx_timeout recovery level 0 [8.935071] i40e :05:00.0: VSI reinit requested [8.945435] i40e :05:00.0 p1p1: NIC Link is Up [ 14.856689] i40e :05:00.0: Detected Tx Unit Hang [ 14.856689] VSI <518> [ 14.856689] Tx Queue <0> [ 14.856689] next_to_use <1> [ 14.856689] next_to_clean<0> [ 14.856697] i40e :05:00.0: tx_bi[next_to_clean] [ 14.856697] time_stamp [ 14.856697] jiffies [ 14.856699] i40e :05:00.0: tx hang detected on queue 0, resetting adapter [ 14.856701] i40e :05:00.0 p1p1: tx_timeout recovery level 1 [ 14.882582] i40e :05:00.0: i40e_ptp_init: added PHC on p1p1 [ 14.899577] i40e :05:00.0 p1p1: NIC Link is Up [ 14.899623] i40e :05:00.0: reset complete [ 24.928762] i40e :05:00.0 p1p1: tx_timeout recovery level 2 [ 25.876839] i40e :05:00.1: i40e_ptp_init: added PHC on p1p2 [ 25.889067] i40e :05:00.1: reset complete [ 25.917938] i40e :05:00.0: i40e_ptp_init: added PHC on p1p1 [ 25.934578] i40e :05:00.0 p1p1: NIC Link is Up [ 25.934621] i40e :05:00.0: reset complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1596550] Re: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0
FYI I have seen similar issues on 3.18 on a different OS so I assume this issue is longer persistent than anticipated. So far I was not able to reproduce in a test environment where I can try different kernels. Not sure how we should proceed here ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: New Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705349] [NEW] tgtd blocked with hitting hung_task_timeout_secs
Public bug reported: We see an issue where an IO thread of tgtd violates the hung task timeout and vmstat reports >20% wait on IO while we are not seeing a issue with the underlying hardware (iowait and svc time) inside IO stat. We already limited the kernel parameters vm.dirty_background_ratio=5 vm.dirty_ratio=10 to reduce the impact of massive dirty blocks hitting the storage which is still based on spinning rust in a RAID 10 array. This is based on kernel 3.13.0-96-generic with the deadline IO scheduler and we got the following stack trace: [25300644.048029] INFO: task tgtd:27827 blocked for more than 300 seconds. [25300644.048065] Not tainted 3.13.0-96-generic #143-Ubuntu [25300644.048100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25300644.048166] tgtdD 88103fc13180 0 27827 1 0x0080 [25300644.048168] 88019cc61c78 0086 880125791800 00013180 [25300644.048171] 88019cc61fd8 00013180 880125791800 88103fc13a18 [25300644.048173] 88207ffef6e8 88019cc61d00 0002 81151e90 [25300644.048176] Call Trace: [25300644.048178] [] ? wait_on_page_read+0x60/0x60 [25300644.048190] [] io_schedule+0x9d/0x130 [25300644.048192] [] sleep_on_page+0xe/0x20 [25300644.048194] [] __wait_on_bit_lock+0x48/0xb0 [25300644.048196] [] __lock_page+0x6a/0x70 [25300644.048198] [] ? autoremove_wake_function+0x40/0x40 [25300644.048200] [] write_cache_pages+0x2f8/0x4b0 [25300644.048202] [] ? global_dirtyable_memory+0x50/0x50 [25300644.048205] [] ? get_futex_key+0x1d8/0x2c0 [25300644.048207] [] ? send_signal+0x3e/0x80 [25300644.048209] [] generic_writepages+0x40/0x60 [25300644.048212] [] do_writepages+0x1e/0x40 [25300644.048213] [] __filemap_fdatawrite_range+0x59/0x60 [25300644.048215] [] filemap_write_and_wait_range+0x2a/0x70 [25300644.048217] [] blkdev_fsync+0x1b/0x50 [25300644.048219] [] do_fsync+0x51/0x80 [25300644.048221] [] SyS_fdatasync+0x13/0x20 [25300644.048223] [] system_call_fastpath+0x1a/0x1f UPTIME report 16:30:01 up 292 days, 22:34, 0 users, load average: 9.89, 8.58, 5.33 FREE report total used free sharedbuffers cached Mem: 131777272 116935780 14841492828 1106297401123368 -/+ buffers/cache:5182672 126594600 Swap: 7999484 90047990480 VMSTAT report procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 10 8 14493 108036 109700 7 22700 0 0 100 0 0 0 10 8 14494 108036 109700 0 0 690 1149 0 0 78 22 0 0 10 8 14494 108036 109700 0 8 736 1442 0 0 78 22 0 IOSTAT report Linux 3.13.0-96-generic (cinder18) 07/19/2017 _x86_64_(32 CPU) 07/19/2017 04:30:03 PM avg-cpu: %user %nice %system %iowait %steal %idle 0.350.000.080.070.00 99.50 Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0.00 3.970.40 10.89 1.7563.1611.51 0.000.160.130.16 0.01 0.01 sdb 51.40 107.252.20 15.89 215.29 7198.82 819.79 0.073.893.263.97 0.60 1.08 sdc 0.00 0.000.000.00 0.00 0.00 8.00 0.000.110.110.00 0.11 0.00 dm-0 0.00 0.000.000.00 0.00 0.01 8.00 0.00 11.760.66 14.98 0.17 0.00 dm-1 0.00 0.000.01 14.86 0.1963.13 8.52 0.000.153.100.15 0.00 0.01 dm-2 0.00 0.000.000.00 0.03 0.0213.67 0.001.071.660.69 0.47 0.00 dm-18 0.00 0.000.000.00 0.00 0.00 8.00 0.003.513.514.00 3.51 0.00 dm-10 0.00 0.000.010.00 0.02 0.00 8.00 0.001.761.760.00 0.41 0.00 dm-28 0.00 0.000.000.02 0.00 0.06 8.00 0.001.395.761.20 0.06 0.00 dm-29 0.00 0.000.000.00 0.00 0.01 8.00 0.003.629.632.97 0.02 0.00 dm-30 0.00 0.000.000.01 0.01 0.03 8.00 0.002.992.843.03 0.03 0.00 dm-24 0.00 0.000.000.00 0.00 0.00 8.00 0.000.040.040.00 0.04 0.00 dm-25 0.00 0.000.000.25 0.00 0.99 8.00 0.006.273.236.27 0.00 0.00 dm-35 0.00 0.000.000.00 0.00 0.01 8.00 0.002.472.052.50 0.01 0.00 dm-36 0.00 0.000.000.00 0.00 0.00 8.00 0.00
[Kernel-packages] [Bug 1705349] Re: tgtd blocked with hitting hung_task_timeout_secs
** Attachment added: "apport.linux-image-3.13.0-96-generic.30pmetzp.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705349/+attachment/4917821/+files/apport ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705349 Title: tgtd blocked with hitting hung_task_timeout_secs Status in linux package in Ubuntu: New Bug description: We see an issue where an IO thread of tgtd violates the hung task timeout and vmstat reports >20% wait on IO while we are not seeing a issue with the underlying hardware (iowait and svc time) inside IO stat. We already limited the kernel parameters vm.dirty_background_ratio=5 vm.dirty_ratio=10 to reduce the impact of massive dirty blocks hitting the storage which is still based on spinning rust in a RAID 10 array. This is based on kernel 3.13.0-96-generic with the deadline IO scheduler and we got the following stack trace: [25300644.048029] INFO: task tgtd:27827 blocked for more than 300 seconds. [25300644.048065] Not tainted 3.13.0-96-generic #143-Ubuntu [25300644.048100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25300644.048166] tgtdD 88103fc13180 0 27827 1 0x0080 [25300644.048168] 88019cc61c78 0086 880125791800 00013180 [25300644.048171] 88019cc61fd8 00013180 880125791800 88103fc13a18 [25300644.048173] 88207ffef6e8 88019cc61d00 0002 81151e90 [25300644.048176] Call Trace: [25300644.048178] [] ? wait_on_page_read+0x60/0x60 [25300644.048190] [] io_schedule+0x9d/0x130 [25300644.048192] [] sleep_on_page+0xe/0x20 [25300644.048194] [] __wait_on_bit_lock+0x48/0xb0 [25300644.048196] [] __lock_page+0x6a/0x70 [25300644.048198] [] ? autoremove_wake_function+0x40/0x40 [25300644.048200] [] write_cache_pages+0x2f8/0x4b0 [25300644.048202] [] ? global_dirtyable_memory+0x50/0x50 [25300644.048205] [] ? get_futex_key+0x1d8/0x2c0 [25300644.048207] [] ? send_signal+0x3e/0x80 [25300644.048209] [] generic_writepages+0x40/0x60 [25300644.048212] [] do_writepages+0x1e/0x40 [25300644.048213] [] __filemap_fdatawrite_range+0x59/0x60 [25300644.048215] [] filemap_write_and_wait_range+0x2a/0x70 [25300644.048217] [] blkdev_fsync+0x1b/0x50 [25300644.048219] [] do_fsync+0x51/0x80 [25300644.048221] [] SyS_fdatasync+0x13/0x20 [25300644.048223] [] system_call_fastpath+0x1a/0x1f UPTIME report 16:30:01 up 292 days, 22:34, 0 users, load average: 9.89, 8.58, 5.33 FREE report total used free sharedbuffers cached Mem: 131777272 116935780 14841492828 1106297401123368 -/+ buffers/cache:5182672 126594600 Swap: 7999484 90047990480 VMSTAT report procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 10 8 14493 108036 109700 7 22700 0 0 100 0 0 0 10 8 14494 108036 109700 0 0 690 1149 0 0 78 22 0 0 10 8 14494 108036 109700 0 8 736 1442 0 0 78 22 0 IOSTAT report Linux 3.13.0-96-generic (cinder18) 07/19/2017 _x86_64_(32 CPU) 07/19/2017 04:30:03 PM avg-cpu: %user %nice %system %iowait %steal %idle 0.350.000.080.070.00 99.50 Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0.00 3.970.40 10.89 1.7563.1611.51 0.000.160.130.16 0.01 0.01 sdb 51.40 107.252.20 15.89 215.29 7198.82 819.79 0.073.893.263.97 0.60 1.08 sdc 0.00 0.000.000.00 0.00 0.00 8.00 0.000.110.110.00 0.11 0.00 dm-0 0.00 0.000.000.00 0.00 0.01 8.00 0.00 11.760.66 14.98 0.17 0.00 dm-1 0.00 0.000.01 14.86 0.1963.13 8.52 0.000.153.100.15 0.00 0.01 dm-2 0.00 0.000.000.00 0.03 0.0213.67 0.001.071.660.69 0.47 0.00 dm-18 0.00 0.000.000.00 0.00 0.00 8.00 0.003.513.514.00 3.51 0.00 dm-10 0.00 0.000.010.00 0.02 0.00 8.00 0.001.761.760.00 0.41 0.00 dm-28 0.00 0.000.000.02 0.00 0.06 8.00 0.001.395.761.20 0.06 0.00 dm-29 0.00 0.000.000.00 0.00 0.0
[Kernel-packages] [Bug 1705349] Re: tgtd blocked with hitting hung_task_timeout_secs
Logs are attached, apport-collect could not be installed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705349 Title: tgtd blocked with hitting hung_task_timeout_secs Status in linux package in Ubuntu: Confirmed Bug description: We see an issue where an IO thread of tgtd violates the hung task timeout and vmstat reports >20% wait on IO while we are not seeing a issue with the underlying hardware (iowait and svc time) inside IO stat. We already limited the kernel parameters vm.dirty_background_ratio=5 vm.dirty_ratio=10 to reduce the impact of massive dirty blocks hitting the storage which is still based on spinning rust in a RAID 10 array. This is based on kernel 3.13.0-96-generic with the deadline IO scheduler and we got the following stack trace: [25300644.048029] INFO: task tgtd:27827 blocked for more than 300 seconds. [25300644.048065] Not tainted 3.13.0-96-generic #143-Ubuntu [25300644.048100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25300644.048166] tgtdD 88103fc13180 0 27827 1 0x0080 [25300644.048168] 88019cc61c78 0086 880125791800 00013180 [25300644.048171] 88019cc61fd8 00013180 880125791800 88103fc13a18 [25300644.048173] 88207ffef6e8 88019cc61d00 0002 81151e90 [25300644.048176] Call Trace: [25300644.048178] [] ? wait_on_page_read+0x60/0x60 [25300644.048190] [] io_schedule+0x9d/0x130 [25300644.048192] [] sleep_on_page+0xe/0x20 [25300644.048194] [] __wait_on_bit_lock+0x48/0xb0 [25300644.048196] [] __lock_page+0x6a/0x70 [25300644.048198] [] ? autoremove_wake_function+0x40/0x40 [25300644.048200] [] write_cache_pages+0x2f8/0x4b0 [25300644.048202] [] ? global_dirtyable_memory+0x50/0x50 [25300644.048205] [] ? get_futex_key+0x1d8/0x2c0 [25300644.048207] [] ? send_signal+0x3e/0x80 [25300644.048209] [] generic_writepages+0x40/0x60 [25300644.048212] [] do_writepages+0x1e/0x40 [25300644.048213] [] __filemap_fdatawrite_range+0x59/0x60 [25300644.048215] [] filemap_write_and_wait_range+0x2a/0x70 [25300644.048217] [] blkdev_fsync+0x1b/0x50 [25300644.048219] [] do_fsync+0x51/0x80 [25300644.048221] [] SyS_fdatasync+0x13/0x20 [25300644.048223] [] system_call_fastpath+0x1a/0x1f UPTIME report 16:30:01 up 292 days, 22:34, 0 users, load average: 9.89, 8.58, 5.33 FREE report total used free sharedbuffers cached Mem: 131777272 116935780 14841492828 1106297401123368 -/+ buffers/cache:5182672 126594600 Swap: 7999484 90047990480 VMSTAT report procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 10 8 14493 108036 109700 7 22700 0 0 100 0 0 0 10 8 14494 108036 109700 0 0 690 1149 0 0 78 22 0 0 10 8 14494 108036 109700 0 8 736 1442 0 0 78 22 0 IOSTAT report Linux 3.13.0-96-generic (cinder18) 07/19/2017 _x86_64_(32 CPU) 07/19/2017 04:30:03 PM avg-cpu: %user %nice %system %iowait %steal %idle 0.350.000.080.070.00 99.50 Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0.00 3.970.40 10.89 1.7563.1611.51 0.000.160.130.16 0.01 0.01 sdb 51.40 107.252.20 15.89 215.29 7198.82 819.79 0.073.893.263.97 0.60 1.08 sdc 0.00 0.000.000.00 0.00 0.00 8.00 0.000.110.110.00 0.11 0.00 dm-0 0.00 0.000.000.00 0.00 0.01 8.00 0.00 11.760.66 14.98 0.17 0.00 dm-1 0.00 0.000.01 14.86 0.1963.13 8.52 0.000.153.100.15 0.00 0.01 dm-2 0.00 0.000.000.00 0.03 0.0213.67 0.001.071.660.69 0.47 0.00 dm-18 0.00 0.000.000.00 0.00 0.00 8.00 0.003.513.514.00 3.51 0.00 dm-10 0.00 0.000.010.00 0.02 0.00 8.00 0.001.761.760.00 0.41 0.00 dm-28 0.00 0.000.000.02 0.00 0.06 8.00 0.001.395.761.20 0.06 0.00 dm-29 0.00 0.000.000.00 0.00 0.01 8.00 0.003.629.632.97 0.02 0.00 dm-30 0.00 0.000.000.
[Kernel-packages] [Bug 1705349] Re: tgtd blocked with hitting hung_task_timeout_secs
That issue did seem to be load induced, nothing has changed on the system side since we did not update any packages. We will update the kernel to the latest trusty first and if it still persists to either the xenial kernel or newer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705349 Title: tgtd blocked with hitting hung_task_timeout_secs Status in linux package in Ubuntu: Incomplete Bug description: We see an issue where an IO thread of tgtd violates the hung task timeout and vmstat reports >20% wait on IO while we are not seeing a issue with the underlying hardware (iowait and svc time) inside IO stat. We already limited the kernel parameters vm.dirty_background_ratio=5 vm.dirty_ratio=10 to reduce the impact of massive dirty blocks hitting the storage which is still based on spinning rust in a RAID 10 array. This is based on kernel 3.13.0-96-generic with the deadline IO scheduler and we got the following stack trace: [25300644.048029] INFO: task tgtd:27827 blocked for more than 300 seconds. [25300644.048065] Not tainted 3.13.0-96-generic #143-Ubuntu [25300644.048100] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [25300644.048166] tgtdD 88103fc13180 0 27827 1 0x0080 [25300644.048168] 88019cc61c78 0086 880125791800 00013180 [25300644.048171] 88019cc61fd8 00013180 880125791800 88103fc13a18 [25300644.048173] 88207ffef6e8 88019cc61d00 0002 81151e90 [25300644.048176] Call Trace: [25300644.048178] [] ? wait_on_page_read+0x60/0x60 [25300644.048190] [] io_schedule+0x9d/0x130 [25300644.048192] [] sleep_on_page+0xe/0x20 [25300644.048194] [] __wait_on_bit_lock+0x48/0xb0 [25300644.048196] [] __lock_page+0x6a/0x70 [25300644.048198] [] ? autoremove_wake_function+0x40/0x40 [25300644.048200] [] write_cache_pages+0x2f8/0x4b0 [25300644.048202] [] ? global_dirtyable_memory+0x50/0x50 [25300644.048205] [] ? get_futex_key+0x1d8/0x2c0 [25300644.048207] [] ? send_signal+0x3e/0x80 [25300644.048209] [] generic_writepages+0x40/0x60 [25300644.048212] [] do_writepages+0x1e/0x40 [25300644.048213] [] __filemap_fdatawrite_range+0x59/0x60 [25300644.048215] [] filemap_write_and_wait_range+0x2a/0x70 [25300644.048217] [] blkdev_fsync+0x1b/0x50 [25300644.048219] [] do_fsync+0x51/0x80 [25300644.048221] [] SyS_fdatasync+0x13/0x20 [25300644.048223] [] system_call_fastpath+0x1a/0x1f UPTIME report 16:30:01 up 292 days, 22:34, 0 users, load average: 9.89, 8.58, 5.33 FREE report total used free sharedbuffers cached Mem: 131777272 116935780 14841492828 1106297401123368 -/+ buffers/cache:5182672 126594600 Swap: 7999484 90047990480 VMSTAT report procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 10 8 14493 108036 109700 7 22700 0 0 100 0 0 0 10 8 14494 108036 109700 0 0 690 1149 0 0 78 22 0 0 10 8 14494 108036 109700 0 8 736 1442 0 0 78 22 0 IOSTAT report Linux 3.13.0-96-generic (cinder18) 07/19/2017 _x86_64_(32 CPU) 07/19/2017 04:30:03 PM avg-cpu: %user %nice %system %iowait %steal %idle 0.350.000.080.070.00 99.50 Device: rrqm/s wrqm/s r/s w/srkB/swkB/s avgrq-sz avgqu-sz await r_await w_await svctm %util sda 0.00 3.970.40 10.89 1.7563.1611.51 0.000.160.130.16 0.01 0.01 sdb 51.40 107.252.20 15.89 215.29 7198.82 819.79 0.073.893.263.97 0.60 1.08 sdc 0.00 0.000.000.00 0.00 0.00 8.00 0.000.110.110.00 0.11 0.00 dm-0 0.00 0.000.000.00 0.00 0.01 8.00 0.00 11.760.66 14.98 0.17 0.00 dm-1 0.00 0.000.01 14.86 0.1963.13 8.52 0.000.153.100.15 0.00 0.01 dm-2 0.00 0.000.000.00 0.03 0.0213.67 0.001.071.660.69 0.47 0.00 dm-18 0.00 0.000.000.00 0.00 0.00 8.00 0.003.513.514.00 3.51 0.00 dm-10 0.00 0.000.010.00 0.02 0.00 8.00 0.001.761.760.00 0.41 0.00 dm-28 0.00 0.000.000.02 0.00 0.06 8.00 0.001.395.761.20 0.06 0.00 dm-29 0.00 0.000.000.00 0.00 0.0
[Kernel-packages] [Bug 1681914] [NEW] XFS kernel modules still trying to flush device after it's been removed
Public bug reported: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.
[Kernel-packages] [Bug 1681914] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860357/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860352/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860356/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860349/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860351/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860350/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Re: XFS kernel modules still trying to flush device after it's been removed
apport information ** Tags added: apport-collected trusty ** Description changed: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 15 2016 seq + crw-rw 1 root audio 116, 33 Sep 15 2016 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=/dev/mapper/lcx-swap00 + InstallationDate: Installed on 2016-02-22 (413 days ago) + InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + MachineType: Dell Inc. PowerEdge R510 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M + ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-25-generic N/A + linux-backports-modules-3.19.0-25-generic N/A + linux-firmware 1.127.14 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty + Uname: Linux 3.19.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/26/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.12.0 + dmi.board.name: 0DPRKF + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 23 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: + dmi.product.name: PowerEdge R510 + dmi.sys.vendor: Dell Inc. ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860348/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix t
[Kernel-packages] [Bug 1681914] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860358/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860354/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860355/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1681914/+attachment/4860353/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: Incomplete Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681914] Re: XFS kernel modules still trying to flush device after it's been removed
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1681914 Title: XFS kernel modules still trying to flush device after it's been removed Status in linux package in Ubuntu: New Bug description: Today I noticed under kernel 3.19.0-25-generic that it still tries to flush to a non existing block device [17985825.406716] XFS (sdl): xfs_log_force: error -5 returned. which is completely removed from the device and udev tree. I found only XFS processes connected to sdl : # ps aux |grep sdl root 2152 0.0 0.0 0 0 ?S<2016 0:00 [xfs-buf/sdl] root 2153 0.0 0.0 0 0 ?S<2016 0:00 [xfs-data/sdl] root 2154 0.0 0.0 0 0 ?S<2016 0:00 [xfs-conv/sdl] root 2155 0.0 0.0 0 0 ?S<2016 0:00 [xfs-cil/sdl] root 2156 0.0 0.0 0 0 ?S 2016 123:33 [xfsaild/sdl] I believe the drive resetted or was replaced and may have came back under a new device number (sdn) but the error messages still persist. At this time I don't know any workaround other than rebooting the machine. The problem seems related or similar as discussed at http://oss.sgi.com/archives/xfs/2016-04/msg00517.html My only problem is that I am not sure if the new device I see, sdn, was indeed the old sdl device. Hence I have not ran any metadata dumps etc. Please advice what is needed to fix this issue ? --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 15 2016 seq crw-rw 1 root audio 116, 33 Sep 15 2016 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/lcx-swap00 InstallationDate: Installed on 2016-02-22 (413 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. PowerEdge R510 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/lcx-root00 ro crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.127.14 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 3.19.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/26/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0DPRKF dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rn0DPRKF:rvrA01:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1008400] Re: Ubuntu server uses CFQ scheduler instead of deadline
In my opinion I also agree to use deadline scheduler for server kernel which is also the same problem on the 4.15 kernel, if a server kernel would still exist. Under trusty we generally saw good performance with deadline scheduler and on a recent SSD based deployment with 4.15 I noticed a large performance regression for random IO until we reverted to deadline. You could argue that the scheduler can be changed at any time but on the contrary I would assume more general suitable parameters from a server distro vs a desktop distro. My larger problem is that this change was seemingly done via https://kernel.ubuntu.com/git/ubuntu/ubuntu-zesty.git/commit/?id=af80b83a2b6184fea27f050948146fcd9a28070d by a test based on kernel compiles etc, which to be honest, is not a standard server use case. Apart from the issue that I could not spot any documentation on the release notes that this has changed. If this has been documented and simply missed it, then please ignore this comment. But now I'm wondering what else has changed now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1008400 Title: Ubuntu server uses CFQ scheduler instead of deadline Status in linux package in Ubuntu: In Progress Bug description: Ubuntu server now uses the '-generic' kernel, as the '-server' kernel doesn't exist anymore. With this change the default server disk scheduler changed from deadline to CFQ. This is very bad for servers, deadline should absolutely be the default for servers. For example we moved some KVM images to an Ubuntu 12.04 server, but we had to revert as we got lots of disk errors and eventually frozen disks on these KVM's due to write timeouts. It took us a while before we found out that this 12.04 server used CFQ, which surprised us a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1008400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
