All of lore.kernel.org
 help / color / mirror / Atom feed
From: German Staltari <gstaltari@arnet.net.ar>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lot of scsi devices bug
Date: Wed, 10 May 2006 17:53:50 -0300	[thread overview]
Message-ID: <446252DE.2070702@arnet.net.ar> (raw)
In-Reply-To: <44623B1C.2040108@arnet.net.ar>

German Staltari wrote:
> Hi, this is maybe a udev bug, but it affected me when I was creating a 
> lv in a cluster, so it could help some with this configuration.
> When I added some scsi disk (SAN) to the cluster nodes (more than 64 
> SCSI devices),  udev created the device node for capi20 instead of 
> sdbm. This produced  a bad behavior in lvm when I was trying to create 
> the vg's and lv's, it started to give errors like:
>
> Error locking on node node-06: Internal lvm error, check syslog
> Error locking on node node-05: Internal lvm error, check syslog
> Error locking on node node-04: Internal lvm error, check syslog
> Error locking on node node-01: Internal lvm error, check syslog
> Error locking on node node-02: Internal lvm error, check syslog
> Error locking on node node-03: Internal lvm error, check syslog
> Failed to activate new LV.
>
> When I commented out this lines
>
> SYSFS{dev}="68:0",              NAME="capi20"
> SYSFS{dev}="191:[0-9]*",        NAME="capi/%n"
> KERNEL=="capi*",                MODE="0660"
>
> in /etc/udev/rules.d/50-udev.rules, everything worked again.
>
> I hope this could help,
> German Staltari
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
Forgot to add:
FC4 system totally updated

      reply	other threads:[~2006-05-10 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 19:12 [linux-lvm] lot of scsi devices bug German Staltari
2006-05-10 20:53 ` German Staltari [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=446252DE.2070702@arnet.net.ar \
    --to=gstaltari@arnet.net.ar \
    --cc=linux-lvm@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.