Still present in the 21.10 daily build. The "fix" is to kill the process
and uninstall the package.
https://askubuntu.com/questions/1033405/crackling-and-delayed-sound-
after-upgrading-to-18-04
killall speech-dispatcher
sudo apt-get remove speech-dispatcher
--
You received this bug
Public bug reported:
This host has ipv6 disabled at the kernel level for security/privacy
reasons. When running through the 'lxd init' answer script taking
defaults for just about everything. Concerning network ipv4/v6 support
the default is 'auto'. It is reasonable to assume that 'auto' would do
This used to work on the last LTS. I reached for it today on Xenial and
found it was broken. Now I can't do scale block device testing without
rebooting the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
Ti
** Changed in: multipath-tools (Ubuntu)
Assignee: Peter Petrakis (peter-petrakis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] failed to get sy
Hmm, we might want to assign this to someone who's more active in this
area; I'm just out of time.
** Changed in: libatasmart (Ubuntu)
Assignee: Peter Petrakis (peter-petrakis) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The right thing to do here is to stop using read_threshold and find a
suitable replacement. Blacklisting a command to a drive because it does
the right thing when faced with an illegal command is ridiculous.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Changed the env series, same result.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
@John, I don't dispute that the tools aren't there, but I'm starting to think
juju-core
isn't able to find it.
I created a saucy VM to try and drive this MAAS, it still won't find the
arm tools.
@John (anyone), have you actually seen this work?
ubuntu@saucy:~$ uname -a
Linux saucy
Do I literally need to be on saucy to get these tools? I pinned the
saucy version and it still doesn't work.
ubuntu@bysen:~$ dpkg -l juju-core
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required
Changed the env series, same result.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-02 11:18:08 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
@John, I don't dispute that the tools aren't there, but I'm starting to think
juju-core
isn't able to find it.
I created a saucy VM to try and drive this MAAS, it still won't find the
arm tools.
@John (anyone), have you actually seen this work?
ubuntu@saucy:~$ uname -a
Linux saucy
Public bug reported:
The problem:
I can clearly see that a machine is allocated in response to the bootstrap
request and that the
same machine is destroyed when the env is trashed, yet, I can't get a handle on
the environment.
Odd thing is this problem cropped up all of a sudden. I've been
juju-core appears to be a non-starter.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
Public bug reported:
The problem:
I can clearly see that a machine is allocated in response to the bootstrap
request and that the
same machine is destroyed when the env is trashed, yet, I can't get a handle on
the environment.
Odd thing is this problem cropped up all of a sudden. I've been
juju-core appears to be a non-starter.
ubuntu@bysen:~$ juju -vvv bootstrap --constraints arch=arm -e maas
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:82 filtering tools by
released version
2013-10-01 21:12:17 INFO juju.environs.tools tools.go:29 reading tools with
major version 1
Why do you think this is a multipath problem and not an mdadm problem?
--
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/1217933
Title:
update-grub fails to detect other md OS
not a multipath issue
** Package changed: multipath-tools (Ubuntu) = grub2 (Ubuntu)
--
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/1217933
Title:
update-grub fails to
Right. multipath is for SANs, not RAIDs. Seeing that both of your
arrays are up and running however implies a grub configuration problem.
Moving...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Why do you think this is a multipath problem and not an mdadm problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217933
Title:
update-grub fails to detect other md OS
To manage notifications
not a multipath issue
** Package changed: multipath-tools (Ubuntu) = grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217933
Title:
update-grub fails to detect other md OS
To manage
Right. multipath is for SANs, not RAIDs. Seeing that both of your
arrays are up and running however implies a grub configuration problem.
Moving...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's what humans are for :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217933
Title:
update-grub fails to detect other md OS
To manage notifications about this bug go to:
multipath-tools will grab any devices that are not excluded by the filtering
directives in
multipath.conf. It's a lot like lvm.conf. The operating system has no idea what
these devices
will be used for, you must direct it explicitly.
multipath-tools will grab any devices that are not excluded by the filtering
directives in
multipath.conf. It's a lot like lvm.conf. The operating system has no idea what
these devices
will be used for, you must direct it explicitly.
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Invalid
--
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/1178721
Title:
multipathd fails to create mappings
At this point I would seriously consider obtaining commercial support. This
is clearly a support issue and not a bug and has been closed as invalid. LVM
could
have easier to grok filtering but it does work, you just have to get creative by
changing the scan directory.
For example: UNTESTED
scan
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178721
Title:
multipathd fails to create mappings when multipath.conf is
At this point I would seriously consider obtaining commercial support. This
is clearly a support issue and not a bug and has been closed as invalid. LVM
could
have easier to grok filtering but it does work, you just have to get creative by
changing the scan directory.
For example: UNTESTED
scan
https://help.ubuntu.com/12.10/serverguide/multipath-devices.html
You cannot have a default LVM config co-exist with multipath. They will
race to grab the SD device for map creation and whoever gets there first wins;
they both use device mapper. LVM is configured using UDEV so it's the
first pass,
https://help.ubuntu.com/12.10/serverguide/multipath-devices.html
You cannot have a default LVM config co-exist with multipath. They will
race to grab the SD device for map creation and whoever gets there first wins;
they both use device mapper. LVM is configured using UDEV so it's the
first pass,
I think it's been fixed indirectly, I just haven't had time to test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004243
Title:
multipath installs not working
To manage notifications about this
** Changed in: multipath-tools (Ubuntu)
Status: New = Incomplete
--
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/1135453
Title:
open-iscsi +mpio with multipathd init
AFAIK most of the work upstream is done, there was just some arguing concerning
an additional interface that could freeze/unfreeze filesystems.
https://lkml.org/lkml/2010/6/10/59
I don't think it's in mainline yet. It really needs a sherpa again.
At a minimum, we should integrate the unit test
** Changed in: multipath-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1135453
Title:
open-iscsi +mpio with multipathd init script order errors
To
** 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/1135453
Title:
open
This might be self inflicted. First, we have really good multipath
documentation now.
You're better off following our docs first and then supplementing it with the
vendor
docs if it doesn't work. Many popular SANs have built-in support.
** Changed in: libatasmart (Ubuntu)
Assignee: (unassigned) = Peter Petrakis (peter-petrakis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092622
Title:
disks hang as atasmart is sending
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Peter Petrakis (peter-petrakis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1135453
Title:
open-iscsi +mpio with multipathd
This might be self inflicted. First, we have really good multipath
documentation now.
You're better off following our docs first and then supplementing it with the
vendor
docs if it doesn't work. Many popular SANs have built-in support.
SUMARRY : module-init-tools and binutils must be added to Depends
$ bzr branch lp:ubuntu/crash
Most recent Ubuntu version: 6.1.0-1ubuntu1
$ cd crash
01:21:16crash$ bzr grep Depends debian/
debian/changelog:libncurses in ${shlibs:Depends} (Closes: #318367)
debian/control:Build-Depends:
Nope, just look at the dsc, if the dep isn't there, it's still broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092911
Title:
linux-crashdump: missing binutils dependancy for strings
To
@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
Public bug reported:
SUMMARY:
crash needs strings to interrogate the dump, it's not installed by default.
SOLUTION:
I install binutils and can now read the dump. Please add binutils
to the dependency list.
DETAILS:
# apt-get install linux-crashdump
Reading package lists... Done
Building
@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
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
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
^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
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
Correction:
is crashkernel even configured?
* grep crash /proc/cmdline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] failed to get sysfs information
To manage
^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
Public bug reported:
SUMMARY:
Model Family: Western Digital Caviar Green (Adv. Format)
Device Model: WDC WD20EARX-32PASB0
Appears to be sensitive to illegal smart commands.
The entire drive stalls to handle this creating a massive interruption
(HANG) of service until the error is
For those still affected by this issue please compile the attached test case
and run
against the suspected disk. If it produces
[189046.60] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[189046.75] ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512
in
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
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 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 you
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 you
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:
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:
Considering the time past and that I'm convinced that this is a user
configuration
issue (Support) that should be addressed by comment #11, I'm closing this issue
as Invalid.
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification
Considering the time past and that I'm convinced that this is a user
configuration
issue (Support) that should be addressed by comment #11, I'm closing this issue
as Invalid.
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification
Public bug reported:
https://juju.ubuntu.com/CryptographicSourceVerification
The snippet that makes use of the charm-helpers ppa is off, it won't
function as a copy/paste. The PPA name may be plural but the contents of it
are not. This is correct:
apt-get -qqy charm-helper-sh
# loading
Public bug reported:
https://juju.ubuntu.com/CryptographicSourceVerification
The snippet that makes use of the charm-helpers ppa is off, it won't
function as a copy/paste. The PPA name may be plural but the contents of it
are not. This is correct:
apt-get -qqy charm-helper-sh
# loading
Blueprint changed by Peter Petrakis:
Work items set to:
Work items:
Integrate netdump support: TODO
netdump charm to aggregate dumps in a cloud: TODO
--
Enable kdump mechanism from kdump-tool instead of kexec-tools
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-kdump-tool
That's actually a good point Lukasz, one that I assume folks get by reading the
multipath guide first.
https://help.ubuntu.com/12.04/serverguide/multipath-devices.html
Whenever you use blacklists, in either lvm or multipath, you must update
the initramfs so those config files are copied to the
That's actually a good point Lukasz, one that I assume folks get by reading the
multipath guide first.
https://help.ubuntu.com/12.04/serverguide/multipath-devices.html
Whenever you use blacklists, in either lvm or multipath, you must update
the initramfs so those config files are copied to the
That devnode line is actually part of the default in memory config,
see libmultipath/blacklist.c#setup_default_blist. So try dropping
that.
Just try and keep you multpath.conf as simple as possible,
to even *one* directive, test and record, then iterate until you start to see it
break. It's best
That devnode line is actually part of the default in memory config,
see libmultipath/blacklist.c#setup_default_blist. So try dropping
that.
Just try and keep you multpath.conf as simple as possible,
to even *one* directive, test and record, then iterate until you start to see it
break. It's best
Then the only possible actors left are the actual initramdisk contents e.g.
zcat initrd | cpio -id and examine all the scripts (init, conf/modules) to
determine
how it could be loaded. The absence of the module reference in all of /etc and
/usr/share/initramfs-tools/ tell me that whatever is
*** This bug is a duplicate of bug 991040 ***
https://bugs.launchpad.net/bugs/991040
** This bug has been marked a duplicate of bug 991040
COMRESET failed (errno=-16) on Intel SSD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It looks like the fix was actually isolated upstream:
http://comments.gmane.org/gmane.linux.kernel/1247563
But debate on how to best implement it without effecting other
platforms has stalled it's progress. More investigation is required to
determine it's current status. Please keep comments here
Then the only possible actors left are the actual initramdisk contents e.g.
zcat initrd | cpio -id and examine all the scripts (init, conf/modules) to
determine
how it could be loaded. The absence of the module reference in all of /etc and
/usr/share/initramfs-tools/ tell me that whatever is
Have you verified that the rdac driver is loaded? Also please account for
the contents of /etc/initramfs-tools/modules, scsi_dh_rdac must be
loaded at boot time to be discovered correctly.
** Changed in: multipath-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug
That's never how it works. multipath has no kernel module loading ability. Would
make a nice feature though. I admit that discovering which dh
is the necessary one is a bit arcane and not well documented anywhere.
The best practice here is to load the necessary device handler into your initrd
so
There is no feature, that has ever existed, that has the capacity to *at
runtime*
examine all attached disks, and cross reference their SCSI INQUIRY data to
a table of available device handlers. That table does not exist, if it did, it
would be miserable to maintain.
I checked the udev rules and
Hmm, that's interesting, does that mean that after reboot scsi_dh_rdac is
loaded?
Please verify.
Yes, it is available with the lucid kernel. Also note that if you were to
reference
your vendor documentation, it would probably recommend that you load
rdac driver (been around for a long time
Then we might have a distro bug here, which is weird as I've done hundreds of
SAN installs with lucid and have had to manage the scsi_dh modules everytime.
So on your lucid system, /etc/initramfs-tools/modules should be empty
except for the commented out examples.
The next thing to check is the
There's nothing in any of the priority checkers except scsi cmds. See for
yourself.
bzr+ssh://bazaar.launchpad.net/+branch/ubuntu/lucid/multipath-tools/
path_priority/pp_rdac/pp_rdac.c
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Then we might have a distro bug here, which is weird as I've done hundreds of
SAN installs with lucid and have had to manage the scsi_dh modules everytime.
So on your lucid system, /etc/initramfs-tools/modules should be empty
except for the commented out examples.
The next thing to check is the
There's nothing in any of the priority checkers except scsi cmds. See for
yourself.
bzr+ssh://bazaar.launchpad.net/+branch/ubuntu/lucid/multipath-tools/
path_priority/pp_rdac/pp_rdac.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Have you verified that the rdac driver is loaded? Also please account for
the contents of /etc/initramfs-tools/modules, scsi_dh_rdac must be
loaded at boot time to be discovered correctly.
** Changed in: multipath-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug
That's never how it works. multipath has no kernel module loading ability. Would
make a nice feature though. I admit that discovering which dh
is the necessary one is a bit arcane and not well documented anywhere.
The best practice here is to load the necessary device handler into your initrd
so
There is no feature, that has ever existed, that has the capacity to *at
runtime*
examine all attached disks, and cross reference their SCSI INQUIRY data to
a table of available device handlers. That table does not exist, if it did, it
would be miserable to maintain.
I checked the udev rules and
Hmm, that's interesting, does that mean that after reboot scsi_dh_rdac is
loaded?
Please verify.
Yes, it is available with the lucid kernel. Also note that if you were to
reference
your vendor documentation, it would probably recommend that you load
rdac driver (been around for a long time
@roysk
The thing about inquiry data is that it's incumbent on the target to provide
what the initiator has asked of it. What is open-iscsi connecting to, another
SAN,
if so which make and model? If it's not a HW SAN could you setup an software
iSCSI target server and connect with the existing
** Changed in: open-iscsi (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034015
Title:
Fails to connect to iSCSI target
To manage notifications about this
So here's your problem, which I identified by running wireshark on the pcap
(very helpful, thanks for providing), typing 'iscsi' to filter on that only
and identified the inquiry exchange.
The inquiry cmd open-iscsi send looks fine. The response from the target
however...
0060 00 00 00 00 00 00
My bad, it's a SANRAD (never heard of it, I though you were using some
slang)
http://www.sanrad.com/
Let us know what they think of that pcap you provided, that was very
helpful.
** Description changed:
- Connecting from an Ubuntu 12.04LTS server to a SANRAD switch offering
- iSCSI
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
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
@Vincent: I thought you asked for this case to be closed?
Did you mean to update another bug?
--
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/1030040
Title:
multipath-tools
@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
@Vincent: I thought you asked for this case to be closed?
Did you mean to update another bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030040
Title:
multipath-tools create duplicate device
@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
** 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
** Changed in: multipath-tools (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/1032550
Title:
[multipath] failed to get sysfs information
To manage
** Changed in: lvm2 (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/865280
Title:
LV status is NOT available after mkfs
To manage notifications about this bug
** 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
@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 search,
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Peter Petrakis (peter-petrakis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] failed to get sysfs
1 - 100 of 346 matches
Mail list logo
