** Changed in: multipath-tools (Ubuntu)
Assignee: Peter Petrakis (peter-petrakis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipa
I can confirm this issue at
root@myhost:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
root@myhost:~# dpkg -s multipath-tools
Package: multipath-tools
Status: install ok installed
Priority: ext
I can confirm this issue at
root@cpt151:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
root@cpt151:~# dpkg -s multipath-tools
Package: multipath-tools
Status: install ok installed
Priority: ex
Syslog of the last testrun on kernel 3.5.0. Test started @ 10:15
** Attachment added: "syslog.server1"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3473174/+files/syslog.server1
--
You received this bug notification because you are a member of Ubuntu
Se
Syslog for server2, the same testrun also on kernel 3.5.0
** Attachment added: "syslog.server2"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3473175/+files/syslog.server2
--
You received this bug notification because you are a member of Ubuntu
Server Tea
Peter,
First: happy new year!
I've been doing some more tests to track down the cause of this bug.
Since it looks like a kernel bug, I tried reproducing this with kernel
3.5.0, version 3.5.0-21.32~precise1. I could reproduce the faulty paths
that multipathd was unable to remove, however: there we
The normal state of the disks is as follows:
LUN-DATABASE (36006016061e02e003cf1aca4ae07e211) dm-2 DGC,VRAID
size=200G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=130 status=active
| |- 4:0:0:1 sdg 8:96 active ready running
| `- 3:0:0:1 sdc 8:32 active
vmcore file of crashed kernel.
** Attachment added: "vmcore-crash.tgz"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3465398/+files/vmcore-crash.tgz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
@Ronald
First, please attach http://www.rmoesbergen.nl/vmcore-crash.tgz to the bug,
launchpad
can handle it just fine. Also, this is going to take awhile. We're off all next
week so don't
expect any movement on this until early-mid Jan. Feel free to ping me if I
forget.
Also, at what time did
I've uploaded the vmcore file separately, because I have some doubts
about the dumpfile created by apport beging complete. Please find it
here: http://www.rmoesbergen.nl/vmcore-crash.tgz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to m
Peter,
I got it to crash again, this time with a nice kernel dump. The dump can
be fetched here:
http://www.rmoesbergen.nl/linux-image-3.2.0-34-generic.0.crash.gz
The crash itself looked like this:
Dec 21 11:07:32 ealxs00161 kernel: [63272.392812] sd 4:0:1:1: emc: ALUA
failover mode detected
D
^5!
Make sure you enable ftrace per:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/comments/16
That'll save me a lot of work, should crash with a nice long call graph and the
CPUs
caught executing the code.
Well done!
--
You received this bug notification because you
Removing the 'reset_devices' and 'irq_poll' in /etc/init.d/kdump did the
trick, both machines now generate a nice vmcore file when they crash.
I'll re-test with all your settings applied and report back. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Correction:
is crashkernel even configured?
* grep crash /proc/cmdline
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] failed to get sysfs inform
Hi Ronald,
Sorry I haven't been timely, this is the best I can do with community level
support
If kdump isn't launching even in the most trivial case then you have to start
from zero.
is crashkernel even configured?
* grep crash /proc/crashkernel
How much memory do you have, could you assi
Peter, is there another way to get you a kernel crash-dump? Whatever I
try, the crashdump tools don't produce a crashdump.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/103255
The problem is not making the kernel crash, that's easy :) The issue is
that no crash dump is ever generated. The whole kexec dump stuff just
doesn't seem to work. I already went through all the troubleshooting
tips and tricks, but it the kernel just crashed and hangs forever and
only a reset work
hmm, try this.
kernel.panic_on_oops = 0
kernel.softlockup_panic = 0
kernel.unknown_nmi_panic = 0
kernel.panic_on_unrecovered_nmi = 0
kernel.panic_on_io_nmi = 0
kernel.hung_task_panic = 0
Make sure these are all set to 1 in /etc/sysctl.conf and then run sysctl
-p
Also, lets configure ftrace, see
I've been trying to get the crashdump stuff to work, but it just won't
generate a dump, or do anything at all when the kernel crashes... Is
there another way to get the info you want? Would a console screenshot
with a high res console work?
About the hanging processes: The only processes I saw in
I should have been more specific, please set kernel.hung_task_panic as well,
which
should trigger on the "blocked more than N sec" events.
Also, if you still have the system in this state. Does ps | aux show a series
of kpartx
processes blocked?
--
You received this bug notification because yo
** Attachment added: "syslog.test2.survived.gz"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3457383/+files/syslog.test2.survived.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-too
I just retested with the multipath-tools version
'0.4.9-3ubuntu5+lp1032250dbg1', on 2 systems simulatiously. The test
consisted of repeatedly shutting down the fibre port in the switch for
one of the paths. One system survived (see syslog.test2.survived.gz),
one system did not (syslog.test2.broken.
@Peter: I'll try do reproduce on our acceptance systems with crashdump
installed and report back.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath]
What I really need is a crashdump. I'm simply short on time to reproduce
this myself.
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe
Configure sysctl to panic on oops, that should do it.
This stack section is interesting.
Dec 9 09:18:27 ealxs00195 kernel: [1726974.078795] RIP:
0010:[] []
_ra
: Monday, December 10, 2012 5:07 PM
To: Chen, Vincent
Subject: [Bug 1032550] Re: [multipath] failed to get sysfs information
** Attachment added: "My multipath.conf"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3456042/+files/multipath.conf
--
Yo
I'm seeing the same issue with an EMC clariion, see attached syslog. On
my systems this problem leads to hanging processes and a server crash
that can only be fixed with a reboot ..
** Attachment added: "syslog of multipath failure"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bu
** Attachment added: "My multipath.conf"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3456042/+files/multipath.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
htt
So you restarted multipath-tools or rebooted before testing again? I was afraid
of this,
the RH patch isn't even upstream and was applied against a different code base.
There
may be additional patches that have a cumulative effect that we're missing.
--
You received this bug notification becaus
i have applied the fix, however the issue still happened :-(
ii kpartx 0.4.9-3ubuntu5+lp1032250dbg1
create device mappings for partitions
ii multipath-tools 0.4.9-3ubuntu5+lp1032250dbg1
maintain multipath block device access
-
@Vincent
I have a test package for you to try.
Add this ppa, https://launchpad.net/~peter-petrakis/+archive/storage
The install incantation should be:
apt-get install multipath-tools=0.4.9-3ubuntu5+lp1032250dbg1
It includes a fix to the state checker which *should* eliminate the sysfs
coherenc
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] failed to get sys
@peter
I have change the filter and update into new init ram disk, thanks.
For powerpath issue, i reproduce by shutdown FC switch port. Here is new
complete syslog of whole prodefure and multipath result.
1)multipath_before_port_down --> multipath status before shutdown port
2)multipath_port_do
@Vincent
Could you please attach the syslog associated with this fault?
How reproducible is this?
Also I noticed that your lvm.conf is a little broken.
scan = [ "/dev" ]
...
filter = [ "r/block/", "r/disk/", "r|/dev/sd.*|", "a/.*/" ]
Since the scan starts in /dev, that's the root of the
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Peter Petrakis (peter-petrakis)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipa
Here is OS and Packge info also attach log and configuration.
root@Linux51:/var/tmp# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04 LTS
Release:12.04
Codename: precise
root@Linux51:/var/tmp# dpkg -s multipath-tools
Package: multipath
35 matches
Mail list logo
