kernel-packages team mailing list archive

["Joshua R. Poulson" <jopoulso@xxxxxxxxxxxxx>]

We are still seeing some errors.

Here are the results for 15.04 running the upstream 4.1.0-rc8-next built 2015-06-22.
I’m still seeing some error messages, though multipath is at least able to recognize the vFC disks.

root@ubuntu1504:~# multipath -ll
360080e500017c5e2000016bf53d7c0c8 dm-3 IBM,1814      FAStT
size=279G features='1 queue_if_no_path' hwhandler='1 rdac' wp=rw
|-+- policy='round-robin 0' prio=6 status=active
| |- 4:0:1:0 sdd 8:48 active ready running
| `- 4:0:3:0 sdf 8:80 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
  |- 4:0:0:0 sdc 8:32 active ghost running
  `- 4:0:2:0 sde 8:64 active ghost running
360022480252826b1808fb8b00780a6be dm-2 Msft,Virtual Disk
size=4.0G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 3:0:0:0 sdb 8:16 active ready running

Dmesg messages:
[  140.678778] device-mapper: table: 252:5: multipath: error getting device
[  140.678888] device-mapper: ioctl: error adding target to table
[  140.706106] device-mapper: table: 252:5: multipath: error getting device
[  140.706282] device-mapper: ioctl: error adding target to table

These 2 items might be specific to the FC or can be ignored, still mentioning them for confirmation:
1.	The [current] illegal request is still showing up.
2.	“failure for create/reload map” messages still appear.

Should we open a new bug or continue with this one?

-- 
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/1439780

Title:
  [Hyper-V] Fiber Channel critical target error

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  System details:
  Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #11~lp1423343v201503311833 SMP Tue Mar 31 17:40:01 UTC 2015 (Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3)

  Ubuntu 3.19.0-11
  Ubuntu Vivid 15.04 64bit custom kernel
  Platform: WS2012R2

  Using a fiber channel disk partition ( dev/sde1 in this example) outputs the following error:
  ​
  [ 1307.744496] blk_update_request: critical target error, dev sde, sector 0
  [ 1396.052488] blk_update_request: critical target error, dev sde, sector 0
  [ 1456.216570] blk_update_request: critical target error, dev sde, sector 0

  Creating a partition works, reading too, but first time writing it
  hangs for around 20 seconds and after a couple more writes the
  partition goes into read-only mode:

  #echo "test1" > test1.txt
  *hangs for 30 seconds*
  blk_update_request: critical target error, dev sde, sector 0
  # echo "test2" > test2.txt
  blk_update_request: critical target error, dev sde, sector 289671192
  Aborting journal on device sde1-8.
  EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal
  EXT4-fs (sde1): Remounting filesystem read-only
  # echo "test string" > sample.txt
  -bash: sample.txt: Read-only file system

  
  Dmesg log:
  [  461.284362] blk_update_request: critical target error, dev sde, sector 0
  [  484.845659] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null)
  [  548.988377] blk_update_request: critical target error, dev sde, sector 0
  [  609.216340] blk_update_request: critical target error, dev sde, sector 289671192
  [  609.221812] Aborting journal on device sde1-8.
  [  612.237503] EXT4-fs error (device sde1): ext4_journal_check_start:56: Detected aborted journal
  [  612.249529] EXT4-fs (sde1): Remounting filesystem read-only

  Additional info:

  cat /proc/version_signature
  Ubuntu 3.19.0-11.11~lp1423343v201503311833-generic 3.19.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439780/+subscriptions