Linux Device Mapper development
 help / color / mirror / Atom feed
From: Sajesh Singh <ssingh@amnh.org>
To: dm-devel@redhat.com
Subject: Re: Strange DM issue on boot
Date: Tue, 29 Jul 2008 10:47:24 -0400	[thread overview]
Message-ID: <488F2D7C.9090905@amnh.org> (raw)
In-Reply-To: <156D04C1A9F47A40BBAE9554FDC7CD7802568F08@3parm3.hq.3pardata.com>



Charles Polk wrote:
> The controllers are not happy with the panging on the controllers.
>
>   
Should I not be using the default settings in the /etc/multipath.conf? 
Are there any specific settings that need to be configured to use 
multipathd with an HDS AMS1000 array?

> ----- Original Message -----
> From: dm-devel-bounces@redhat.com <dm-devel-bounces@redhat.com>
> To: dm-devel@redhat.com <dm-devel@redhat.com>
> Sent: Mon Jul 28 13:54:52 2008
> Subject: [dm-devel] Strange DM issue on boot
>
> EL 5.2
> Hitachi AMS1000 array
> Qlogic HBA (qla2xxx driver)
>
> I am seeing a strange issue when rebooting a server connected to the 
> AMS1000 disk array. If I have a mount point defined in /etc/fstab that 
> points to a mulitpathe device I receive the following error:
>
> error calling out /sbin/mpath_prio_hds_modular 8:32
>
> That error would seem to indicate a path failure, but if I remove the 
> entry from /etc/fstab and reboot I am able to mount the device from the 
> command line. I have tried to include the qlogic driver in the initrd, 
> but that did help in any way. Are the dm-multipath drivers loading at 
> the incorrect time? Has anyone ever encountered this before?
>
> Regards,
>
> Sajesh
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>   

  parent reply	other threads:[~2008-07-29 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 21:20 Strange DM issue on boot Charles Polk
2008-07-29  2:07 ` Sajesh Singh
2008-07-29 14:47 ` Sajesh Singh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-28 20:54 Sajesh Singh

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=488F2D7C.9090905@amnh.org \
    --to=ssingh@amnh.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox