[Bug 1720228] Re: User reports excessive ALUA retry messages
Hi Stefan- fix verified so I changed the tag to verification-done-xenia ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720228 Title: User reports excessive ALUA retry messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756197] [NEW] Kernel panic BUG_ON in 4.4.0-92-generic fs/ext4/inode.c:1894!
ucm(OE)
ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE)
ib_umad(OE) mlx5_ib(OE) mlx4_ib(OE) ib_core(OE) mlx4_en(OE) mlx4_core(OE)
ipmi_ssif mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev
input_leds sb_edac edac_core nvidia_uvm(POE) lpc_ich mei_me mei shpchp
[2503476.691252] 8250_fintek ipmi_si acpi_power_meter wmi mac_hid ipmi_devintf
ipmi_msghandler knem(OE) sunrpc autofs4 nvidia_drm(POE) nvidia_modeset(POE) ses
enclosure ast ixgbe i2c_algo_bit dca ttm nvidia(POE) drm_kms_helper syscopyarea
hid_generic vxlan sysfillrect sysimgblt ip6_udp_tunnel mlx5_core(OE) usbhid
udp_tunnel mlx_compat(OE) megaraid_sas fb_sys_fops hid ahci ptp libahci drm
pps_core mdio fjes
[2503476.692726] CPU: 23 PID: 27629 Comm: kworker/u162:3 Tainted: P D
OE 4.4.0-92-generic #115-Ubuntu
[2503476.693996] Hardware name: NVIDIA DGX-1 with V100/DGX-1 with V100, BIOS
S2W_3A04 08/29/2017
[2503476.695119] task: 884b48124600 ti: 887a04a58000 task.ti:
887a04a58000
[2503476.696215] RIP: 0010:[] []
kthread_data+0x10/0x20
[2503476.697313] RSP: 0018:887a04a5b528 EFLAGS: 00010002
[2503476.698404] RAX: RBX: 0017 RCX:
82109e80
[2503476.699529] RDX: 0017 RSI: 0017 RDI:
884b48124600
[2503476.700569] RBP: 887a04a5b528 R08: R09:
[2503476.701511] R10: 884b48124660 R11: 6c00 R12:
[2503476.702419] R13: 00016dc0 R14: 884b48124600 R15:
887f7ecd6dc0
[2503476.703346] FS: () GS:887f7ecc()
knlGS:
[2503476.704206] CS: 0010 DS: ES: CR0: 80050033
[2503476.705054] CR2: 0028 CR3: 02e0a000 CR4:
003406e0
[2503476.705898] DR0: DR1: DR2:
[2503476.706732] DR3: DR6: fffe0ff0 DR7:
0400
[2503476.707606] Stack:
[2503476.708423] 887a04a5b540 8109b9c1 887f7ecd6dc0
887a04a5b590
[2503476.709253] 8183dab0 887f60547eb0 887a0017
884b48124600
[2503476.710079] 887a04a5c000 884b48124cd0 887a04a5b140
[2503476.710922] Call Trace:
[2503476.711769] [] wq_worker_sleeping+0x11/0x90
[2503476.712594] [] __schedule+0x650/0xa30
[2503476.713414] [] schedule+0x35/0x80
[2503476.714228] [] do_exit+0x775/0xb00
[2503476.715061] [] oops_end+0xa1/0xd0
[2503476.715883] [] die+0x4b/0x70
[2503476.716681] [] do_trap+0xb1/0x140
[2503476.717481] [] do_error_trap+0x89/0x110
[2503476.718280] [] ? ext4_writepage+0x2ec/0x540
[2503476.719099] [] ? do_get_write_access+0x38d/0x490
[2503476.719909] [] ? __wake_up+0x44/0x50
[2503476.720690] [] do_invalid_op+0x20/0x30
[2503476.721468] [] invalid_op+0x1e/0x30
[2503476.722241] [] ? ext4_writepage+0x2ec/0x540
[2503476.723044] [] ? page_mkclean+0x73/0xa0
[2503476.723847] [] ? page_referenced_one+0x1a0/0x1a0
[2503476.724621] [] __writepage+0x12/0x30
[2503476.725396] [] write_cache_pages+0x1ee/0x510
[2503476.726172] [] ? ext4_writepage+0x540/0x540
[2503476.726967] [] ext4_writepages+0x195/0xd30
[2503476.727770] [] ? generic_writepages+0x5b/0x80
[2503476.728545] [] do_writepages+0x1e/0x30
[2503476.729318] [] __writeback_single_inode+0x45/0x340
[2503476.730093] [] writeback_sb_inodes+0x262/0x600
[2503476.730870] [] __writeback_inodes_wb+0x8c/0xc0
[2503476.731696] [] wb_writeback+0x253/0x310
[2503476.732472] [] wb_workfn+0x24d/0x400
[2503476.733248] [] process_one_work+0x165/0x480
[2503476.734026] [] worker_thread+0x4b/0x4c0
[2503476.734801] [] ? process_one_work+0x480/0x480
[2503476.735691] [] kthread+0xe5/0x100
[2503476.736464] [] ? kthread_create_on_node+0x1e0/0x1e0
[2503476.737240] [] ret_from_fork+0x3f/0x70
[2503476.737991] [] ? kthread_create_on_node+0x1e0/0x1e0
[2503476.738724] Code: ff ff ff be 49 02 00 00 48 c7 c7 98 b9 cb 81 e8 e7 00 fe
ff e9 a6 fe ff ff 66 90 0f 1f 44 00 00 48 8b 87 18 05 00 00 55 48 89 e5 <48> 8b
40 d8 5d c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00
[2503476.739609] RIP [] kthread_data+0x10/0x20
[2503476.740384] RSP
[2503476.741149] CR2: ffd8
[2503476.741909] ---[ end trace 03d35738081084c7 ]---
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dragan S. (dragan-s)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dragan S. (dragan-s)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756197
Title:
Kernel panic BUG_ON in 4.4.0-92-generic fs/ext4/inode.c:1894!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756197/+subscriptions
--
ubun
[Bug 1720228] Re: User reports excessive ALUA retry messages
Khaled, any ides when this fix will be released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720228 Title: User reports excessive ALUA retry messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750038] [NEW] user space process hung in 'D' state waiting for disk io to complete
Public bug reported: Using Ubuntu Xenial user reports processes hang in D state waiting for disk io. Ocassionally one of the applications gets into "D" state on NFS reads/sync and close system calls. based on the kernel backtraces seems to be stuck in kmalloc allocation during cleanup of dirty NFS pages. All the subsequent operations on the NFS mounts are stuck and reboot is required to rectify the situation. [Test scenario] 1) Applications running in Docker environment 2) Application have cgroup limits --cpu-shares --memory -shm-limit 3) python and C++ based applications (torch and caffe) 4) Applications read big lmdb files and write results to NFS shares 5) use NFS v3 , hard and fscache is enabled 6) now swap space is configured This prevents all other I/O activity on that mount to hang. we are running into this issue more frequently and identified few applications causing this problem. As updated in the description, the problem seems to be happening when exercising the stack try_to_free_mem_cgroup_pages+0xba/0x1a0 we see this with docker containers with cgroup option --memory . whenever there is a deadlock, we see that the process that is hung has reached the maximum cgroup limit, multiple times and typically cleans up dirty data and caches to bring the usage under the limit. This reclaim path happens many times and finally we hit probably a race get into deadlock ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Dragan S. (dragan-s) Status: Incomplete ** Changed in: linux (Ubuntu) Milestone: None => xenial-updates ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750038 Title: user space process hung in 'D' state waiting for disk io to complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720228] Re: User reports excessive ALUA retry messages
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720228 Title: User reports excessive ALUA retry messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720228] Re: User reports excessive ALUA retry messages
** Description changed: SRU Justification: Impact: - User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-lts-4.4.0-91.114_14.04.1. Messages appear after a LUN disappears and there are hundreds of them flooding the log... + User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-lts-4.4.0-91.114_14.04.1 + Messages appear after a LUN disappears and there are hundreds of them flooding the log... [263095.795873] sd 3:0:0:129: alua: rtpg retry [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported This causes an intense requeing of the ALUA work queue for 60 seconds and it floods the kernel log + Fix: - The err value was initialized to 0 to prevent random assignment the fix is a cherry-pick from linus' tree a4bd85203190990ad808abbd4a5dc848a950002c + UBUNTU: scsi: fixe excessive ALUA (LP: #1720228) + + BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228 + + The err value was initialized to 0 to prevent random assignemtn + the fix is a cherry-pick from linus tree a4bd85203190990ad808abbd4a5dc848a950002c + Testcase: User reports issue when a network iscsi disk gets disconnected. - Original Bug Text: + Original Bug Text: - - User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-lts-4.4.0-91.114_14.04.1 + User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu- + lts-4.4.0-91.114_14.04.1 Messages appear after a LUN disappears and there are hundreds of them flooding the log... [263095.795873] sd 3:0:0:129: alua: rtpg retry [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.795961] sd 3:0:0:129: alua: rtpg retry [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796049] sd 3:0:0:129: alua: rtpg retry [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796140] sd 3:0:0:129: alua: rtpg retry [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796224] sd 3:0:0:129: alua: rtpg retry [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796473] sd 3:0:0:129: alua: rtpg retry [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796604] sd 3:0:0:129: alua: rtpg retry [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796691] sd 3:0:0:129: alua: rtpg retry [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796778] sd 3:0:0:129: alua: rtpg retry [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796868] sd 3:0:0:129: alua: rtpg retry [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796951] sd 3:0:0:129: alua: rtpg retry [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797034] sd 3:0:0:129: alua: rtpg retry [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797117] sd 3:0:0:129: alua: rtpg retry [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797202] sd 3:0:0:129: alua: rtpg retry [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797288] sd 3:0:0:129: alua: rtpg retry [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797387] sd 3:0:0:129: alua: rtpg retry [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797470] sd 3:0:0:129: alua: rtpg retry [263095.797471] sd 3:0:0:129:
[Bug 1720228] Re: User reports excessive ALUA retry messages
** Description changed: - User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu- - lts-4.4.0-91.114_14.04.1 + SRU Justification: + + Impact: + User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-lts-4.4.0-91.114_14.04.1. Messages appear after a LUN disappears and there are hundreds of them flooding the log... + + [263095.795873] sd 3:0:0:129: alua: rtpg retry + [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported + + This causes an intense requeing of the ALUA work queue for 60 seconds + and it floods the kernel log + + Fix: + The err value was initialized to 0 to prevent random assignment the fix is a cherry-pick from linus' tree a4bd85203190990ad808abbd4a5dc848a950002c + + Testcase: + User reports issue when a network iscsi disk gets disconnected. + + + Original Bug Text: + + + User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu-lts-4.4.0-91.114_14.04.1 Messages appear after a LUN disappears and there are hundreds of them flooding the log... - [263095.795873] sd 3:0:0:129: alua: rtpg retry - [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.795961] sd 3:0:0:129: alua: rtpg retry - [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796049] sd 3:0:0:129: alua: rtpg retry - [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796140] sd 3:0:0:129: alua: rtpg retry - [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796224] sd 3:0:0:129: alua: rtpg retry - [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796473] sd 3:0:0:129: alua: rtpg retry - [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796604] sd 3:0:0:129: alua: rtpg retry - [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796691] sd 3:0:0:129: alua: rtpg retry - [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796778] sd 3:0:0:129: alua: rtpg retry - [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796868] sd 3:0:0:129: alua: rtpg retry - [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796951] sd 3:0:0:129: alua: rtpg retry - [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797034] sd 3:0:0:129: alua: rtpg retry - [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797117] sd 3:0:0:129: alua: rtpg retry - [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797202] sd 3:0:0:129: alua: rtpg retry - [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] + [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal
[Bug 1720228] Re: User reports excessive ALUA retry messages
PPA fix for the issue is at: https://launchpad.net/~dragan-s/+archive/ubuntu/lp1720228 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720228 Title: User reports excessive ALUA retry messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720228] Re: User reports excessive ALUA retry messages
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720228 Title: User reports excessive ALUA retry messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720228] [NEW] User reports excessive ALUA retry messages
Public bug reported: User reports excessive ALUA messages on Ubuntu Trusty, kernel Ubuntu- lts-4.4.0-91.114_14.04.1 Messages appear after a LUN disappears and there are hundreds of them flooding the log... [263095.795873] sd 3:0:0:129: alua: rtpg retry [263095.795874] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795876] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.795961] sd 3:0:0:129: alua: rtpg retry [263095.795962] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.795964] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796049] sd 3:0:0:129: alua: rtpg retry [263095.796052] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796054] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796140] sd 3:0:0:129: alua: rtpg retry [263095.796142] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796143] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796224] sd 3:0:0:129: alua: rtpg retry [263095.796226] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796227] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796473] sd 3:0:0:129: alua: rtpg retry [263095.796475] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796476] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796604] sd 3:0:0:129: alua: rtpg retry [263095.796606] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796607] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796691] sd 3:0:0:129: alua: rtpg retry [263095.796693] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796694] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796778] sd 3:0:0:129: alua: rtpg retry [263095.796780] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796781] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796868] sd 3:0:0:129: alua: rtpg retry [263095.796869] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796871] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.796951] sd 3:0:0:129: alua: rtpg retry [263095.796953] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.796954] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797034] sd 3:0:0:129: alua: rtpg retry [263095.797035] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797037] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797117] sd 3:0:0:129: alua: rtpg retry [263095.797119] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797120] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797202] sd 3:0:0:129: alua: rtpg retry [263095.797203] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797205] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797288] sd 3:0:0:129: alua: rtpg retry [263095.797289] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797290] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797387] sd 3:0:0:129: alua: rtpg retry [263095.797388] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797390] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797470] sd 3:0:0:129: alua: rtpg retry [263095.797471] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797472] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797562] sd 3:0:0:129: alua: rtpg retry [263095.797563] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797564] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported [263095.797652] sd 3:0:0:129: alua: rtpg retry [263095.797653] sd 3:0:0:129: [alua] Sense Key : Illegal Request [current] [263095.797654] sd 3:0:0:129: [alua] Add. Sense: Logical unit not supported ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Dragan S. (dragan-s) Status: Incomplete ** Tags: kernel-bug sts trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720228 Title: User reports excessive ALUA retry messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file handling has races
** Changed in: ebtables (Debian) Status: Fix Released => Unknown ** Changed in: ebtables (Debian) Remote watch: Debian Bug tracker #813760 => Debian Bug tracker #860590 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file handling has races To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file handling has races
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860590 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file handling has races To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file handling has races
** Changed in: ebtables (Ubuntu Zesty) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file handling has races To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file handling has races
@Robie- Hi Robie- if by Z+1 you mean Zesty, I have attached the patch for zesty and Dan nominated it for zesty but we are waiting for someone with permissions to confirm it. I also filed a bug with upstream Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860590 The DEP-3 header is in the diff: +Description: Use real locking in ebtables + Prior use of locking by file exclusive access is inadequate + because if ebtables crashes or is killed it will leave a + stale lock file behind which then blocks new ebtables from + running. +Author: dragan.stance...@canonical.com +Bug: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +Index: ebtables-2.0.10.4/libebtc.c Is that what you are looking for? Thanks ** Bug watch added: Debian Bug tracker #860590 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860590 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file handling has races To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run
** Patch added: "Zesty Patch" https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+attachment/4864509/+files/zesty-fix-real-locking.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587475] Re: Kernel panic on btrfs mount and ls
I can reproduce this problem and I have pinpointed the problem. Working on creating a patch and a test build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587475 Title: Kernel panic on btrfs mount and ls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587475] Re: Kernel panic on btrfs mount and ls
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587475 Title: Kernel panic on btrfs mount and ls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run
r/lib/ebtables directory with timestamp 14:54 - - ebtables was configured: - * Ebtables support available, number of installed rules [ OK ] - (other nodes appeared to be in the same state from ebtables point of view, but without the lock file) - - I removed the lock file and libvirt started to work instantly - the lock obtain messages have disappeared from the trace and virsh commands are working - - at 14:54 the host was booting up. According to the logs, there were other reboots after that one, but the lock file remained intact (at least the timestamp was not updated). + - there was a file named 'lock' in /var/lib/ebtables directory with timestamp 14:54 + - ebtables was configured: + * Ebtables support available, number of installed rules [ OK ] + (other nodes appeared to be in the same state from ebtables point of view, but without the lock file) + - I removed the lock file and libvirt started to work instantly - the lock obtain messages have disappeared from the trace and virsh commands are working + - at 14:54 the host was booting up. According to the logs, there were other reboots after that one, but the lock file remained intact (at least the timestamp was not updated). Could you please suggest a solution to be sure that ebtables lock file is removed during boot? ** Changed in: ebtables (Ubuntu Trusty) Assignee: (unassigned) => Dragan S. (dragan-s) ** Changed in: ebtables (Ubuntu Trusty) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run
Use real locking in ebtables (LP: #1645324) - Prior use of locking by file exclusive access is inadequate because if ebtables crashes or is killed it will leave a stale lock file behind which then blocks new ebtables from running. ** Patch added: "fix_ds-lp1645324.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+attachment/4832573/+files/fix_ds-lp1645324.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run
> Sure, but if it fixes (and is expected to fix completely) the actual impact > to users then it may > be the most appropriate for an SRU. We don't fix > theoretical bugs in SRUs. As far as I understand the impact to the user was that a lock file from a previous run prevents ebtables to run again. And then second part was that user tried to reboot and that didn't help either. So a reboot is not the fix part, the fix part is in ebtables to not leave stale locks around... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run
Creating a "fix" that only removes the file on boot is not a fix I have taken over this issue from Amad and have looked into the code. The file exclusive create approach is a bad substitution for real locking. I have a patch done that I am in the process of building a PPA to test, this uses real locking. File existence as a lock is bad because if the process dies or is killed it leaves a stale file around blocking any new ebtables instance from running. The approach taken in Zesty is not a real solution either since it just shifts the problem around. If the process is killed or crashes by an un-trappable signal the file will persist until the system is rebooted. Hardly a solution My patch creates a real lock on the file that is automatically released on exit or a crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635049] Re: Boot fails with degraded mdadm raid
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635049 Title: Boot fails with degraded mdadm raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1635049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635049] Re: Boot fails with degraded mdadm raid
PPA located at: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2500 Fixes my degraded raid boot issues. System boots up fine after this PPA is applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635049 Title: Boot fails with degraded mdadm raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1635049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645324] Re: ebtables: Lock file should be moved from /var/lib/ebtables to /run
Good points racb, I think the startup script should test on "start" the existence of the process and the lock. If process is not running it should remove the lock before starting a new process. Also file should be removed on "stop". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645324 Title: ebtables: Lock file should be moved from /var/lib/ebtables to /run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ebtables/+bug/1645324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657281] Re: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue
Verified: 4.4.0-59-generic $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 100+0 records in 100+0 records out 819200 bytes (8.2 GB, 7.6 GiB) copied, 56.7741 s, 144 MB/s 4.4.0-62-generic $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 100+0 records in 100+0 records out 819200 bytes (8.2 GB, 7.6 GiB) copied, 31.3783 s, 261 MB/s ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657281 Title: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657281] [NEW] Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue
Public bug reported:
[Impact]
* When running block device I/O on an Amazon i3 system there
is a performance degradation. A patch with git change id
87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
series increases I/O performance.
* Fix should be backported to xenial 4.4 series to avoid more
support issues being filed.
* This change gets rid of uneccessary work being performed.
[Test Case]
* Steps to reproduce below
1) partition ephemeral disks
/sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary
0% 100%
/sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary
0% 100%
/sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary
0% 100%
/sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary
0% 100%
2) create raid array
/sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1
3) create pv
/sbin/pvcreate --force --metadatasize 4092k /dev/md0
4) create volume group
/sbin/vgcreate RDSVG /dev/md0
5) create lv
/sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG
5) test I/O
sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
[Regression Potential]
* No known regression potential.
[Original Description]
When we were doing testing on i3, we noticed that it is taking
significantly longer to perform operations when using software RAID than
without, we believe this is resolved in an upstream commit:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da
So stock 4.4.0-59-generic performs ok:
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
sudo: unable to resolve host ip-10-0-85-167
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s
and the patch you originally providing works a little bit better (as expected):
$ uname -a
Linux ip-10-0-85-167 4.4.0-57-generic
#78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64
x86_64 GNU/Linux
ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k
count=100 && sync
sudo: unable to resolve host ip-10-0-85-167
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dragan S. (dragan-s)
Status: Incomplete
** Tags: sts
** Patch added: "block: fix plug list flushing for nomerge queues"
https://bugs.launchpad.net/bugs/1657281/+attachment/4805506/+files/fix_plug_list_flushing_for_nomerge_queues.patch
** Tags added: sts
** Description changed:
+
+ [Impact]
+
+ * When running block device I/O on an Amazon i3 system there
+is a performance degradation. A patch with git change id
+87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
+series increases I/O performance.
+
+ * Fix should be backported to xenial 4.4 series to avoid more
+support issues being filed.
+
+ * This change gets rid of uneccessary work being performed.
+
+ [Test Case]
+
+ * Steps to reproduce below
+1) partition ephemeral disks
+ /sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary
0% 100%
+ /sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary
0% 100%
+ /sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary
0% 100%
+ /sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary
0% 100%
+
+2) create raid array
+ /sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1
+
+3) create pv
+ /sbin/pvcreate --force --metadatasize 4092k /dev/md0
+
+4) create volume group
+ /sbin/vgcreate RDSVG /dev/md0
+
+5) create lv
+ /sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG
+
+5) test I/O
+ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
+
+ [Regression Potential]
+
+ * No known regression potential.
+
+ [Original Description]
+
When we were doing testing on i3, we noticed that it is taking
significantly longer to perform operations when using software RAID than
without, we believe this is resolved in an upstream commit:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da
So stock 4.4.0-59-generic performs ok:
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
sudo: unable to resolve host ip-10-0-85-167
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s
and the patch you originally providing works a little
[Bug 1651609] Re: Missing hugepages in xenial on 4.4.0-36-generic
** Package changed: ethtool (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651609 Title: Missing hugepages in xenial on 4.4.0-36-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651609] [NEW] Missing hugepages in xenial on 4.4.0-36-generic
Public bug reported: When spawning multiple VMs and then shutting then down there are hugepages that are unaccounted for, they don't show up in "ipcs -m" or on in /dev/hugepages/ ** Affects: ethtool (Ubuntu) Importance: Undecided Assignee: Dragan S. (dragan-s) Status: New ** Tags: sts ** Changed in: ethtool (Ubuntu) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651609 Title: Missing hugepages in xenial on 4.4.0-36-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/1651609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
** Changed in: linux (Ubuntu) Assignee: Dragan S. (dragan-s) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625381 Title: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] Re: Core dump on multipathd shutdown - trusty 14.04.4
User also verified issue as fixed with 0.4.9-3ubuntu7.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616213 Title: Core dump on multipathd shutdown - trusty 14.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] Re: Core dump on multipathd shutdown - trusty 14.04.4
I pulled multipath-tools 0.4.9-3ubuntu7.15 and verified that the fix is there. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616213 Title: Core dump on multipathd shutdown - trusty 14.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
test, ignore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] Re: Core dump on multipathd shutdown - trusty 14.04.4
PPA with the fix is available at:
https://launchpad.net/~dragan-s/+archive/ubuntu/lp1616213
** Description changed:
+ [Impact]
+
+ * During "service multipath-tools stop" multipath daemon
+is trying to cleanup and shut down several concurrent
+threads. At times depending on a race condition between
+two threads, one thread might free resources that are still
+used by another thread.
+
+This is causing the multipathd to dump crash core on
+stop events.
+
+ * Fix should be backported to trusty to avoid more support
+issues being filed.
+
+ * This change delays freeing resources that another thread is
+still using.
+
+ [Test Case]
+
+ * install multipath-tools, create a basic multipath.conf with
+devices under management. Run: "service multipath-tools start"
+run I/O on devices and keep the system CPU busy, then run
+"service multipath-tools stop".
+
+ [Regression Potential]
+
+ * There should be no regression potential with this change,
+this problem happens on the exit path and we are only delaying
+a free call.
+
+ [Original Description]
+
On ubuntu trusty 14.04.4 in multipath-tools version 0.4.9-3ubuntu7.14
there is bug in multipathd on shutdown.
The code will access pathvec pointer which is a valid address:
Reading symbols from /sbin/multipathd...Reading symbols from
/usr/lib/debug//sbin/multipathd...done.
done.
[New LWP 41631]
[New LWP 41584]
[New LWP 41633]
[New LWP 41632]
[New LWP 41582]
[New LWP 41583]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/sbin/multipathd'.
Program terminated with signal SIGSEGV, Segmentation fault.
- #0 0x004075db in checkerloop (ap=0x1b81040) at main.c:1150
+ #0 0x004075db in checkerloop (ap=0x1b81040) at main.c:1150
- 1150 vector_foreach_slot (vecs->pathvec, pp, i) {
+ 1150 vector_foreach_slot (vecs->pathvec, pp, i) {
(gdb) list
- 1145 pthread_cleanup_push(cleanup_lock, >lock);
- 1146 lock(vecs->lock);
- 1147 condlog(4, "tick");
- 1148
- 1149 if (vecs->pathvec) {
- 1150 vector_foreach_slot (vecs->pathvec, pp, i) {
- 1151 check_path(vecs, pp);
- 1152 }
- 1153 }
- 1154 if (vecs->mpvec) {
+ 1145 pthread_cleanup_push(cleanup_lock, >lock);
+ 1146 lock(vecs->lock);
+ 1147 condlog(4, "tick");
+ 1148
+ 1149 if (vecs->pathvec) {
+ 1150 vector_foreach_slot (vecs->pathvec, pp, i) {
+ 1151 check_path(vecs, pp);
+ 1152 }
+ 1153 }
+ 1154 if (vecs->mpvec) {
Pathvec is a valid pointer:
(gdb) p vecs->pathvec
$1 = (vector) 0x1b81280
But the contents of the structure are just garbage:
(gdb) p *vecs->pathvec
$2 = {allocated = 1651076143, slot = 0x756e696c2d34365f}
(gdb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616213
Title:
Core dump on multipathd shutdown - trusty 14.04.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] Re: Core dump on multipathd shutdown - trusty 14.04.4
** Patch added: "Fix debdiff" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+attachment/4752077/+files/fix-lp1616213.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616213 Title: Core dump on multipathd shutdown - trusty 14.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625381 Title: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625381] Re: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
Here is the crash log: Aug 31 15:35:34 6SZXP72 kernel: [4.320565] general protection fault: [#1] SMP Aug 31 15:35:34 6SZXP72 kernel: [4.320605] Modules linked in: joydev wacom arc4 ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG snd_hda_codec_hdmi iwlmvm i2c_designware_platform xt_limit snd_hda_codec_realtek i2c_designware_core snd_hda_codec_generic xt_tcpudp mac80211 xt_addrtype snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_ipc dell_wmi sparse_keymap snd_soc_sst_dsp nf_conntrack_ipv4 snd_soc_core nf_defrag_ipv4 xt_conntrack snd_compress ip6table_filter ip6_tables ac97_bus nf_conntrack_netbios_ns nf_conntrack_broadcast snd_pcm_dmaengine nf_nat_ftp nf_nat dw_dmac_core nf_conntrack_ftp snd_hda_intel nf_conntrack iwlwifi intel_rapl iptable_filter x86_pkg_temp_thermal ip_tables x_tables intel_powerclamp coretemp snd_hda_codec cfg80211 kvm_intel dell_laptop dcdbas snd_hda_core snd_hwdep dell_smm_hwmon rtsx_pci_ms memstick cdc_mbim cdc_wdm kvm cdc_ncm usbnet snd_pcm mii irqbypas s crct10dif_pclmul crc32_pclmul rfcomm idma64 aesni_intel virt_dma aes_x86_64 lrw gf128mul bnep glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer input_leds snd serio_raw soundcore mei_me btusb btrtl mei shpchp intel_lpss_pci wmi i2c_hid hid i915_bpo hci_uart btbcm btqca int3403_thermal soc_button_array btintel bluetooth intel_ips video pinctrl_sunrisepoint pinctrl_intel int3402_thermal drm_kms_helper nls_iso8859_1 drm tpm_crb int3400_thermal acpi_thermal_rel intel_lpss_acpi intel_lpss processor_thermal_device int340x_thermal_zone intel_soc_dts_iosf i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt acpi_pad mac_hid parport_pc ppdev acpi_als kfifo_buf industrialio lp parport rtsx_pci_sdmmc ahci rtsx_pci libahci fjes Aug 31 15:35:34 6SZXP72 kernel: [4.321778] CPU: 2 PID: 900 Comm: sh Not tainted 4.4.0-21-generic #37~14.04.1-Ubuntu Aug 31 15:35:34 6SZXP72 kernel: [4.321821] Hardware name: Dell Inc. Latitude 5175/0W1PYK, BIOS 01.00.07 02/24/2016 Aug 31 15:35:34 6SZXP72 kernel: [4.321865] task: 88016c61d880 ti: 880084b0c000 task.ti: 880084b0c000 Aug 31 15:35:34 6SZXP72 kernel: [4.321908] RIP: 0010:[] [] kmem_cache_alloc+0x79/0x200 Aug 31 15:35:34 6SZXP72 kernel: [4.321963] RSP: 0018:880084b0fd90 EFLAGS: 00010282 Aug 31 15:35:34 6SZXP72 kernel: [4.321995] RAX: RBX: 024000c0 RCX: 473a Aug 31 15:35:34 6SZXP72 kernel: [4.322035] RDX: 4739 RSI: 024000c0 RDI: 88016d401b00 Aug 31 15:35:34 6SZXP72 kernel: [4.322075] RBP: 880084b0fdc0 R08: 00019f80 R09: 811bd98d Aug 31 15:35:34 6SZXP72 kernel: [4.322115] R10: 0007efee6131 R11: 88016ad39040 R12: 024000c0 Aug 31 15:35:34 6SZXP72 kernel: [4.322156] R13: 00020501 R14: 88016d401b00 R15: 88016d401b00 Aug 31 15:35:34 6SZXP72 kernel: [4.322197] FS: 7efee6113740() GS:88017210() knlGS: Aug 31 15:35:34 6SZXP72 kernel: [4.322242] CS: 0010 DS: ES: CR0: 80050033 Aug 31 15:35:34 6SZXP72 kernel: [4.322275] CR2: 7efee5c87e00 CR3: 84d49000 CR4: 003406e0 Aug 31 15:35:34 6SZXP72 kernel: [4.322316] DR0: DR1: DR2: Aug 31 15:35:34 6SZXP72 kernel: [4.322356] DR3: DR6: fffe0ff0 DR7: 0400 Aug 31 15:35:34 6SZXP72 kernel: [4.322396] Stack: Aug 31 15:35:34 6SZXP72 kernel: [4.322410] 811bd98d 88007fbcf190 88016c3debb8 88016a3529b0 Aug 31 15:35:34 6SZXP72 kernel: [4.322462] 0001 8800864fa268 880084b0fdf0 811bd98d Aug 31 15:35:34 6SZXP72 kernel: [4.322514] 88007f9bda40 88016c3debb8 88007fbcf190 0001 Aug 31 15:35:34 6SZXP72 kernel: [4.322565] Call Trace: Aug 31 15:35:34 6SZXP72 kernel: [4.322586] [] ? anon_vma_fork+0x8d/0x130 Aug 31 15:35:34 6SZXP72 kernel: [4.322621] [] anon_vma_fork+0x8d/0x130 Aug 31 15:35:34 6SZXP72 kernel: [4.322655] [] copy_process+0xe36/0x1c60 Aug 31 15:35:34 6SZXP72 kernel: [4.322689] [] _do_fork+0x82/0x310 Aug 31 15:35:34 6SZXP72 kernel: [4.322720] [] SyS_clone+0x19/0x20 Aug 31 15:35:34 6SZXP72 kernel: [4.322752] [] entry_SYSCALL_64_fastpath+0x16/0x75 Aug 31 15:35:34 6SZXP72 kernel: [4.322789] Code: 4c 03 05 13 e9 e2 7e 4d 8b 28 49 8b 40 10 4d 85 ed 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 49 63 46 20 48 8d 4a 01 4d 8b 06 <49> 8b 5c 05 00 4c 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 74 b8 49 Aug 31 15:35:34 6SZXP72 kernel: [4.323049] RIP [] kmem_cache_alloc+0x79/0x200 Aug 31 15:35:34 6SZXP72 kernel: [4.323090] RSP Aug 31 15:35:34 6SZXP72 kernel: [4.323130] ---[ end trace
[Bug 1625381] [NEW] Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu
Public bug reported: On Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu there is a crash that randomly happens. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625381 Title: Crash on Ubuntu 14.04.5 LTS linux kernel 4.4.0-21-generic #37~14.04.1-Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] Re: Core dump on multipathd shutdown - trusty 14.04.4
Thread 5 is on the way out:
(gdb) thread 5
[Switching to thread 5 (Thread 0x7f21ca11f840 (LWP 41582))]
#0 0x7f21c9111dfd in nanosleep () at ../sysdeps/unix/syscall-template.S:81
81 ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) up
#1 0x7f21c9111c94 in __sleep (seconds=0) at
../sysdeps/unix/sysv/linux/sleep.c:137
137 ../sysdeps/unix/sysv/linux/sleep.c: No such file or directory.
(gdb)
#2 0x004084e6 in child (param=0x0) at main.c:1539
1539sleep (1); /* This is weak. */
(gdb) list
1534free_polls();
1535
1536unlock(vecs->lock);
1537/* Now all the waitevent threads will start rushing in. */
1538while (vecs->lock.depth > 0) {
1539sleep (1); /* This is weak. */
1540condlog(3,"Have %d wait event checkers threads to
de-alloc, waiting..\n", vecs->lock.depth);
1541}
1542pthread_mutex_destroy(vecs->lock.mutex);
1543FREE(vecs->lock.mutex);
The code in thread 5 before the sleep(1) is:
(gdb) list -
1524
1525pthread_cancel(check_thr);
1526pthread_cancel(uevent_thr);
1527pthread_cancel(uxlsnr_thr);
1528pthread_cancel(uevq_thr);
1529
1530free_keys(keys);
1531keys = NULL;
1532free_handlers(handlers);
1533handlers = NULL;
(gdb) list -
1514/*
1515 * exit path
1516 */
1517block_signal(SIGHUP, NULL);
1518lock(vecs->lock);
1519if (conf->queue_without_daemon == QUE_NO_DAEMON_OFF)
1520vector_foreach_slot(vecs->mpvec, mpp, i)
1521dm_queue_if_no_path(mpp->alias, 0);
1522remove_maps_and_stop_waiters(vecs);
1523free_pathvec(vecs->pathvec, FREE_PATHS);
(gdb)
So as you can see at line 1523, thread 5 freed vecs->pathvec. Which thread 1 is
accessing:
1150vector_foreach_slot (vecs->pathvec, pp, i) {
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616213
Title:
Core dump on multipathd shutdown - trusty 14.04.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] Re: Core dump on multipathd shutdown - trusty 14.04.4
Other threads on the way out: (gdb) info threads Id Target Id Frame 6Thread 0x7f21ca11e700 (LWP 41583) pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 5Thread 0x7f21ca11f840 (LWP 41582) 0x7f21c9111dfd in nanosleep () at ../sysdeps/unix/syscall-template.S:81 4Thread 0x7f21ca0b3700 (LWP 41632) (Exiting) 0x7f21c9145967 in madvise () at ../sysdeps/unix/syscall-template.S:81 3Thread 0x7f21ca0a2700 (LWP 41633) (Exiting) 0x7f21c732a1d1 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1 2Thread 0x7f21ca10d700 (LWP 41584) (Exiting) __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 * 1Thread 0x7f21ca0c4700 (LWP 41631) 0x004075db in checkerloop (ap=0x1b81040) at main.c:1150 (gdb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616213 Title: Core dump on multipathd shutdown - trusty 14.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616213] [NEW] Core dump on multipathd shutdown - trusty 14.04.4
Public bug reported:
On ubuntu trusty 14.04.4 in multipath-tools version 0.4.9-3ubuntu7.14
there is bug in multipathd on shutdown.
The code will access pathvec pointer which is a valid address:
Reading symbols from /sbin/multipathd...Reading symbols from
/usr/lib/debug//sbin/multipathd...done.
done.
[New LWP 41631]
[New LWP 41584]
[New LWP 41633]
[New LWP 41632]
[New LWP 41582]
[New LWP 41583]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/sbin/multipathd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x004075db in checkerloop (ap=0x1b81040) at main.c:1150
1150vector_foreach_slot (vecs->pathvec, pp, i) {
(gdb) list
1145pthread_cleanup_push(cleanup_lock, >lock);
1146lock(vecs->lock);
1147condlog(4, "tick");
1148
1149if (vecs->pathvec) {
1150vector_foreach_slot (vecs->pathvec, pp, i) {
1151check_path(vecs, pp);
1152}
1153}
1154if (vecs->mpvec) {
Pathvec is a valid pointer:
(gdb) p vecs->pathvec
$1 = (vector) 0x1b81280
But the contents of the structure are just garbage:
(gdb) p *vecs->pathvec
$2 = {allocated = 1651076143, slot = 0x756e696c2d34365f}
(gdb)
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Assignee: Dragan S. (dragan-s)
Status: In Progress
** Tags: sts trusty
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Dragan S. (dragan-s)
** Changed in: multipath-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616213
Title:
Core dump on multipathd shutdown - trusty 14.04.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1616213/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Package version tested: ubuntu-SRV-16-04-lp1570093:~$ apt-cache policy multipath-tools multipath-tools: Installed: 0.5.0+git1.656f8865-5ubuntu2.2 Candidate: 0.5.0+git1.656f8865-5ubuntu2.2 Version table: *** 0.5.0+git1.656f8865-5ubuntu2.2 400 400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.5.0+git1.656f8865-5ubuntu2.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 0.5.0+git1.656f8865-5ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Hi Brian- I can confirm that after: apt-get install multipath-tools/xenial-proposed the messages below went away: Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 systemd[1]: Started Device-Mapper Multipath Device Controller. Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-3: failed to get udev uid: Invalid argument Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-3: failed to get sysfs uid: Invalid argument Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-3: failed to get sgio uid: No such file or directory Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-4: failed to get udev uid: Invalid argument Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-4: failed to get sysfs uid: Invalid argument Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-4: failed to get sgio uid: No such file or directory Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-5: failed to get udev uid: Invalid argument Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-5: failed to get sysfs uid: Invalid argument Aug 16 15:05:08 ubuntu-SRV-16-04-lp1570093 multipath: dm-5: failed to get sgio uid: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611133] Re: dpkg truncates lines in 'status' file which begin with two spaces.
** Attachment added: "Good status file" https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+attachment/4721386/+files/status-good -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611133 Title: dpkg truncates lines in 'status' file which begin with two spaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611133] Re: dpkg truncates lines in 'status' file which begin with two spaces.
** Attachment added: "Bad status file" https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+attachment/4721387/+files/status-bad ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611133 Title: dpkg truncates lines in 'status' file which begin with two spaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611133] Re: dpkg truncates lines in 'status' file which begin with two spaces.
Hi Dimitri- yes my mistake, I meant Description field. I will upload the good and the bad files momentarily... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611133 Title: dpkg truncates lines in 'status' file which begin with two spaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611133] Re: dpkg truncates lines in 'status' file which begin with two spaces.
** Tags added: dpkg precise ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611133 Title: dpkg truncates lines in 'status' file which begin with two spaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611133] [NEW] dpkg truncates lines in 'status' file which begin with two spaces.
Public bug reported: On Ubuntu 12.04.5 LTS command dpkg version 1.16.1.2ubuntu7.7 seems to experience issues when updating packages. In one instance the status file seems to have over a thousand lines that have been truncated. It only seems to truncate package comments that are indented with two spaces. No indent or single space indent lines are all fine but lines that have a double space get truncated. They are not gone in the file they are just replaced by a line that has two spaces and a new line. Programmatically I would describe the problem as in perhaps a failure in reading the comment from the source and writing an empty string into the target: Comment = read_comment(next_line); fprintf(Status, " %s\n", Comment); So if there was an error in read_comment and function returned an empty string "", this would explain why some lines were getting truncated. ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611133 Title: dpkg truncates lines in 'status' file which begin with two spaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1611133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477466] Re: Low performance when using vlan over VxLan
Closing as incomplete since we are missing required information ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Vivid) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477466 Title: Low performance when using vlan over VxLan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump
Steve- Louis is out and in his absence I am still looking into this that's why I assigned it to myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535898 Title: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump
** Changed in: multipath-tools (Ubuntu Precise) Assignee: Louis Bouchard (louis-bouchard) => Dragan S. (dragan-s) ** Changed in: multipath-tools (Ubuntu Trusty) Assignee: Louis Bouchard (louis-bouchard) => Dragan S. (dragan-s) ** Changed in: multipath-tools (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535898 Title: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477466] Re: Low performance when using vlan over VxLan
Hi Talat- any update on this issue? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477466 Title: Low performance when using vlan over VxLan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
** Description changed: + [Impact] + + * During "service multipath-tools start" /sbin/multipath is +called on dm- devices that are filtered but due to a condition +conf->dev_type == DEV_DEVNODE in filtering code multipath +binary wasn't dropping out when hitting a dm- device. This +was due to the fact that in this case conf->dev_type is +set to DEV_UEVENT. It also happens during a fail-over event. + +This is causing the logs to be filled with following +messages: + +multipath: dm-6: failed to get udev uid: Invalid argument +multipath: dm-6: failed to get sysfs uid: Invalid argument +multipath: dm-6: failed to get sgio uid: No such file or directory + + * Fix should be backported to xenial to avoid more support +issues being filed. + + * This change alows the filtering to happen. + + [Test Case] + + * install multipath-tools, create a basic multipath.conf with +dm- filtering rule. Run: "service multipath-tools start" +and check the log + + [Regression Potential] + + * There should be no regression potential with this change, the filtering +only allows the code to not traverse the error path. + + + [Original Description] + During a path loss event, the syslog is showing these messages where prior to the recent upgrade to multipath-tools I didn't see anything - like this. To me this seems like either a problem or it seems like a + like this. To me this seems like either a problem or it seems like a print message that should go into a different log file. Apr 13 11:21:00 ICTM1618S01H4 systemd-udevd[14861]: Process '/usr/bin/partx -d --nr 1-1024 /dev/sdam' failed with exit code 1. ... Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get udev uid: Invalid argument Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sysfs uid: Invalid argument Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sgio uid: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: multipath-tools 0.5.0+git1.656f8865-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 15:29:36 2016 SourcePackage: multipath-tools UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477466] Re: Low performance when using vlan over VxLan
Hi Talat- The bug was filed against vivid which is no longer maintained. The original submitter had requested certain patches be back-ported to vivid because they supposedly fixed an issue. The requested patches were back-ported and they didn't fix the issue the submitter purported that they fix. So I wanted to know two things: 1. Does the reported issue still appear in latest releases such as xenial(16.04) 2. If so does this issue appear in the mainline kernel as well? This will determine if the reported issue is an Ubuntu specific issue or if the general mainline linux kernel needs fixing. If you can re-run the tests on 1 & 2 that would be very helpful, but it would also help if you could provide the exact configuration and steps you use so that I can try and reproduce your tests. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477466 Title: Low performance when using vlan over VxLan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477466] Re: Low performance when using vlan over VxLan
Hi Kamal- what is the status of this issue. Have you had a chance to try the kernel with back-ported changes? Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477466 Title: Low performance when using vlan over VxLan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Great, thank you Matt. Independent verification of the fix will now allow it to move upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Fix has been submitted upstream into Debian: Tue, 12 Jul 2016 11:30:15 -0500 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830882 ** Bug watch added: Debian Bug tracker #830882 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830882 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Hi Mike, I already built the PPA for this change. You can get it by running following commands: add-apt-repository ppa:dragan-s/lp1570093 apt update apt install multipath-tools With this fix the errors like the ones below should be gone: Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get udev uid: Invalid argument Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sysfs uid: Invalid argument Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sgio uid: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Err... -ENONAME sorry meant to type Matt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Here is the debdiff for the fix. Working on up-streaming this fix to debian. ** Patch added: "Fix debdiff" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+attachment/4698896/+files/fix-0001-multipath-tools-fix-dm-device-filtering.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Patch has been submitted upstream on: 1. Thu, 23 Jun 2016 16:06:24 -0500 [dm-devel] Subject: [PATCH 1/1] multipath-tools: fix dm- device filtering https://www.redhat.com/archives/dm-devel/2016-June/msg00359.html 2. Tue, 5 Jul 2016 15:46:57 -0500 [dm-devel] [PATCH 1/1] multipath-tools: fix dm- device filtering https://www.redhat.com/archives/dm-devel/2016-July/msg00086.html I has been accepted upstream on: Fri, 8 Jul 2016 09:42:43 +0200 https://www.redhat.com/archives/dm-devel/2016-July/msg00159.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592999] Re: memory leak in libmultipath
After analysis this turns out not to be a bug, the code at the top of get_uid calls select_getuid which calls pp_set_ovr(uid_attribute). That macro points uid_attribute into the global config variable that lives beyond this function call. So no need for get_uid to free it. ** Changed in: multipath-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592999 Title: memory leak in libmultipath To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1592999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Hi Matt- just wanted to give you a quick update on the issue. We've isolated the problem and are now working with upstream developer to push the patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Thanks for the info Matt. I am looking into the case. If you replace: uid_attribute "ID_SERIAL" with: getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n" in your multipath.conf and restart your multipathd those messages should go away. The line should be in your "defaults" section of the config. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477466] Re: Low performance when using vlan over VxLan
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dragan S. (dragan-s) ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477466 Title: Low performance when using vlan over VxLan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533721] Re: Ethtool didn't support link speed 25Gb 56Gb 100Gb 200Gb
** Changed in: ethtool (Ubuntu) Assignee: (unassigned) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533721 Title: Ethtool didn't support link speed 25Gb 56Gb 100Gb 200Gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/1533721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592999] [NEW] memory leak in libmultipath
Public bug reported:
Description:Ubuntu 16.04 LTS
Release:16.04
get_uid in libmultipath appears to be leaking memory on the error path.
1553 if (len <= 0 &&
1554 !strcmp(pp->uid_attribute, DEFAULT_UID_ATTRIBUTE)) {
1555 len = get_vpd_uid(pp);
1556 origin = "sysfs";
1557 pp->uid_attribute = NULL;
1558 if (len < 0) {
1559 condlog(1, "%s: failed to get sysfs uid:
%s %d",
1560 pp->dev, strerror(-len), line);
1561 len = get_vpd_sgio(pp->fd, 0x83, pp->wwid,
1562WWID_SIZE);
1563 origin = "sgio";
1564 }
1565 }
Line 1557 resets the uid_attribute to NULL after it was successfully
compared at line 1554 but it doesn't free the pointer fist.
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Assignee: Dragan S. (dragan-s)
Status: New
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Dragan S. (dragan-s)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592999
Title:
memory leak in libmultipath
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1592999/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
Hi Matt- do you mind posting your "/etc/multipath.conf" from the host you provided the last syslog. And also if you can provide the output of "sudo multipath -ll" from the same host. Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570093] Re: multipath-tools update introduced syslog messages about partx
** Changed in: multipath-tools (Ubuntu) Assignee: Rafael David Tinoco (inaddy) => Dragan S. (dragan-s) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570093 Title: multipath-tools update introduced syslog messages about partx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
