XFS kernel modules still trying to flush device after it's been removed

Bug #1681914 reported by Bjoern Teipel on 2017-04-11
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

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=<set>
 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.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1681914

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected trusty
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → New

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

It looks like your kernel is behind. The current lts-vivid kernel is: 3.19.0-82. You might want to apply the latest updates. Do you have a way to reproduce the bug?

Changed in linux (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers