kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #121754
[Bug 1439780] Re: [Hyper-V] Fiber Channel critical target error
Thanks for the update, Alex.
I am performing a "Reverse" bisect between v4.1-rc4 and v4.1-rc5 using the master branch in the mainline repo:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I'll continue the bisect unless you prefer to do it. Here is the
current bisect log:
# good: [e26081808edadfd257c6c9d81014e3b25e9a6118] Linux 4.1-rc4
git bisect good e26081808edadfd257c6c9d81014e3b25e9a6118
# bad: [ba155e2d21f6bf05de86a78dbe5bfd8757604a65] Linux 4.1-rc5
git bisect bad ba155e2d21f6bf05de86a78dbe5bfd8757604a65
# good: [1d82b0baf9abd59ae6f53f3102f4e442043763a4] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
git bisect good 1d82b0baf9abd59ae6f53f3102f4e442043763a4
# good: [0b6280c62026168f79ff4dd1437df131bdfd24f2] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
git bisect good 0b6280c62026168f79ff4dd1437df131bdfd24f2
# good: [b0f155ada4c819f06aa32b4c906e7e76350c7ec1] drm/exynos: dp: Lower level of EDID read success message
git bisect good b0f155ada4c819f06aa32b4c906e7e76350c7ec1
# good: [7ce14f6ff26460819345fe8495cf2dd6538b7cdc] Merge branch 'for-linus-4.1' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs
git bisect good 7ce14f6ff26460819345fe8495cf2dd6538b7cdc
--
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:
Confirmed
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
References