All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandra Seetharaman <sekharan@us.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Need Help
Date: Thu, 17 Jan 2008 10:37:41 -0800	[thread overview]
Message-ID: <1200595061.7183.60.camel@linuxchandra> (raw)
In-Reply-To: <EEBC5C82F965344199BFA3E6047FE13302E8B7@SAUSEXMB2.amd.com>

Without the /etc/fstab, this is my hunch: you are using /dev/mpath
in /etc/fstab. Try /dev/mapper instead.

On Thu, 2008-01-17 at 08:35 -0600, Nath, Varun wrote:
> Hi,
> 
>  
> 
> I am trying to configure multipathing on Red hat 4 update 6 64 bit.
> 
>  
> 
> Below is the list of RPM I have installed
> 
>  
> 
> rpm -qa | grep mapper
> 
> device-mapper-1.02.21-1.el4
> 
> device-mapper-1.02.21-1.el4
> 
> device-mapper-multipath-0.4.5-27.RHEL4
> 
>  
> 
> The hardware is Sun x4600 and I am using QLA cards. The system has two
> LUNs presented to it of size 10 GB and size 90 GB
> 
>  
> 
> There is a problem when I configure file system on it. I am able to
> access and mount the file system. But when I add those entries
> in /etc/fstab, the system would not recognize those devices. 
> 
>  
> 
> Below is the output from multipath command
> 
>  
> 
> multipath -ll
> 
> mpath5 (3600508b40010541d00009000065d0000)
> 
> [size=90 GB][features="1 queue_if_no_path"][hwhandler="0"]
> 
> \_ round-robin 0 [prio=100][active]
> 
>  \_ 1:0:0:2 sdd 8:48  [active][ready]
> 
>  \_ 2:0:0:2 sdh 8:112 [active][ready]
> 
> \_ round-robin 0 [prio=20][enabled]
> 
>  \_ 1:0:1:2 sdf 8:80  [active][ready]
> 
>  \_ 2:0:1:2 sdj 8:144 [active][ready]
> 
>  
> 
> mpath4 (3600508b40010541d00009000065a0000)
> 
> [size=10 GB][features="1 queue_if_no_path"][hwhandler="0"]
> 
> \_ round-robin 0 [prio=100][enabled]
> 
>  \_ 1:0:1:1 sde 8:64  [active][ready]
> 
>  \_ 2:0:1:1 sdi 8:128 [active][ready]
> 
> \_ round-robin 0 [prio=20][enabled]
> 
>  \_ 1:0:0:1 sdc 8:32  [active][ready]
> 
>  \_ 2:0:0:1 sdg 8:96  [active][ready]
> 
>  
> 
>  
> 
> Also, below is my /etc/multipath.conf
> 
>  
> 
> # This is an example configuration file for device mapper multipath.
> 
> # For a complete list of the default configuration values, see
> 
> # /usr/share/doc/device-mapper-multipath-0.4.5/multipath.conf.defaults
> 
> # For a list of configuration options with descriptions, see
> 
> # /usr/share/doc/device-mapper-
> multipath-0.4.5/multipath.conf.annotated
> 
>  
> 
>  
> 
> # Blacklist all devices by default. Remove this to enable multipathing
> 
> # on the default devices.
> 
> #devnode_blacklist {
> 
> #        devnode "*"
> 
> #}
> 
>  
> 
> ## Use user friendly names, instead of using WWIDs as names.
> 
> defaults {
> 
>         user_friendly_names yes
> 
>         selector   "round-robin 0"
> 
> }
> 
>  
> 
>  
> 
> ## By default, devices with vendor = "IBM" and product = "S/390.*" are
> 
> ## blacklisted. To enable mulitpathing on these devies, uncomment the
> 
> ## following lines.
> 
> #devices {
> 
> #       device {
> 
> #               vendor                  "IBM"
> 
> #               product                 "S/390 DASD ECKD"
> 
> #               path_grouping_policy    multibus
> 
> #               getuid_callout          "/sbin/dasdview -j -f /dev/%n"
> 
> #               path_checker            directio
> 
> #       }
> 
> #}
> 
>  
> 
>  
> 
> ##
> 
> ## This is a template multipath-tools configuration file
> 
> ## Uncomment the lines relevent to your environment
> 
> ##
> 
> #defaults {
> 
> #       udev_dir                /dev
> 
> #       polling_interval        10
> 
> #       selector                "round-robin 0"
> 
> #       path_grouping_policy    multibus
> 
> #       getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
> 
> #       prio_callout            /bin/true
> 
> #       path_checker            readsector0
> 
> #       rr_min_io               100
> 
> #       rr_weight               priorities
> 
> #       failback                immediate
> 
> #       no_path_retry           fail
> 
> #       user_friendly_name      yes
> 
> #}
> 
> ##
> 
> ## The wwid line in the following blacklist section is shown as an
> example
> 
> ## of how to blacklist devices by wwid.  The 3 devnode lines are the
> 
> ## compiled in default blacklist. If you want to blacklist entire
> types
> 
> ## of devices, such as all scsi devices, you should use a devnode
> line.
> 
> ## However, if you want to blacklist specific devices, you should use
> 
> ## a wwid line.  Since there is no guarantee that a specific device
> will
> 
> ## not change names on reboot (from /dev/sda to /dev/sdb for example)
> 
> ## devnode lines are not recommended for blacklisting specific
> devices.
> 
> ##
> 
> devnode_blacklist {
> 
>        wwid 3600508e000000000ed7fb52911133c06
> 
>         devnode "^(ram|raw|loop|fd|md|sr|scd|st)[0-9]*"
> 
>         devnode "^hd[a-z]"
> 
> }
> 
> #multipaths {
> 
> #       multipath {
> 
> #               wwid
> 3600508b4000156d700012000000b0000
> 
> #               alias                   yellow
> 
> #               path_grouping_policy    multibus
> 
> #               path_checker            readsector0
> 
> #               path_selector           "round-robin 0"
> 
> #               failback                manual
> 
> #               rr_weight               priorities
> 
> #               no_path_retry           5
> 
> #       }
> 
> #       multipath {
> 
> #               wwid                    1DEC_____321816758474
> 
> #               alias                   red
> 
> #       }
> 
> #}
> 
> #devices {
> 
> #       device {
> 
> #               vendor                  "COMPAQ  "
> 
> #               product                 "HSV110 (C)COMPAQ"
> 
> #               path_grouping_policy    multibus
> 
> #               getuid_callout          "/sbin/scsi_id -g -u -
> s /block/%n"
> 
> #               path_checker            readsector0
> 
> #               path_selector           "round-robin 0"
> 
> #               hardware_handler        "0"
> 
> #               failback                15
> 
> #               rr_weight               priorities
> 
> #               no_path_retry           queue
> 
> #       }
> 
> #       device {
> 
> #               vendor                  "COMPAQ  "
> 
> #               product                 "MSA1000         "
> 
> #               path_grouping_policy    multibus
> 
> #       }
> 
> #}
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Here is the contents of the /dev/mpath/
> 
>  
> 
> [root@x mpath]# pwd
> 
> /dev/mpath
> 
> [root@x mpath]# ls -all
> 
> total 0
> 
> drwxr-xr-x   2 root root   80 Jan 16 17:34 .
> 
> drwxr-xr-x  12 root root 5260 Jan 17 08:17 ..
> 
> lrwxrwxrwx   1 root root    7 Jan 16 17:34 mpath4 -> ../dm-8
> 
> lrwxrwxrwx   1 root root    7 Jan 16 17:34 mpath5 -> ../dm-9
> 
>  
> 
>  
> 
>  
> 
>  
> 
> Can anyone please help me with this? I think I am missing some
> configuration on the system which is causing this. 
> 
>  
> 
> Thanks,
> 
>  
> 
>  
> 
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
-- 

----------------------------------------------------------------------
    Chandra Seetharaman               | Be careful what you choose....
              - sekharan@us.ibm.com   |      .......you may get it.
----------------------------------------------------------------------

  parent reply	other threads:[~2008-01-17 18:37 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 14:35 Need Help Nath, Varun
2008-01-17 18:24 ` Pradipmaya Maharana
2008-01-17 18:34   ` Nath, Varun
2008-01-17 18:40     ` Pradipmaya Maharana
2008-01-17 20:15       ` Nath, Varun
2008-01-17 20:28         ` Pradipmaya Maharana
2008-01-17 20:35           ` malahal
2008-01-17 20:39             ` Nath, Varun
2008-01-17 20:45               ` Nath, Varun
2008-01-17 21:10                 ` Nath, Varun
2008-01-17 21:34                   ` Chandra Seetharaman
2008-01-17 21:37                     ` Nath, Varun
2008-01-17 22:43                       ` Pradipmaya Maharana
2008-01-17 21:12                 ` Pradipmaya Maharana
2008-01-17 21:13                   ` Nath, Varun
2008-01-21 17:37                     ` Nath, Varun
2008-01-17 20:30         ` malahal
2008-01-17 20:36           ` Nath, Varun
2008-01-17 20:44             ` malahal
2008-01-17 20:46               ` Nath, Varun
2008-01-17 18:37 ` Chandra Seetharaman [this message]
2008-01-17 18:40   ` Nath, Varun
2008-01-17 19:02     ` Chandra Seetharaman
2008-01-17 19:09       ` Pradipmaya Maharana
2008-01-17 19:18         ` Chandra Seetharaman
2008-01-17 20:05       ` Nath, Varun
2008-01-17 20:15         ` malahal
2008-01-17 20:14       ` malahal
2008-01-17 20:24         ` Nath, Varun
  -- strict thread matches above, loose matches on Subject: below --
2021-10-26  4:53 Need help Brad Knorr
2021-10-26  7:14 ` Daniel
2021-07-06  5:27 priyabrata mishra
2019-07-24  7:10 Gobinda Nandi
2019-07-24 16:16 ` Emily Shaffer
2012-07-13 11:13 Need Help rakesh
2008-01-30 10:40 need help Daniel Vera
2008-01-13 11:09 Need help Ramachandran ms
2008-01-13 13:59 ` Nick Kossifidis
     [not found] <002501c7e6c8$a6079170$a378c00a@chia>
2007-08-27  2:43 ` Tejun Heo
     [not found] <86Xi2-6La-421@gated-at.bofh.it>
2007-04-06 21:24 ` need help Bodo Eggert
2007-04-06  7:49 vjn
2007-04-08 18:00 ` Bill Davidsen
2007-02-19 13:45 Need help Lina
2005-12-06  5:14 need Help arijit.sinharay
2005-12-06  6:02 ` Komal Shah
2005-03-22  5:15 Need help Naveen Kumar Atmakuri
2005-03-22 21:36 ` Kumar Gala
2004-04-16 19:17 need help Khanh Tran
2004-04-16 18:28 Matt Robineau
2004-04-16 19:26 ` Antony Stone
2004-04-16 17:32 Xen cpu usage limting Mark Williamson
2004-04-20 15:44 ` Need help I RATTAN
2004-04-20 16:27   ` Borut Mrak
2004-04-20 18:02   ` I RATTAN
2004-04-20 18:23     ` Rolf Neugebauer
2004-04-21  0:24   ` I RATTAN
2003-10-30  7:51 need help Pius Jerry
2003-10-30  9:30 ` Nick Piggin
2003-07-23 20:46 Need HELP Vladimir Vanyukov
2003-04-29 10:21 need help Karthik RC
2003-04-29  6:43 ` hare ram
2003-04-29  7:35 ` Julius Wijaya
2003-04-29  9:27 ` Maciej Soltysiak
2003-02-06 14:35 Need help Yates, Ben
2002-09-27 11:08 Need Help Mohammad Shakir
2002-09-29 22:26 ` Davide
2002-09-29 22:40   ` Antony Stone
2002-08-10  1:14 Need help Muhammad Farooq Bhatti
2002-08-09 14:10 ` Patrice DUMAS - DOCT
2002-08-09 14:24 ` Andreas Behnert
     [not found] <3D04BA0E.7000702@metaparadigm.com>
2002-06-13 14:21 ` need help manjuanth n
2002-06-13 14:21 ` manjuanth n
2002-06-08 11:27 manjuanth n
2002-06-08 19:43 ` Michael Clark
2002-06-10 14:21   ` manjuanth n
2002-06-10 17:04     ` Patrick Mansfield
2002-06-13 14:25   ` manjuanth n
2002-06-13 14:25   ` manjuanth n
2000-01-10 19:30 Need Help Pravin Pathak
2000-01-12  9:35 ` Gabriel Paubert

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=1200595061.7183.60.camel@linuxchandra \
    --to=sekharan@us.ibm.com \
    --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.