Your message dated Tue, 22 Feb 2011 13:44:05 +0530
with message-id <[email protected]>
and subject line Re: Bug#614353: multipath-tools-boot: upgrade to squeeze
breaks machines with root on iscsi
has caused the Debian Bug report #614353,
regarding multipath-tools-boot: upgrade to squeeze breaks machines with root on
iscsi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
614353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614353
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: multipath-tools-boot
Version: 0.4.8+git0.761c66f-9
Severity: normal
Hi,
I have a bunch of virtual (kvm) lenny machines, booting with iscsi-root.
An update to squeeze consistently breaks booting, because
the /dev/disk/by-uuid symbolic links do not point to the correct mpath
devices, e.g.
on squeeze:
c33ab1d4-4861-4638-a753-5c3ccfb47847 -> ../../sdb1
on lenny:
c33ab1d4-4861-4638-a753-5c3ccfb47847 -> ../../dm-1
instead, they point to the underlying physical device, which leads to
"Device or resource busy" when trying to mount the root filesystem.
The output of multipath -ll under squeeze says:
3600c0ff000da565a9721ed4b01000000dm-0 HP ,MSA2324i
size=9.3G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| `- 3:0:0:1 sdb 8:16 active ready running
|-+- policy='round-robin 0' prio=10 status=enabled
`- 2:0:0:1 sda 8:0 active ready running
and under lenny:
3600c0ff000da565a9721ed4b01000000dm-0 HP ,MSA2324i
[size=9.3G][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 3:0:0:1 sdb 8:16 [active][ready]
\_ round-robin 0 [prio=1][enabled]
\_ 2:0:0:1 sda 8:0 [active][ready]
So, the multipath devices are there.
Under /dev/mapper/ is see symlinks under squeeze, e.g.
3600c0ff000da565a9721ed4b01000000-part1 -> ../dm-1
whereas under lenny I see blockdevices (however, I do not know if this
is a problem or intended).
Also I am not sure, if multipath-tools-boot is causing the problem,
please re-assign if necessary.
Please also note, that I am reporting the bug from a lenny system.
(however, I adjusted the package version in the header).
Package versions on the squeeze system are:
multipath-tools(-boot) 0.4.8+git0.761c66f-9
initramfs-tools 0.98.8
udev 164-3
linux-image-2.6.32-5-amd64 2.6.32-30
Best regards,
Hp
-- Package-specific info:
/etc/multipath.conf does not exist.
-- System Information:
Debian Release: 5.0.8
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages multipath-tools-boot depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration
management sy
ii initramfs-tools 0.92o tools for generating an
initramfs
ii multipath-tools 0.4.8-14+lenny2 maintain multipath block
device ac
multipath-tools-boot recommends no packages.
multipath-tools-boot suggests no packages.
-- debconf information:
multipath-tools-boot/scsi_id:
--- End Message ---
--- Begin Message ---
On 02/22/2011 11:22 AM, Hanspeter Kunz wrote:
>> > If yes, why are you not using the multipath guaranteed /dev/mapper/*
>> > entries?
> I guess I could do that, but this would be a workaround. Or is there a
> reason for not creating disk/by-uuid links?
>
Persistence is not available for devices everywhere in the kernel.
/dev/sd[??]
Not persistent. They can change of reboots based on which one gets
discovered first
/dev/dm-*
Not persistent. These are device mapper devices with the same caveat I
mentioned above.
/dev/disk/by*
I don't know the history behind why it was started. But these entries
are symlinks to block devices. Now when block devices are locked (like
in your case), you can't use any of these entries.
/dev/mapper/* is the recommended way of using any Device Mapper
solution. Be it linear, crypt, multipath, snapshot or anything else.
I'm closing this bug report. If you have other info, please feel free to
open it.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
--- End Message ---
