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
@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
** 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: 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
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,
** 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
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.
We need a full apport collect to see the fall out from loading the
module.
apport-collect -p linux 916200
Thanks.
** Changed in: ipmitool (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
@Asif
Get the apport data any way you can. I merely offered a popular manner to
accomplish it. Also, please don't change bug states without justification. The
point of Incomplete is part of the bug triage process where a developer has
posed a question etc and is waiting for that request to be
** Changed in: ipmitool (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipmitool in Ubuntu.
https://bugs.launchpad.net/bugs/916200
Title:
missing kernel module ipmi_si module
To manage
Public bug reported:
There's an interesting feature called find_multipaths that was first
mentioned here on dm-devel in July 2011.
https://www.redhat.com/archives/dm-devel/2011-July/msg00102.html
It's now the corner stone of dm multipath configuration in the RHEL 6 DM
Multipath configuration
** Attachment added: 0021-RHBZ-558636-add-find-multipaths.patch
https://bugs.launchpad.net/bugs/956128/+attachment/2876175/+files/0021-RHBZ-558636-add-find-multipaths.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
)
a¡±¡±a¡±€ (8:96)
mpath14-part1 (252:9)
Thank you. -- Peter
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Peter Petrakis (peter-petrakis)
--
You received this bug notification because you
://help.ubuntu.com/12.04/serverguide/dm-multipath-chapter.html
Take care.
-- Peter
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Invalid
** Changed in: multipath-tools (Ubuntu)
Assignee: Peter Petrakis (peter-petrakis) = (unassigned)
--
You received this bug notification because you
-devices.html
#multipath-devices-in-logical-volumes
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Peter Petrakis (peter-petrakis)
** Changed in: multipath-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
-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/1013724
Title:
Setting prio const in multipath.conf
This has been resolved by updating the documentation in the serverguide.
https://help.ubuntu.com/12.04/serverguide/device-mapper-
multipathing.html#multipath-new-and-changed-features
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug
-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/927540
Title:
multipath ignores blacklist
In examining the ioctl interface to device mapper (kernel), I have not found
any architecture that
assures that when a device mapper device has been marked for deletion, that
this information is
relayed back to userspace so it can block on this deletion. An example will
clarify things.
In SD
Should really be won't fix but I apparently can't set it.
--
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/585027
Title:
Race condition with dmsetup causes 'map already
@Alasdair
It's buried in the description:
We were attempting variants of 'while true; do sudo multipath -F; sudo
multipath -v4 ; done' to create a set of udev add/remove events and
noticed that shortly after starting, no output appeared within the
'udevadm monitor' command.
So it appears that
So when this bug was first reported we were using multipath 0.4.8, it doesn't
appear
to have this cookie mechanism. 0.4.9 does (oneiric and higher); I have been
unable to reproduce the issue with 0.4.9. Going back through the logs...
From 8d63b33d0996e141a2451df552b062b908db15bc Mon Sep 17
Your blacklist definition is wrong. You provided.
blacklist {
wwid 3600605b0039afe20ff54052e7d38
vendor SMART
product SMART
}
defaults {
user_friendly_names yes
}
wwid cites an entire device, vendor product cite a different device and must
be
included
If your device is mounted, you won't be able to flush it, flush ==
destroy.
OK. so it's not just you, I can recreate this.
Coincidentally, I also have an HP RAID controller and see the same warning
message. This device *is blacklisted* but apparently it's still getting probed.
Shouldn't be
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Confirmed
--
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/1020436
Title:
Cannot read superblock after FC
Thanks for all the feedback, there's quite a bit of information here to sort
through.
In the meanwhile, it would be an interesting data point to see how well this
array
functions under multipath 0.4.9, which is what Precise, the new LTS uses.
This can be accomplished by using apt pinning.
Alrighty.
[OK] lvm.conf device blacklist
[OK] multipath.conf, sans fix I already pointed out
You can ignore that FW blurb, it's just a script that shouldn't be so noisy.
failover logs *look good*
bug-1020436$ grep fail_path multipathd_stdout.log | sort -u
Jul 10 15:08:25 | libdevmapper:
Retested on precise base and downgraded to multipath-tools 0.4.8-14ubuntu4
on generic 3.2.0.27.29. Ran unit test for several hours, no fault found.
Intend to downgrade to lucid kernel and retest, hopefully it pops then, save
me the trouble of installing lucid somewhere.
--
You received this bug
Using the lucid kernel, I was able to reproduce, though it took a lot longer
than
original report implied, easily over an hour, probably more than 3 I wasn't
watching
it the entire time.
multipath-tools 0.4.8-14ubuntu4.10.04.2
kernel 2.6.32-41-generic
udevadm monitor simply stops responding.
** Changed in: multipath-tools (Ubuntu)
Status: Invalid = Confirmed
--
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/585027
Title:
Race condition with dmsetup causes
Hmm, we've got some counter indicators here.
lvs claims that the volumes are active. But the probe itself
is showing problems reading the volumes.
XFS is telling us that it cannot write it's journal to disk.
[1039812.311433] Filesystem dm-4: Log I/O Error Detected. Shutting down
filesystem:
scratch the ext3 test, I just re-read the description.
I've replicated this behaviour using both xfs and ext4 filesystems, on multiple
different luns presented to the server.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
It doesn't look like your lvm.conf filter is working.
(pvdisplay)
/dev/sdb: block size is 4096 bytes
/dev/sdb: lvm2 label detected
Ignoring duplicate PV RLOhdDURbD7uK2La3MDK2olkP0BF2Tu7 on /dev/sdb -
using dm /dev/mapper/mpath0
Closed /dev/sdb
Opened /dev/sdc
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = 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/1020436
Title:
Cannot read superblock after FC
@gheeke
Did you try the alternate config file style I proposed in comment #5?
Thanks.
--
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/927540
Title:
multipath ignores
Hmm, A reproduction case is going to be necessary, there are some
weird things going on in syslog.2 which I'm unfamiliar with. Unfortunately,
I don't have access to a symmetrix either. I really need to have multipathd
running
in the foreground, with full logging to a file, to catch what went
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = 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/1030040
Title:
multipath-tools create duplicate
** 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)
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
@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
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
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 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
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'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
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
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
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
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:
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
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
** Visibility changed to: Private
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/788326
Title:
Ubuntu 10.04 LTS guest did not boot after install
--
Ubuntu-server-bugs mailing list
We had another incident of this fault, but with an EMC Clariion CX4-120.
After eliminating LVM, and moving to a default MP config. It wasn't
until we removed the change rule to the 95-multipath.tools script
that the udev error messages ceased. I'm convinced that this
approach for the boot scripts
@John, I've got a test for you.
- stop multipathd: service multipath-tools stop
- monitor udev events as root: udevadm monitor
There should be no new change events.
then in a separate terminal, as root run:
/sbin/mpath_prio_netapp /dev/sdb (or any netapp device)
do you see a change event each
Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp that should
not generate any more change events for you. Please post
for comparison that this new version returns the same data
as the old one.
move the old mpath_prio_netapp to
I can understand that. Attached is a debdiff of the updated package.
I must stress that may not be the final form of the solution. I'm
chatting with Douglas Gilbert (sg io maintainer) now about this.
So far it appears that using an SD device as the target for sg io
can have unintended side
** Changed in: multipath-tools (Ubuntu)
Status: Confirmed = In Progress
** Changed in: udev (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
After chatting with Douglas Gilbert on this I know have a better
understanding of the problem. This very issue has been raised by
him before on linux-scsi and it never saw final resolution.
http://kerneltrap.org/mailarchive/linux-scsi/2010/2/15/6778453
When the file descriptor to the SD device
** Changed in: multipath-tools (Ubuntu)
Status: In Progress = Fix Released
--
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/644489
Title:
constantly changes
also affects udev should be removed.
** Changed in: udev (Ubuntu Lucid)
Status: New = Invalid
** Changed in: udev (Ubuntu Maverick)
Status: New = Invalid
** Changed in: udev (Ubuntu Natty)
Status: New = Invalid
** Package changed: udev (Ubuntu) = ubuntu
** Description
** Changed in: ubuntu
Status: Invalid = Confirmed
** Changed in: Ubuntu Lucid
Status: Invalid = Confirmed
** Changed in: Ubuntu Maverick
Status: Invalid = Confirmed
** Changed in: Ubuntu Natty
Status: Invalid = Confirmed
--
You received this bug notification
@All,
The stream of udev change events you've observed has been fixed in multipath
itself by this update.
https://launchpad.net/~peter-petrakis/+archive/storage
It's been proposed for SRU on behalf of (LP: #644489)
Please test and verify that the change events cease. So we can
reconcile
@Joe
What's the status of this? Is the issue resolved? Thanks.
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Moving visibility to private since this is an resolved customer support issue.
We can't fix it if they're not willing to work with us. That probably means
either remote access or on site troubleshooting.
Peter
** Visibility changed to: Private
--
You received this bug notification because you
@ Martin
fix verified, no udev change events generated.
root@kickseed:~# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
^Z
[1]+ Stopped udevadm monitor
root@kickseed:~# bg
[1]+
@Serge
Yes, fix-released for oneiric
I believe natty is covered.
The confusion I think is the changelog references this fix from a
private bug:
multipath-tools (0.4.8-14ubuntu7) natty; urgency=low
* Add patch to fix the expected pathname from multipath uevents
(LP: #660597)
Where this
Experimenting shows that we can have the older config values side by side
with the new ones. e.g.
...
prio_callout /sbin/mpath_prio_alua /dev/%n
prio alua
...
multipath doesn't have a rigid config file format, it seems to slurp symbols
and then seek the key/value pair out on
@Clint
lucid-proposed looks good.
$ apt-cache showpkg multipath-tools
Package: multipath-tools
Versions:
0.4.8-14ubuntu4.10.04.2
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_lucid-proposed_main_binary-amd64_Packages)
(/var/lib/dpkg/status)
# multipath -ll
222fb00015553d0d9dm-3
@Clint
maverick-proposed looks good.
# apt-cache showpkg multipath-tools
Package: multipath-tools
Versions:
0.4.8-14ubuntu4.10.10.2
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_maverick-proposed_main_binary-amd64_Packages)
(/var/lib/dpkg/status)
# multipath -ll
@Joe
Please attach the latest multipath.conf and lvm.conf responsible for this
stream of messages. If you could move over that logs and other stuff
from salesforce into this bug that would be ideal. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
So the paths not showing up with a config file error, a few well
placed regexp and a proper blacklist to filter out the internal disks
solved that. Also added scsi_dh_rdac to initial ramdisk. Now the paths
are up, and stay up. However when we tried testing failover using
a scsi delete of the
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Ubuntu Storage Development Team
(ubuntu-storage-dev)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Changed in: multipath-tools (Ubuntu)
Status: New = Confirmed
--
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/824790
Title:
IBM DS3400 Will Not Bring Up Second
In an addition to the MP issues, LVM was misconfigured. We attempt
to repair this on one of the blades but the config file just wouldn't *take*.
I suspect there was something else going, especially since we didn't
even have direct access to the console and was forced to relay
directives to the
** Branch linked: lp:~peter-petrakis/ubuntu/lucid/multipath-
tools/lp-641151
--
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/641151
Title:
multipath flush always returns 1
It's an indirect crash, if we're script driven, since the output is always
1, the user decided that the return value meant nothing and that
removing the actual path member was OK. Instead a crash occurred.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
:10.04
apt-cache policy multipath-tools | grep Insta
Installed: 0.4.8-14ubuntu4.10.04.2.1
** Branch linked: lp:~peter-petrakis/ubuntu/maverick/multipath-tools/lp-641151
** Branch linked: lp:~peter-petrakis/ubuntu/natty/multipath-
tools/lp-641151
--
You received this bug notification
SRU Justification:
* During development where a customer is aiming to automate storage
provisioning that includes a multipath component. Politely tearing
down the dm table before physically removing the device is part of
best practices for removing devices at runtime. Since multipath -f/-F
** Changed in: multipath-tools (Ubuntu)
Assignee: Ubuntu Storage Development Team (ubuntu-storage-dev) =
(unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Hi James,
Thanks for the feedback. Will track bug 789229 and rebase/propose
accordingly.
--
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/641151
Title:
multipath flush
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Invalid
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/716659
Title:
[EMC
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.
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
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:
Binary package hint: multipath-tools
This was exposed on the Intel IMS SAN which is an ODM'd Promise Vtrak
variant on 10.04 server. The SAN has Active/Standby capabilities and
is configured for failover. It probably affects other SANs too.
Setup:
multipath'd SAN consisting
1 - 100 of 106 matches
Mail list logo
