On Mon, 2011-02-28 at 03:07 +0530, Ritesh Raj Sarraf wrote:
On 02/27/2011 04:26 PM, Hanspeter Kunz wrote:
ok, let me restate the issue, it is actually quite simple:
During boot, after multipath assembled its devices, I see
the /dev/mapper multipath devices (which is fine) but
the
On Mon, 2011-02-28 at 14:34 +0100, Hanspeter Kunz wrote:
On Mon, 2011-02-28 at 03:07 +0530, Ritesh Raj Sarraf wrote:
On 02/27/2011 04:26 PM, Hanspeter Kunz wrote:
ok, let me restate the issue, it is actually quite simple:
During boot, after multipath assembled its devices, I see
On 02/28/2011 08:05 PM, Hanspeter Kunz wrote:
If I do the above steps on a lenny system (with otherwise identical
configuration) I get the same results except that after step 4
the /dev/disk/by/uuid symlinks point to the /dev/dm-x devices (as it
should be).
If I boot the squeeze system (by
On Mon, 2011-02-28 at 20:23 +0530, Ritesh Raj Sarraf wrote:
On 02/28/2011 08:05 PM, Hanspeter Kunz wrote:
If I do the above steps on a lenny system (with otherwise identical
configuration) I get the same results except that after step 4
the /dev/disk/by/uuid symlinks point to the /dev/dm-x
On 02/28/2011 08:47 PM, Hanspeter Kunz wrote:
Ha! I upgraded to dmsetup from sid. Now it works :)
I'm glad that your issue is resolved.
Any ideas what is the delta of dmsetup between squeeze and sid?
I think this bug should still be assigned to dmsetup targeting the
squeeze version.
--
Ritesh
On Mon, 2011-02-28 at 20:56 +0530, Ritesh Raj Sarraf wrote:
On 02/28/2011 08:47 PM, Hanspeter Kunz wrote:
Ha! I upgraded to dmsetup from sid. Now it works :)
I'm glad that your issue is resolved.
Any ideas what is the delta of dmsetup between squeeze and sid?
I think this bug should
On Sun, 2011-02-27 at 12:02 +0530, Ritesh Raj Sarraf wrote:
severity 614353 normal
thanks
On 02/25/2011 03:26 PM, Hanspeter Kunz wrote:
I switched to the /dev/mapper devices for booting as you suggested. that
works.
interestingly, after the boot has finished, the /dev/disk/by-uuid
On 02/27/2011 04:26 PM, Hanspeter Kunz wrote:
ok, let me restate the issue, it is actually quite simple:
During boot, after multipath assembled its devices, I see
the /dev/mapper multipath devices (which is fine) but
the /dev/disk/by-uuid symlinks point to one of the underlying iscsi
severity 614353 normal
thanks
On 02/25/2011 03:26 PM, Hanspeter Kunz wrote:
I switched to the /dev/mapper devices for booting as you suggested. that
works.
interestingly, after the boot has finished, the /dev/disk/by-uuid
symlinks are created correctly.
Therefore, the only problem is
Hi there,
I switched to the /dev/mapper devices for booting as you suggested. that
works.
interestingly, after the boot has finished, the /dev/disk/by-uuid
symlinks are created correctly.
Therefore, the only problem is that they are not created during boot.
This is clearly a bug.
I do not
Hello,
On 02/22/2011 05:16 PM, Hanspeter Kunz wrote:
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
On Tue, Feb 22, 2011 at 06:28:30PM +0530, Ritesh Raj Sarraf wrote:
[..snip..]
I have taken up the multipath-tools maintenance very recently. I can't
really comment on what was in Lenny. But I can talk on multipath best
practices.
In multipath, you can disable user_friendly_names, which will
On Tue, 2011-02-22 at 01:31 +0530, Ritesh Raj Sarraf wrote:
Hello,
In your setup, you've mentioned iscsi-root. But are you using multipath
on top of it?
sure.
If yes, why are you not using the multipath guaranteed /dev/mapper/*
entries?
I guess I could do that, but this would be a
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.
Hello,
In your setup, you've mentioned iscsi-root. But are you using multipath
on top of it?
If yes, why are you not using the multipath guaranteed /dev/mapper/*
entries?
On 02/21/2011 03:43 PM, Hanspeter Kunz wrote:
Package: multipath-tools-boot
Version: 0.4.8+git0.761c66f-9
Severity: normal
15 matches
Mail list logo
