All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Domenico Viggiani" <dviggiani@tiscali.it>
To: 'device-mapper development' <dm-devel@redhat.com>
Subject: RE: dup mpath?
Date: Fri, 12 Oct 2007 16:39:07 +0200	[thread overview]
Message-ID: <000101c80cdd$a4de0aa0$222813ac@pitagora.it> (raw)
In-Reply-To: <470F744F.5080709@redhat.com>

> Looks like you have a problem with your bindings 
> (/var/lib/mpath/bindings). This can happen if, for e.g. the 
> /var tree is a separate file system.
> 
> In this case, multipath devices are created by rc.sysinit 
> before /var is mounted. Later on, if the wwid to mpath names 
> in the bindings file are different from those that mpath 
> auto-detected in rc.sysinit you end up with conflicts like 
> this - multipath is trying to re-name the mpath devices 
> according to the entries in the bindings file.
> 
> If LVM has already activated volume groups on the devices 
> this gives you the "map in use" errors you noted above.
> 
> See this bugzilla:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=320151

It's amazing the way you answer me with this wonderful description of the
problem after only a few tens of minutes while regular Red Hat support is
struggling with my call since many days!
In my opinion, this is a limit to the adoption of Linux in the enterprise
environment: it needs too technical involvement from specialized personnel.
I hope that Red Hat will understand that it needs more expert engineers in
the frontline.

Heartfelt thanks and sorry for my bad english
..
Domenico Viggiani

      parent reply	other threads:[~2007-10-12 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12  7:58 dup mpath? Domenico Viggiani
2007-10-12 13:19 ` Bryn M. Reeves
2007-10-12 13:28   ` Bryn M. Reeves
2007-10-12 14:39   ` Domenico Viggiani [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000101c80cdd$a4de0aa0$222813ac@pitagora.it' \
    --to=dviggiani@tiscali.it \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.