need help

need help

[vjn]

in my project i want to code the kernel such that when i plugged my usb it
should ask for password and check it in the kernel space . can anyone help
me
-- 
View this message in context: http://www.nabble.com/need-help-tf3535625.html#a9868997
Sent from the linux-kernel mailing list archive at Nabble.com.

Re: need help

[Bill Davidsen]

vjn wrote:
> in my project i want to code the kernel such that when i plugged my usb it
> should ask for password and check it in the kernel space . can anyone help
> me

I think the correct solution is to use an excrypted mount, and issue the 
mount command manually with the question in user space. There's no code 
to ask for input, nor anyway to positively decide which connected 
terminal is the terminal to ask.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

Need help

[Brad Knorr]

I am new to nft commands.  I wish to use the map feature for port
forwarding.  What I want to achieve is the following

Sftp  incoming  to port 2222 on the public IP to be port forwarded to
private IP on port 22.  So what I found in the docs is this.

% nft add map nat foo { type inet_service : ipv4_addr . inet_service \; }

% nft add element nat foo { \
    1100 : 192.168.1.2 . 5061, \
    1101 : 192.168.1.3 . 5061, \
    1400 : 192.168.1.4 . 5061 \
}
% nft add rule nat pre ip protocol tcp dnat ip addr . port to tcp dport
map @foo


So when I issue the first command I get the following error:
Error: unqualified mapping data type specified in map definition

When I issue the command:  nft add map nat foo { type inet_service :
ipv4_addr \; }

It works just fine.  I am at a loss as to why this is happening.  The
reason I need the mapping is I need to add and remove port forwarding
rules easily with a simple command.

Any help would be greatly appreciated.
Brad

Re: Need help

[Daniel]

Hello Brad

Le 26/10/2021 à 06:53, Brad Knorr a écrit :
> I am new to nft commands.  I wish to use the map feature for port
> forwarding.  What I want to achieve is the following
>
> Sftp  incoming  to port 2222 on the public IP to be port forwarded to
> private IP on port 22.  So what I found in the docs is this.
>
> % nft add map nat foo { type inet_service : ipv4_addr . inet_service \; }
>
> % nft add element nat foo { \
>      1100 : 192.168.1.2 . 5061, \
>      1101 : 192.168.1.3 . 5061, \
>      1400 : 192.168.1.4 . 5061 \
> }
> % nft add rule nat pre ip protocol tcp dnat ip addr . port to tcp dport
> map @foo
>
>
> So when I issue the first command I get the following error:
> Error: unqualified mapping data type specified in map definition
>
> When I issue the command:  nft add map nat foo { type inet_service :
> ipv4_addr \; }
>
> It works just fine.  I am at a loss as to why this is happening.  The
> reason I need the mapping is I need to add and remove port forwarding
> rules easily with a simple command.
>
> Any help would be greatly appreciated.
> Brad

% nft add map nat foo { type inet_service : ipv4_addr \; flags interval \; } should do the job

-- 
Daniel

Need help

[Gobinda Nandi]

Hi,

I have cloned a project using GIT. There I am facing one issue and nobody is confident that when that issue was not there. They are convinced that earlier it was working well but noe its not. I am trying revert the version but still I am finding the issue. I know this can depend upon several variable but at least can you suggest how to check from git log.

If this is not a right place ask this type of query then plz ignore it.

Regards
Gobinda Nandi
Software Engineer

Re: Need help

[Emily Shaffer]

Hi Gobinda, if you have a consistent way to reproduce the issue, check
out `git bisect`: https://git-scm.com/docs/git-bisect

 - Emily


On Wed, Jul 24, 2019 at 12:11 AM Gobinda Nandi
<Gobinda.Nandi@dynacommerce.com> wrote:
>
> Hi,
>
> I have cloned a project using GIT. There I am facing one issue and nobody is confident that when that issue was not there. They are convinced that earlier it was working well but noe its not. I am trying revert the version but still I am finding the issue. I know this can depend upon several variable but at least can you suggest how to check from git log.
>
> If this is not a right place ask this type of query then plz ignore it.
>
> Regards
> Gobinda Nandi
> Software Engineer
>


-- 
Emily Shaffer

Need Help

[rakesh]

[-- Attachment #1: Type: text/plain, Size: 439 bytes --]

Hello everyone,

 

I am new to linux and i also want to contribute in linux community.

I am running Ubuntu 11.04 and i have downloaded linux-2.6.35.13 for
learning. so kindly tell me how to set up and starting kernel development.

I did tried some books and websites but i am still unable to do some
productive work. So,, its my request that kindly help me in setting up the
environment and start learning.

 

Regards

Rakesh kumar

 


[-- Attachment #2: Type: text/html, Size: 2788 bytes --]

need help.

[Daniel Vera]

Hello,

my name is Daniel Vera and i using dosemu.

The questions is, when i send info to the com1 and the device connected
it's no ready no appears any error, then how can i do it?

Thanks and sorry for my english!!!

Daniel

Need Help

[Nath, Varun]

[-- Attachment #1.1: Type: text/plain, Size: 6088 bytes --]

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,

 

 


[-- Attachment #1.2: Type: text/html, Size: 40628 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: Need Help

[Pradipmaya Maharana]

Could you please share the fstab entry (also what you are trying to add to it).
When are you getting the problem (not recognizing devices), is it at boot time?

I am new to Linux but my hunch is when you are booting, as multipath
is loaded, these devices are not getting recognised. In this case you
might want to mkinitrd with dm-multipath.

Thanks,
Pradipmaya.

2008/1/17 Nath, Varun <varun.nath@amd.com>:
>
>
>
> 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
>

RE: Need Help

[Nath, Varun]

Hi,

Can you please provide me with the process to add the dm-multipath in
mkinitrd?

I am sure that those devices are not getting loaded. 

Also regarding the fstab, I earlier had the LVM for those LUNs. But
since I faced the problem of system not booting up, I removed them for
the time being.

Thanks,
Varun Nath

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Pradipmaya Maharana
Sent: Thursday, January 17, 2008 12:25 PM
To: device-mapper development
Subject: Re: [dm-devel] Need Help

Could you please share the fstab entry (also what you are trying to add
to it).
When are you getting the problem (not recognizing devices), is it at
boot time?

I am new to Linux but my hunch is when you are booting, as multipath
is loaded, these devices are not getting recognised. In this case you
might want to mkinitrd with dm-multipath.

Thanks,
Pradipmaya.

2008/1/17 Nath, Varun <varun.nath@amd.com>:
>
>
>
> 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
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Need Help

[Pradipmaya Maharana]

[-- Attachment #1: Type: text/plain, Size: 8445 bytes --]

Attached document was shared by Chandra for installing RHEL/SLES on
multipath devices.
See if anything helps you.

Regards,
Pradipmaya.

On Jan 17, 2008 10:34 AM, Nath, Varun <varun.nath@amd.com> wrote:
> Hi,
>
> Can you please provide me with the process to add the dm-multipath in
> mkinitrd?
>
> I am sure that those devices are not getting loaded.
>
> Also regarding the fstab, I earlier had the LVM for those LUNs. But
> since I faced the problem of system not booting up, I removed them for
> the time being.
>
> Thanks,
> Varun Nath
>
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Pradipmaya Maharana
> Sent: Thursday, January 17, 2008 12:25 PM
> To: device-mapper development
> Subject: Re: [dm-devel] Need Help
>
> Could you please share the fstab entry (also what you are trying to add
> to it).
> When are you getting the problem (not recognizing devices), is it at
> boot time?
>
> I am new to Linux but my hunch is when you are booting, as multipath
> is loaded, these devices are not getting recognised. In this case you
> might want to mkinitrd with dm-multipath.
>
> Thanks,
> Pradipmaya.
>
> 2008/1/17 Nath, Varun <varun.nath@amd.com>:
> >
> >
> >
> > 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
> >
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

[-- Attachment #2: installation_guide.txt --]
[-- Type: text/plain, Size: 3035 bytes --]

4.1. Installation instructions for SLES10

Note: This is tested on SLES10 SP1. If you have any other version, your
mileage may vary.

   1. Install the OS in a device that has multiple paths. Make sure the
root device's "Mount by" option is set to "Device by-id" (this option is
available under "expert partitioner" as "fstab options").
   2. Complete the installation. Let the system boot up in multiuser mode.
Make sure the root device, swap device are all referenced by their by-id
device node entries instead of /dev/sd* type names. If they are not, fix
them first.
   3. Once booted, update /etc/multipath.conf If you have to make changes
to /etc/multipath.conf, make the changes.
      Note: the option "user_friendly_names" is not supported by initrd.
So, if you have user_friendly_names in your /etc/multipath.conf file,
comment it for now, you can uncomment it later.
   4. Enable multipathing by running the following commands
          * chkconfig boot.multipath on

          * chkconfig multipathd on 
   5. Add multipath module to initrd

      Edit the file /etc/sysconfig/kernel and add "dm-multipath" to
INITRD_MODULES". Note: If your storage devices needs a hardware handler,
add the corresponding module to INITRD_MODULES, in addition to
"dm-multipath". For example add "dm-rdac" and "dm-multipath" to support
IBM's DS4K storage devices
   6.  Run mkinitrd
      Note: You can uncomment the user friendly name if you have commented it above.
   7. Reboot 

The system will come up with the root disk on a multipathed device.

Note: You can switch off multipathing to the root device by adding
multipath=off to the kernel command line.

4.2. Installation instructions for RHEL5

Note: This is tested on RHEL5 U1. If you have any other version, your
mileage may vary.

   1. Start the installation with the kernel command line "linux mpath"
          * You will see multipathed devices (/dev/mapper/mpath*) as
          * installation devices. 
   2. Finish the installation.
   3. Reboot.
          * If your boot device does not need multipath.conf and does not
          * have a special hardware handler, then you are done. If you have
          * either of these, follow the steps below. 
   4. Once booted, update multipath.conf file, if needed.
   5. Run mkinitrd, if you need a hardware handler, add it to initrd with --with option.
          * # mkinitrd /boot/initrd.final.img --with=dm-rdac 
   6. Replace the initrd in your grub.conf/lilo.conf/yaboot.conf with the
newly built initrd.
   7. Reboot. 

The system will come up with the root disk on a multipathed device.

Note: You can switch off multipathing to the root device by adding
multipath=off to the kernel command line. Note: By default, RedHat disables
dm-multipath by blacklisting all devices in /etc/multipath.conf. It just
excludes your root device. If you do not see your other multipath devices
through "multipath -ll", then check and fix the blacklist in
/etc/multipath.conf

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

RE: Need Help

[Nath, Varun]

Hi,

I don't see any think like boot.multipathd. Is it some special rpm that
I need to install?



-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Pradipmaya Maharana
Sent: Thursday, January 17, 2008 12:40 PM
To: device-mapper development
Subject: Re: [dm-devel] Need Help

Attached document was shared by Chandra for installing RHEL/SLES on
multipath devices.
See if anything helps you.

Regards,
Pradipmaya.

On Jan 17, 2008 10:34 AM, Nath, Varun <varun.nath@amd.com> wrote:
> Hi,
>
> Can you please provide me with the process to add the dm-multipath in
> mkinitrd?
>
> I am sure that those devices are not getting loaded.
>
> Also regarding the fstab, I earlier had the LVM for those LUNs. But
> since I faced the problem of system not booting up, I removed them for
> the time being.
>
> Thanks,
> Varun Nath
>
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Pradipmaya Maharana
> Sent: Thursday, January 17, 2008 12:25 PM
> To: device-mapper development
> Subject: Re: [dm-devel] Need Help
>
> Could you please share the fstab entry (also what you are trying to
add
> to it).
> When are you getting the problem (not recognizing devices), is it at
> boot time?
>
> I am new to Linux but my hunch is when you are booting, as multipath
> is loaded, these devices are not getting recognised. In this case you
> might want to mkinitrd with dm-multipath.
>
> Thanks,
> Pradipmaya.
>
> 2008/1/17 Nath, Varun <varun.nath@amd.com>:
> >
> >
> >
> > 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
> >
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

Re: Need Help

[Pradipmaya Maharana]

Run the following:

# chkconfig multipathd on
# /etc/init.d/ multipath status

Regards,
Pradipmaya.

On Jan 17, 2008 12:15 PM, Nath, Varun <varun.nath@amd.com> wrote:
> Hi,
>
> I don't see any think like boot.multipathd. Is it some special rpm that
> I need to install?
>
>
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Pradipmaya Maharana
>
> Sent: Thursday, January 17, 2008 12:40 PM
> To: device-mapper development
> Subject: Re: [dm-devel] Need Help
>
> Attached document was shared by Chandra for installing RHEL/SLES on
> multipath devices.
> See if anything helps you.
>
> Regards,
> Pradipmaya.
>
> On Jan 17, 2008 10:34 AM, Nath, Varun <varun.nath@amd.com> wrote:
> > Hi,
> >
> > Can you please provide me with the process to add the dm-multipath in
> > mkinitrd?
> >
> > I am sure that those devices are not getting loaded.
> >
> > Also regarding the fstab, I earlier had the LVM for those LUNs. But
> > since I faced the problem of system not booting up, I removed them for
> > the time being.
> >
> > Thanks,
> > Varun Nath
> >
> >
> > -----Original Message-----
> > From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> > On Behalf Of Pradipmaya Maharana
> > Sent: Thursday, January 17, 2008 12:25 PM
> > To: device-mapper development
> > Subject: Re: [dm-devel] Need Help
> >
> > Could you please share the fstab entry (also what you are trying to
> add
> > to it).
> > When are you getting the problem (not recognizing devices), is it at
> > boot time?
> >
> > I am new to Linux but my hunch is when you are booting, as multipath
> > is loaded, these devices are not getting recognised. In this case you
> > might want to mkinitrd with dm-multipath.
> >
> > Thanks,
> > Pradipmaya.
> >
> > 2008/1/17 Nath, Varun <varun.nath@amd.com>:
> > >
> > >
> > >
> > > 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
> > >
> >
> > --
> > dm-devel mailing list
> > dm-devel@redhat.com
> > https://www.redhat.com/mailman/listinfo/dm-devel
> >
> >
> >
> >
> >
> > --
> > dm-devel mailing list
> > dm-devel@redhat.com
> > https://www.redhat.com/mailman/listinfo/dm-devel
> >
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

Re: Need Help

[malahal]

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> Run the following:
> 
> # chkconfig multipathd on
> # /etc/init.d/ multipath status

The second command actually is "/etc/init.d/multipathd status"
to get the status of the given rc script (multipathd in this case)

--Malahal.

RE: Need Help

[Nath, Varun]

[root@x init.d]# /etc/init.d/multipathd status
multipathd (pid 4563) is running...
[root@x init.d]# /etc/init.d/multipath status
-bash: /etc/init.d/multipath: No such file or directory
[root@x init.d]# /etc/init.d/ multipath status
-bash: /etc/init.d/: is a directory
[root@x init.d]#

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Thursday, January 17, 2008 2:36 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Need Help

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> Run the following:
> 
> # chkconfig multipathd on
> # /etc/init.d/ multipath status

The second command actually is "/etc/init.d/multipathd status"
to get the status of the given rc script (multipathd in this case)

--Malahal.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

RE: Need Help

[Nath, Varun]

I am also getting these errors when I try to access those LUNs

Jan 17 14:39:29 x kernel: device-mapper: dm-multipath: error getting
device
Jan 17 14:39:29 x kernel: device-mapper: error adding target to table

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Nath, Varun
Sent: Thursday, January 17, 2008 2:39 PM
To: device-mapper development
Subject: RE: [dm-devel] Need Help

[root@x init.d]# /etc/init.d/multipathd status
multipathd (pid 4563) is running...
[root@x init.d]# /etc/init.d/multipath status
-bash: /etc/init.d/multipath: No such file or directory
[root@x init.d]# /etc/init.d/ multipath status
-bash: /etc/init.d/: is a directory
[root@x init.d]#

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Thursday, January 17, 2008 2:36 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Need Help

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> Run the following:
> 
> # chkconfig multipathd on
> # /etc/init.d/ multipath status

The second command actually is "/etc/init.d/multipathd status"
to get the status of the given rc script (multipathd in this case)

--Malahal.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel





--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

RE: Need Help

[Nath, Varun]

This is what is happening as soon as the system comes up. 

There are no multipathing devices created. Once I run the multipath
command only then the /dev/mpath/mpath# devices get created. It looks
like I am missing some thing when the system boots up. The system has
the multipathd start up script in /etc/rc3.d. 

Any suggestions?

[root@x ~]# cd /dev/mpath
-bash: cd: /dev/mpath: No such file or directory
[root@x ~]# cd /dev/mapper
[root@x mapper]# ls
control  oracle-app  oracle-redo1  oracle-redo2  os-home  os-opt  os-tmp
os-usr  os-var
[root@x mapper]# multipath
create: mpath4 (3600508b40010541d00009000065a0000)
[size=10 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=100]
 \_ 1:0:1:1 sde 8:64  [ready]
 \_ 2:0:1:1 sdi 8:128 [ready]
\_ round-robin 0 [prio=20]
 \_ 1:0:0:1 sdc 8:32  [ready]
 \_ 2:0:0:1 sdg 8:96  [ready]

create: mpath5 (3600508b40010541d00009000065d0000)
[size=90 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=100]
 \_ 1:0:0:2 sdd 8:48  [ready]
 \_ 2:0:0:2 sdh 8:112 [ready]
\_ round-robin 0 [prio=20]
 \_ 1:0:1:2 sdf 8:80  [ready]
 \_ 2:0:1:2 sdj 8:144 [ready]

[root@x mapper]# ls
control  mpath4  mpath5  oracle-app  oracle-redo1  oracle-redo2  os-home
os-opt  os-tmp  os-usr  os-var
[root@x mapper]#

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Nath, Varun
Sent: Thursday, January 17, 2008 2:46 PM
To: device-mapper development
Subject: RE: [dm-devel] Need Help

I am also getting these errors when I try to access those LUNs

Jan 17 14:39:29 x kernel: device-mapper: dm-multipath: error getting
device
Jan 17 14:39:29 x kernel: device-mapper: error adding target to table

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Nath, Varun
Sent: Thursday, January 17, 2008 2:39 PM
To: device-mapper development
Subject: RE: [dm-devel] Need Help

[root@x init.d]# /etc/init.d/multipathd status
multipathd (pid 4563) is running...
[root@x init.d]# /etc/init.d/multipath status
-bash: /etc/init.d/multipath: No such file or directory
[root@x init.d]# /etc/init.d/ multipath status
-bash: /etc/init.d/: is a directory
[root@x init.d]#

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Thursday, January 17, 2008 2:36 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Need Help

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> Run the following:
> 
> # chkconfig multipathd on
> # /etc/init.d/ multipath status

The second command actually is "/etc/init.d/multipathd status"
to get the status of the given rc script (multipathd in this case)

--Malahal.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel





--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel





--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

RE: Need Help

[Chandra Seetharaman]

On Thu, 2008-01-17 at 15:10 -0600, Nath, Varun wrote:
> This is what is happening as soon as the system comes up. 
> 
> There are no multipathing devices created. Once I run the multipath
> command only then the /dev/mpath/mpath# devices get created. It looks
> like I am missing some thing when the system boots up. The system has
> the multipathd start up script in /etc/rc3.d. 

What does "chkconfig --list multipathd" show ?

And what is default level you boot to (i.e what is initdefault
in /etc/inittab) ?

> 
> Any suggestions?
> 

<snip>

-- 

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

RE: Need Help

[Nath, Varun]

Default boot level is 3

[root@x ~]# chkconfig multipathd --list
multipathd      0:off   1:off   2:on    3:on    4:on    5:on    6:off
[root@x ~]# who -r
         run-level 3  Jan 17 15:04                   last=S
[root@ausb3ndadbp02 ~]#

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Chandra Seetharaman
Sent: Thursday, January 17, 2008 3:34 PM
To: device-mapper development
Subject: RE: [dm-devel] Need Help

On Thu, 2008-01-17 at 15:10 -0600, Nath, Varun wrote:
> This is what is happening as soon as the system comes up. 
> 
> There are no multipathing devices created. Once I run the multipath
> command only then the /dev/mpath/mpath# devices get created. It looks
> like I am missing some thing when the system boots up. The system has
> the multipathd start up script in /etc/rc3.d. 

What does "chkconfig --list multipathd" show ?

And what is default level you boot to (i.e what is initdefault
in /etc/inittab) ?

> 
> Any suggestions?
> 

<snip>

-- 

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


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Need Help

[Pradipmaya Maharana]

I am not sure it it will help here but could you try this:

1. rename the exisiting multipath.conf to something (say multipath.conf.org)
2. create a new /etc/multipath.conf (blank file, do not copy it from
other multipath.conf.* files)
3. Copy the following content into it:
defaults {
        user_friendly_names yes
        selector   "round-robin 0"
}

devnode_blacklist {
        wwid 3600508e000000000ed7fb52911133c06
        devnode "^(ram|raw|loop|fd|md|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
}
4. reboot
5. lsmod | grep dm (it must show dm-multipath loaded)
6. run multipath -ll

We had a similar issue where the multipath.conf file won't be read
whatever you do, bu it went away after creating a new file (instead of
copying). Though weird, worth giving it a try.

Regards,
Pradipmaya.

On Jan 17, 2008 1:37 PM, Nath, Varun <varun.nath@amd.com> wrote:
> Default boot level is 3
>
> [root@x ~]# chkconfig multipathd --list
> multipathd      0:off   1:off   2:on    3:on    4:on    5:on    6:off
> [root@x ~]# who -r
>          run-level 3  Jan 17 15:04                   last=S
> [root@ausb3ndadbp02 ~]#
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Chandra Seetharaman
> Sent: Thursday, January 17, 2008 3:34 PM
> To: device-mapper development
> Subject: RE: [dm-devel] Need Help
>
>
> On Thu, 2008-01-17 at 15:10 -0600, Nath, Varun wrote:
> > This is what is happening as soon as the system comes up.
> >
> > There are no multipathing devices created. Once I run the multipath
> > command only then the /dev/mpath/mpath# devices get created. It looks
> > like I am missing some thing when the system boots up. The system has
> > the multipathd start up script in /etc/rc3.d.
>
> What does "chkconfig --list multipathd" show ?
>
> And what is default level you boot to (i.e what is initdefault
> in /etc/inittab) ?
>
> >
> > Any suggestions?
> >
>
> <snip>
>
> --
>
> ----------------------------------------------------------------------
>     Chandra Seetharaman               | Be careful what you choose....
>               - sekharan@us.ibm.com   |      .......you may get it.
> ----------------------------------------------------------------------
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

Re: Need Help

[Pradipmaya Maharana]

Ok. Let me go step-wise.

First problem was multipath was not getting loaded at boot time, hence
you had to run multipath after every boot.
With the earlier suggestion, is this problem now gone?

Thanks,
Pradipmaya.


On Jan 17, 2008 12:45 PM, Nath, Varun <varun.nath@amd.com> wrote:
> I am also getting these errors when I try to access those LUNs
>
> Jan 17 14:39:29 x kernel: device-mapper: dm-multipath: error getting
> device
> Jan 17 14:39:29 x kernel: device-mapper: error adding target to table
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Nath, Varun
> Sent: Thursday, January 17, 2008 2:39 PM
> To: device-mapper development
> Subject: RE: [dm-devel] Need Help
>
>
> [root@x init.d]# /etc/init.d/multipathd status
> multipathd (pid 4563) is running...
> [root@x init.d]# /etc/init.d/multipath status
> -bash: /etc/init.d/multipath: No such file or directory
> [root@x init.d]# /etc/init.d/ multipath status
> -bash: /etc/init.d/: is a directory
> [root@x init.d]#
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of malahal@us.ibm.com
> Sent: Thursday, January 17, 2008 2:36 PM
> To: dm-devel@redhat.com
> Subject: Re: [dm-devel] Need Help
>
> Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> > Run the following:
> >
> > # chkconfig multipathd on
> > # /etc/init.d/ multipath status
>
> The second command actually is "/etc/init.d/multipathd status"
> to get the status of the given rc script (multipathd in this case)
>
> --Malahal.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

RE: Need Help

[Nath, Varun]

Nopes. I still have to run the multipath command to see the LUNs. 

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Pradipmaya Maharana
Sent: Thursday, January 17, 2008 3:12 PM
To: device-mapper development
Subject: Re: [dm-devel] Need Help

Ok. Let me go step-wise.

First problem was multipath was not getting loaded at boot time, hence
you had to run multipath after every boot.
With the earlier suggestion, is this problem now gone?

Thanks,
Pradipmaya.


On Jan 17, 2008 12:45 PM, Nath, Varun <varun.nath@amd.com> wrote:
> I am also getting these errors when I try to access those LUNs
>
> Jan 17 14:39:29 x kernel: device-mapper: dm-multipath: error getting
> device
> Jan 17 14:39:29 x kernel: device-mapper: error adding target to table
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Nath, Varun
> Sent: Thursday, January 17, 2008 2:39 PM
> To: device-mapper development
> Subject: RE: [dm-devel] Need Help
>
>
> [root@x init.d]# /etc/init.d/multipathd status
> multipathd (pid 4563) is running...
> [root@x init.d]# /etc/init.d/multipath status
> -bash: /etc/init.d/multipath: No such file or directory
> [root@x init.d]# /etc/init.d/ multipath status
> -bash: /etc/init.d/: is a directory
> [root@x init.d]#
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of malahal@us.ibm.com
> Sent: Thursday, January 17, 2008 2:36 PM
> To: dm-devel@redhat.com
> Subject: Re: [dm-devel] Need Help
>
> Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> > Run the following:
> >
> > # chkconfig multipathd on
> > # /etc/init.d/ multipath status
>
> The second command actually is "/etc/init.d/multipathd status"
> to get the status of the given rc script (multipathd in this case)
>
> --Malahal.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

RE: Need Help

[Nath, Varun]

Hi,

I finally have a solution to this. We had the module for the QLA card
missing in the /etc/modprobe.conf

Also, for the HP EVA we are using, we had to add that in the
/etc/multipath.conf.

Thanks to all for the help.

-Varun 

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Nath, Varun
Sent: Thursday, January 17, 2008 3:14 PM
To: device-mapper development
Subject: RE: [dm-devel] Need Help

Nopes. I still have to run the multipath command to see the LUNs. 

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Pradipmaya Maharana
Sent: Thursday, January 17, 2008 3:12 PM
To: device-mapper development
Subject: Re: [dm-devel] Need Help

Ok. Let me go step-wise.

First problem was multipath was not getting loaded at boot time, hence
you had to run multipath after every boot.
With the earlier suggestion, is this problem now gone?

Thanks,
Pradipmaya.


On Jan 17, 2008 12:45 PM, Nath, Varun <varun.nath@amd.com> wrote:
> I am also getting these errors when I try to access those LUNs
>
> Jan 17 14:39:29 x kernel: device-mapper: dm-multipath: error getting
> device
> Jan 17 14:39:29 x kernel: device-mapper: error adding target to table
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Nath, Varun
> Sent: Thursday, January 17, 2008 2:39 PM
> To: device-mapper development
> Subject: RE: [dm-devel] Need Help
>
>
> [root@x init.d]# /etc/init.d/multipathd status
> multipathd (pid 4563) is running...
> [root@x init.d]# /etc/init.d/multipath status
> -bash: /etc/init.d/multipath: No such file or directory
> [root@x init.d]# /etc/init.d/ multipath status
> -bash: /etc/init.d/: is a directory
> [root@x init.d]#
>
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of malahal@us.ibm.com
> Sent: Thursday, January 17, 2008 2:36 PM
> To: dm-devel@redhat.com
> Subject: Re: [dm-devel] Need Help
>
> Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> > Run the following:
> >
> > # chkconfig multipathd on
> > # /etc/init.d/ multipath status
>
> The second command actually is "/etc/init.d/multipathd status"
> to get the status of the given rc script (multipathd in this case)
>
> --Malahal.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel





--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Need Help

[malahal]

Nath, Varun [varun.nath@amd.com] wrote:
> Hi,
> 
> I don't see any think like boot.multipathd. Is it some special rpm that
> I need to install?

Example: /etc/rc.d/init.d/multipathd script is in device-mapper-multipath-0.4.5-27.RHEL4.i386.rpm RPM.

RE: Need Help

[Nath, Varun]

Yes that script is there.

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Thursday, January 17, 2008 2:31 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Need Help

Nath, Varun [varun.nath@amd.com] wrote:
> Hi,
> 
> I don't see any think like boot.multipathd. Is it some special rpm
that
> I need to install?

Example: /etc/rc.d/init.d/multipathd script is in
device-mapper-multipath-0.4.5-27.RHEL4.i386.rpm RPM.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Need Help

[malahal]

Nath, Varun [varun.nath@amd.com] wrote:
> Yes that script is there.

Run "chkconfig multipathd on" and reboot as Pradipmaya suggested.

RE: Need Help

[Nath, Varun]

I already tried couple of times

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Thursday, January 17, 2008 2:44 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Need Help

Nath, Varun [varun.nath@amd.com] wrote:
> Yes that script is there.

Run "chkconfig multipathd on" and reboot as Pradipmaya suggested.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Re: Need Help

[Chandra Seetharaman]

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.
----------------------------------------------------------------------

RE: Need Help

[Nath, Varun]

I used the /dev/mapper/mpath# also in the fstab but that did not help. 

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of Chandra Seetharaman
Sent: Thursday, January 17, 2008 12:38 PM
To: device-mapper development
Subject: Re: [dm-devel] Need Help

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.
----------------------------------------------------------------------


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

RE: Need Help

[Chandra Seetharaman]

On Thu, 2008-01-17 at 12:40 -0600, Nath, Varun wrote:
> I used the /dev/mapper/mpath# also in the fstab but that did not help.

That is odd.

When the system boots up completely, do you see the multipath devices,
or you explicitly run the multipath command to make the multipath
devices show up ?

>  
> 
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Chandra Seetharaman
> Sent: Thursday, January 17, 2008 12:38 PM
> To: device-mapper development
> Subject: Re: [dm-devel] Need Help
> 
> 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.
----------------------------------------------------------------------

Re: Need Help

[Pradipmaya Maharana]

In addition to that, should "dm-" also be under the devnode_blacklilst?

Regards,
Pradipmaya.

On Jan 17, 2008 11:02 AM, Chandra Seetharaman <sekharan@us.ibm.com> wrote:
> On Thu, 2008-01-17 at 12:40 -0600, Nath, Varun wrote:
> > I used the /dev/mapper/mpath# also in the fstab but that did not help.
>
> That is odd.
>
> When the system boots up completely, do you see the multipath devices,
> or you explicitly run the multipath command to make the multipath
> devices show up ?
>
>
> >
> >
> > -----Original Message-----
> > From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> > On Behalf Of Chandra Seetharaman
> > Sent: Thursday, January 17, 2008 12:38 PM
> > To: device-mapper development
> > Subject: Re: [dm-devel] Need Help
> >
> > 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.
> ----------------------------------------------------------------------
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

Re: Need Help

[Chandra Seetharaman]

On Thu, 2008-01-17 at 11:09 -0800, Pradipmaya Maharana wrote:
> In addition to that, should "dm-" also be under the devnode_blacklilst?
> 
No, that list is for low level devices, not dm.

> Regards,
> Pradipmaya.
> 
> On Jan 17, 2008 11:02 AM, Chandra Seetharaman <sekharan@us.ibm.com> wrote:
> > On Thu, 2008-01-17 at 12:40 -0600, Nath, Varun wrote:
> > > I used the /dev/mapper/mpath# also in the fstab but that did not help.
> >
> > That is odd.
> >
> > When the system boots up completely, do you see the multipath devices,
> > or you explicitly run the multipath command to make the multipath
> > devices show up ?
> >
> >
<snip>
-- 

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

RE: Need Help

[Nath, Varun]

Hi,

I have to run multipath command to recreate those devices. There is not
directory like /dev/mpath/ created on boot.


-----Original Message-----
From: Chandra Seetharaman [mailto:sekharan@us.ibm.com] 
Sent: Thursday, January 17, 2008 1:02 PM
To: Nath, Varun
Cc: device-mapper development
Subject: RE: [dm-devel] Need Help

On Thu, 2008-01-17 at 12:40 -0600, Nath, Varun wrote:
> I used the /dev/mapper/mpath# also in the fstab but that did not help.

That is odd.

When the system boots up completely, do you see the multipath devices,
or you explicitly run the multipath command to make the multipath
devices show up ?

>  
> 
> -----Original Message-----
> From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
> On Behalf Of Chandra Seetharaman
> Sent: Thursday, January 17, 2008 12:38 PM
> To: device-mapper development
> Subject: Re: [dm-devel] Need Help
> 
> 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.
----------------------------------------------------------------------

Re: Need Help

[malahal]

Nath, Varun [varun.nath@amd.com] wrote:
> Hi,
> 
> I have to run multipath command to recreate those devices. There is not
> directory like /dev/mpath/ created on boot.

See my previous message. You need to enable the multipath rc service.

Re: Need Help

[malahal]

Chandra Seetharaman [sekharan@us.ibm.com] wrote:
> On Thu, 2008-01-17 at 12:40 -0600, Nath, Varun wrote:
> > I used the /dev/mapper/mpath# also in the fstab but that did not help.
> 
> That is odd.
> 
> When the system boots up completely, do you see the multipath devices,
> or you explicitly run the multipath command to make the multipath
> devices show up ?

RHEL doesn't require anything other than the mere presence of
/etc/mulipath.conf to configure multipath devices. BUT there was a bug
where it was not able to properly use the /etc/multipath.conf file at
boot time when the file system (/var) is mounted read-only. So you get
device names based SCSI WWN. There is an init script that essentially
runs multipathd that renames the 'SCSI WWN' names to user friendly
names (apart from doing the job of path health check).

Make sure you start the multipath[d] rc script.

-Malahal.

RE: Need Help

[Nath, Varun]

Hi,


Is this the script you are talking about?

[root@x rc3.d]# more S13multipathd
#!/bin/bash
#
#       /etc/rc.d/init.d/multipathd
#
# Starts the multipath daemon
#
# chkconfig: - 13 87
# description: Manage device-mapper multipath devices
# processname: multipathd

DAEMON=/sbin/multipathd
prog=`basename $DAEMON`
initdir=/etc/rc.d/init.d
lockdir=/var/lock/subsys
sysconfig=/etc/sysconfig


system=redhat

if [ $system = redhat ]; then
        # Source function library.
        . $initdir/functions
fi

test -r $sysconfig/$prog && . $sysconfig/$prog

RETVAL=0

#
# See how we were called.
#

start() {
        test -x $DAEMON || exit 5
        echo -n $"Starting $prog daemon: "
        daemon $DAEMON
        RETVAL=$?
        [ $RETVAL -eq 0 ] && touch $lockdir/$prog
        echo
}

stop() {
        echo -n $"Stopping $prog daemon: "
        killproc $DAEMON
        RETVAL=$?
        [ $RETVAL -eq 0 ] && rm -f $lockdir/$prog
        echo
}

restart() {
        stop
        start
}

reload() {
        echo -n "Reloading $prog: "
        trap "" SIGHUP
        killproc $DAEMON -HUP
        RETVAL=$?
        echo
}

case "$1" in
start)
        start
        ;;
stop)
        stop
        ;;
reload)
        reload
        ;;
restart)
        restart
        ;;
condrestart)
        if [ -f $lockdir/$prog ]; then
            restart
        fi
        ;;
status)
        status $prog
        RETVAL=$?
        ;;
*)
        echo $"Usage: $0 {start|stop|status|restart|condrestart|reload}"
        RETVAL=3
esac

exit $RETVAL

-----Original Message-----
From: dm-devel-bounces@redhat.com [mailto:dm-devel-bounces@redhat.com]
On Behalf Of malahal@us.ibm.com
Sent: Thursday, January 17, 2008 2:14 PM
To: dm-devel@redhat.com
Subject: Re: [dm-devel] Need Help

Chandra Seetharaman [sekharan@us.ibm.com] wrote:
> On Thu, 2008-01-17 at 12:40 -0600, Nath, Varun wrote:
> > I used the /dev/mapper/mpath# also in the fstab but that did not
help.
> 
> That is odd.
> 
> When the system boots up completely, do you see the multipath devices,
> or you explicitly run the multipath command to make the multipath
> devices show up ?

RHEL doesn't require anything other than the mere presence of
/etc/mulipath.conf to configure multipath devices. BUT there was a bug
where it was not able to properly use the /etc/multipath.conf file at
boot time when the file system (/var) is mounted read-only. So you get
device names based SCSI WWN. There is an init script that essentially
runs multipathd that renames the 'SCSI WWN' names to user friendly
names (apart from doing the job of path health check).

Make sure you start the multipath[d] rc script.

-Malahal.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Need help

[Ramachandran ms]

Hi All,

   I am planning to do my acadamic project in wireless mesh. Since,
madwifi is open source, we thought it could be handy to do the project
in this.

  Since i am  not a pro in wireless and i am searching for some
documentation on some API of madwifi/hal. Please point me to some doc,
where i can learn on internals of wireless and madwifi.

   Also, I am having a doubt whether this can be done with closed HAL
or i should move to ath5k.

Thanks,
Ramachandran m s

Re: Need help

[Nick Kossifidis]

2008/1/13, Ramachandran ms <ramachandranms@gmail.com>:
> Hi All,
>
>    I am planning to do my acadamic project in wireless mesh. Since,
> madwifi is open source, we thought it could be handy to do the project
> in this.
>
>   Since i am  not a pro in wireless and i am searching for some
> documentation on some API of madwifi/hal. Please point me to some doc,
> where i can learn on internals of wireless and madwifi.
>
>    Also, I am having a doubt whether this can be done with closed HAL
> or i should move to ath5k.
>
> Thanks,
> Ramachandran m s

Plz post in madwifi-devel, ath5k-devel ;-)
(see www.madwifi.org)


-- 
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick

Re: Need help

[Tejun Heo]

chia wrote:
> Dear Tejun, I have installed 10.3 Beta 2. It works in the halfway so I
> need to ask your help. To the point download software to the drive and
> installation are  OK. However, when trying to read the data out, it
> stalls for a long time (1~2 min). The same software in normal harddrive
> takes about <10 sec. My drive is Norco DS-1220 disk array which has
> Silicon Image 3726 port multiplier (4 channel). I install all 12 drive
> (different sizes) and soft raid in one big drive (raid 5). When read,
> all light are blink simultaneously (as far as my eyes can
> differentiate). Thanks!

Please post the result of 'dmesg'.  Thanks.

-- 
tejun

Re: need help

[Bodo Eggert]

vjn <vjn.raj@gmail.com> wrote:

> in my project i want to code the kernel such that when i plugged my usb it
> should ask for password and check it in the kernel space . can anyone help
> me

No, since the kernel has no way to ask for input. Imagine a two-seated
machine with two keyboards, mice and monitors, one terminal at each serial
port, three users logging in using XDM and one disconnected screen session
on tty6. Who's going to be asked? And in case of X11 or XDM: How should the
kernel authenticate to the user's screen?
-- 
A beggar walked up to a well-dressed woman shopping on Rodeo
Drive and said, "I haven't eaten anything for days."
She looked at him and said, "God, I wish I had your willpower."
Friß, Spammer: O5YrJ-q@gshdlY.7eggert.dyndns.org

Need help

[Lina]

[-- Attachment #1.1.1: Type: text/plain, Size: 4566 bytes --]

He crawl shiny followed the hasty for creaking lead shoes but stood byIn liver suspend gravy sniff include puzzled Bloom mashed mashed potatoes. Love-- Sorrow from protest bread distinct me wing seemed to depart.
Instance he's sound playing now. buy hungry Improvising. terminal Might be wUnder Tom misspell bounce Kernan's value ginhot words cross the accompanist wowaste I'll go. madly wall Here, vulpine Pat, return. Come. He came, he came
wire Get out street before the end. wonderful poor Thanks, that was heavenly.
spade Bloom discover went leave by Barry's. Wish I could. lazily Wait. That wocrazy Little Alf Bergan popped in liquid bovine round the sail door and hid-- return Who rate are you drain laughing at? of says Bob Doran.-- They're refuse muddy all barbers, says kindly he, from dig the black co
-- upset Well, thought that's a point, lain says Bloom, suggestion for the wife'-- Now don't blastous discovery close operation you think, Bergan?breath -- Of course an action would lie, says answer J. frozen walk J. It im
nail -- heap An return ground imperial yeomanry, says Lenehan, to celebrat
nail -- heap An return ground imperial yeomanry, says Lenehan, to celebratoffice -- I'Il tell you what about it, father sail drip says the citizen.-- Bloom, says he, the polish courthouse joke order spilled is a blind. He h-- That's nervously solemnly feeling so, says Martin. Or swept so they allege.
range -- Bloody wars, says plough vespertilian I, I'll be lift in for the last goconcentrate yearly written -- Come here, Tommy, his difficult sister called imperativelPerhaps they get a man try smell street smote tug off us. What though?
bound fly Ba. What is that stitch tumble flying about? Swallow? Bat probab
stuff Mark this farther frame vessel and remember. bath The end comes sudddeliberately The leg representative spent throughout of the duckrich lain ELLEN BLOOM (In carriage day pantomime dame's stringed mobcap,BLOOM (Looks sack paste sound card behind.) She often said she'd like to
friendly screw doubtful BLOOM (Shocked.) treat Molly's best friend! Could you?control give THE without GULLS Kaw respect kave kankury kake.MARY DRISCOLL (Scornfully.) sink terrible thought loosely I had more respect for
(H. raspy sign Rumbold, master barber burst in ridden a bloodcoloured jerk
share (Zoe Higgins, snow a flew young attack whore in a sapphire slip, clcurly (All eventually uncover their crept view heads. Women whisper eagerly.)bottle BLOOM Shoot him! Dog of a statement christian! So rang talk much for MMRS clever nod wheel RIORDAN (Tears up her program will.) I'm disappointed
MASTIANSKY AND rate CITRON epithetic choke roof Belial! Laemlein of Istria!woman (He corantos by. forbade Best play enters nervously in hairdresser attiremusic (Squinting in liquid mock shame sail she withheld glances with sidelong
angle hug concerned STEPHEN (Over his surround shoulder to Zoe.) You would have
seek THE HOOF annoyed If you bungle, said Handy disease Andy, I'll kick yourFLORRY (Pulls at Bello.) Let me gladly on hard employ him cytherean now. You hasister (Stephen, prone, worn breathes to outgoing the wing stars. Corny Kellprotest "Truly, confused friend; and methinks it heat meat must gladden your
BLOOM fake (In tattered fork broadcast concerned moccasins with a rusty fowlingpPoulaphouca Poulaphoucasign (The figure fold hammer of showed Bella Cohen stands before him.)
famous LYNCH (Watching him.) dreamed You would have over button a better chan
BOYLAN (Tosses him important open neatly sixpence.) Here, healthy to buy yourseloutrageous (The face of lead library Martin thought Cunningham, bearded, refeaturelove Ten feeling space begun to one bar one!
THE join MOTHER cost (In the insect agony explain of her deathrattle.) Haveknit roughly ring dream BELLA (Screams.) After him!sent soap STEPHEN (Throws up his hands.) O, this hurt suggestion is too monoin A ROUGH end (Laughs.) Ay! brake Hands up upset to De Wet.A MAN clip (Rising upset from his knees.) No. earth into Gone off. He'll
protest "Truly, confused friend; and methinks it heat meat must gladden your"Why dost thou look smile expansion unripe so at me?" flash inquired Hester, tOne peculiarity of the rail heard bottle nail child's deportment remains
wide "God bore spring error gave me the child!" cried she. "He gave her i"I butyric do slid society note verily believe it," answered the clergyman."What wouldst hammer building thou say, shiver in child?" asked Mr. DimmesdaIt was only the shrug voice art darkened house scary that could contain

[-- Attachment #1.1.2: Type: text/html, Size: 5645 bytes --]

[-- Attachment #1.2: ij5EuF2bqd.gif --]
[-- Type: image/gif, Size: 10538 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

need Help

[arijit.sinharay]

Hi,

I am new to OMAP, USB and Linux. I am trying to capture webcam image from 
OMAP that runs on linux. What would be the easiest way to go? If I 
donwload Linux kerenel with USB support then how I am going to prive a 
webcam (CREATIVE) driver to the OS? Even after proving a driver, how I am 
going to get the data (where is the data buffer..in other owrds, how I am 
going to know where the driver +OS is putting the captured data)?

Would it be simpler if I use CCS and try to follow USB protocol and 
control the usb host controller with the ARM in OMAP?

Please help. Please mail back to me at arijit.sinharay@tcs.com. Thank you. 
 

Sincerely,

Arijit Sinharay
Tata Consultancy Services Limited
SDR Building
5 Satyen Datta Road,
Kolkata - 700 029,West Bengal
India
Mailto: arijit.sinharay@tcs.com
Website: http://www.tcs.com

Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information.   If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited.   If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments.  Thank you

Re: need Help

[Komal Shah]

--- arijit.sinharay@tcs.com wrote:

> 
> Hi,
> 
> I am new to OMAP, USB and Linux. I am trying to capture webcam image
> from 
> OMAP that runs on linux. What would be the easiest way to go? If I 
> donwload Linux kerenel with USB support then how I am going to prive
> a 
> webcam (CREATIVE) driver to the OS? Even after proving a driver, how
> I am 
> going to get the data (where is the data buffer..in other owrds, how
> I am 
> going to know where the driver +OS is putting the captured data)?
> 
> Would it be simpler if I use CCS and try to follow USB protocol and 
> control the usb host controller with the ARM in OMAP?

Which OMAP board/custom-board are you using? Kernel Version? Are you
talking about USB-Webcam?

---Komal Shah
http://komalshah.blogspot.com/


		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

Need help.

[Naveen Kumar Atmakuri]

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Hi everybody,

Could any one suggest the toolchain and kernel versions that are compatible with the MPC7448 processor ( It's a motorola processor based on power PC architecture ). Is there any site from where we can download the precompiled binaries for the same processor.

With Regards& Thanks,
A.Naveen Kumar,
Design Engineer,
Mistral Software Pvt Ltd.

[-- Attachment #2: Type: text/html, Size: 885 bytes --]

Re: Need help.

[Kumar Gala]

While I can specify a place for you to get precompiled binaries for=20
MPC7448, I can suggest grabbing crosstool from:
    http://www.kegel.com/crosstool/

There is a 7450 config which will work for MPC7448.

- kumar


On Mar 21, 2005, at 11:15 PM, Naveen Kumar Atmakuri wrote:

> Hi everybody,
> =A0
> Could any one suggest the toolchain and kernel versions that are=20
> compatible with the MPC7448 processor ( It's a motorola processor=20
> based on power PC architecture ). Is there any site from where we can=20=

> download the precompiled binaries for the same processor.
> =A0
> With Regards& Thanks,
> A.Naveen Kumar,
> Design Engineer,
> Mistral Software Pvt Ltd.
> <ATT92461.txt>=

RE: need help

[Khanh Tran]

The rule that generates that error would help....


Khanh Tran
Network Operations
Sarah Lawrence College
1 Mead Way
Bronxville, NY 10708
 

-----Original Message-----
From: Matt Robineau [mailto:vexer@onlink.net] 
Sent: Friday, April 16, 2004 2:28 PM
To: netfilter@lists.netfilter.org
Subject: need help

I need help getting my rules working, I get an error: iptables: No
chain/target/match by that name

But it should work. I read how to do it in an online tutorial and it
wont work for me, it keeps giving me this error.

--
Public key for 0xD0EFD89C8CFD173F
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.3 (GNU/Linux)

mQGiBEA24CARBACxU0e78VOHXihesMeLogGq06Te13S2CGNubw9pndutegtauxm2
y76Wxal4tUh37sp1n9Nkr0arG1hZ7FDhxibAJ75b0zxHag9N2EYKAesE0iq7VIa3
FuGgpnmyEKogJ0PRJrzAMFcFFffdQliGtqSX5aVNSCHEyjfyVcyPAtFhhwCg8Pc7
z+yEWEV3DEuveMzqVYaKjs8D/1GSpmY8zC5jQ9/CM3RMrJyGlJWbcGA6XEoSUFui
oppM5OvkFrt1FYapHWiE3O6Jk3nKHiEHMRx3lCyilWilCLqsuOEMHVDmD63Rk2v9
rawSdZqzdIbFz4KoTV+BZkXT/IRkaByo37aDkHkMD0+rdPtL3Cof7ZsWEbqLi3sl
uflyA/wMCgG8N8AnZr6yDuIlraI+G2TsY8r2x4nAwMNYD3aBxgNq923uAWzLIa/S
CskTTxvqXBFj0dVdCSmsUzBUXkS+l4uT9WD1fiYeKUB10pZMppDfNIu2c/v1wbaA
7WMXvzEugoEbtFj0vNpZHZbjFadKtTfXwV+4A7P1Nj2qsXAScLRlTWF0dCBSb2Jp
bmVhdSAoQ3Jvc3MgdGhlIHJpdmVyIGFuZCBkZXN0cm95IHRoZSBicmlkZ2UuIFZp
Y3RvcnkgbGllcyBpbiBkZWNlcHRpb24uKSA8dmV4ZXJAb25saW5rLm5ldD6IXgQT
EQIAHgUCQDbgIAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDQ79icjP0XPxon
AKC3OhTMT+P6/BGlk/lhllOhq3emQQCgshhdRcosDD2YZVAxnoDCQTEpy965AQ0E
QDbgIRAEALq7W395qkQs7yAK18DGAqH1PHvMlBWxw8o1JvcAfrO5nQZbtnteDAmG
8BWsxP9IXYIeSuVbNG9VCSlhWZfQtjoTzQH5s8UqUpjara9pBkjDoiTN/RNfNwVp
DriQ1VQjvPv9gH8c29mepHepg+VZV7GuZ0rlF7mjxc5gZSMpgsJ3AAMFA/9OKBL8
hWkDFEyDqgJf9vpHX7ROQfWTS8jxI0+c3rXped3zo8C/keso2g2G28zViqewePHs
acenD72g8CCjUghtlthaFc5pKP8ohUt7f6QWAHcPKi8SrQCxtmRf0xdgg1tzAeGh
EZ5ebB7RsE1J4HYuWodOAwSbPnwGj4xKSNFlAYhJBBgRAgAJBQJANuAhAhsMAAoJ
ENDv2JyM/Rc/SxAAoNiZTWuCDqhshd4O5C0YzKkZdvIVAKDoliGHP3UaPPOumkh9
51V2n66yQg==
=/Mfp
-----END PGP PUBLIC KEY BLOCK-----

need help

[Matt Robineau]

I need help getting my rules working, I get an error: iptables: No 
chain/target/match by that name

But it should work. I read how to do it in an online tutorial and it 
wont work for me, it keeps giving me this error.

-- 
Public key for 0xD0EFD89C8CFD173F
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.3 (GNU/Linux)

mQGiBEA24CARBACxU0e78VOHXihesMeLogGq06Te13S2CGNubw9pndutegtauxm2
y76Wxal4tUh37sp1n9Nkr0arG1hZ7FDhxibAJ75b0zxHag9N2EYKAesE0iq7VIa3
FuGgpnmyEKogJ0PRJrzAMFcFFffdQliGtqSX5aVNSCHEyjfyVcyPAtFhhwCg8Pc7
z+yEWEV3DEuveMzqVYaKjs8D/1GSpmY8zC5jQ9/CM3RMrJyGlJWbcGA6XEoSUFui
oppM5OvkFrt1FYapHWiE3O6Jk3nKHiEHMRx3lCyilWilCLqsuOEMHVDmD63Rk2v9
rawSdZqzdIbFz4KoTV+BZkXT/IRkaByo37aDkHkMD0+rdPtL3Cof7ZsWEbqLi3sl
uflyA/wMCgG8N8AnZr6yDuIlraI+G2TsY8r2x4nAwMNYD3aBxgNq923uAWzLIa/S
CskTTxvqXBFj0dVdCSmsUzBUXkS+l4uT9WD1fiYeKUB10pZMppDfNIu2c/v1wbaA
7WMXvzEugoEbtFj0vNpZHZbjFadKtTfXwV+4A7P1Nj2qsXAScLRlTWF0dCBSb2Jp
bmVhdSAoQ3Jvc3MgdGhlIHJpdmVyIGFuZCBkZXN0cm95IHRoZSBicmlkZ2UuIFZp
Y3RvcnkgbGllcyBpbiBkZWNlcHRpb24uKSA8dmV4ZXJAb25saW5rLm5ldD6IXgQT
EQIAHgUCQDbgIAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDQ79icjP0XPxon
AKC3OhTMT+P6/BGlk/lhllOhq3emQQCgshhdRcosDD2YZVAxnoDCQTEpy965AQ0E
QDbgIRAEALq7W395qkQs7yAK18DGAqH1PHvMlBWxw8o1JvcAfrO5nQZbtnteDAmG
8BWsxP9IXYIeSuVbNG9VCSlhWZfQtjoTzQH5s8UqUpjara9pBkjDoiTN/RNfNwVp
DriQ1VQjvPv9gH8c29mepHepg+VZV7GuZ0rlF7mjxc5gZSMpgsJ3AAMFA/9OKBL8
hWkDFEyDqgJf9vpHX7ROQfWTS8jxI0+c3rXped3zo8C/keso2g2G28zViqewePHs
acenD72g8CCjUghtlthaFc5pKP8ohUt7f6QWAHcPKi8SrQCxtmRf0xdgg1tzAeGh
EZ5ebB7RsE1J4HYuWodOAwSbPnwGj4xKSNFlAYhJBBgRAgAJBQJANuAhAhsMAAoJ
ENDv2JyM/Rc/SxAAoNiZTWuCDqhshd4O5C0YzKkZdvIVAKDoliGHP3UaPPOumkh9
51V2n66yQg==
=/Mfp
-----END PGP PUBLIC KEY BLOCK-----

Re: need help

[Antony Stone]

On Friday 16 April 2004 7:28 pm, Matt Robineau wrote:

> I need help getting my rules working, I get an error: iptables: No
> chain/target/match by that name
>
> But it should work. I read how to do it in an online tutorial and it
> wont work for me, it keeps giving me this error.

It doesn't like one of the words you typed in the command you entered.

Since you didn't tell us what the command was, I can't tell you which word it 
was, but hopefully this is enough of a clue for you to work out the problem.

Regards,

Antony.

-- 
People who use Microsoft software should be certified.

                                                     Please reply to the list;
                                                           please don't CC me.

Re: Xen cpu usage limting

[Mark Williamson]

> I was also wondering if there is a way to assign a percentage of cpu time
> to a domain. Eg guarantee domain 3 gets 25% of the cpu time no matter how
> many other domains are in there, or how much cpu time they want.

The Atropos scheduler allows you to specify that a domain should receive x 
nanoseconds of CPU time per y nanoseconds of real time, i.e. what share of the 
CPU a domain gets and how regularly it gets scheduled.  Don't overcommit the 
CPU, though (i.e. reserve more than [100 minus a small margin for overheads] 
percent in total across all domains).

You can select Atropos using sched=atropos as a boot param to Xen.  The 
administrator tools (xc_dom_control.py and friends) don't have support for 
actually configuring it yet (though there's some library calls available in 
the Python Xc module if you want to write your own script) but I'll be 
checking in basic support early next week.

Cheers,

Mark



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Need help..

[I RATTAN]

I am back to trying xen-1.2 and need a little(?) help.

Hard disk config:
hda1 (primary swap), hda2(extended): had5(/, 1Gb), hda6(/usr, 2Gb),
hda7(1Gb), hda8(1Gb)

Installed Fedora-core-1 using / and /usr
Downloaded precompiled xen-1.2-install.tar.gz
Installed it
Able to boot domain-0

How do I put root partition info for dom1 on partition hda8
I tried dd if=/dev/hda5 of=/dev/hda8 bs=1024
  aborts with I/O error after copying the file system
  (mount says that it is invalid FS etc..)

Is there another way? Just want to see if I can boot one more
domain other than domain-0.

-ishwar



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: Need help..

[Borut Mrak]

On Tuesday 20 of April 2004 17:44, I RATTAN wrote:
> How do I put root partition info for dom1 on partition hda8
> I tried dd if=/dev/hda5 of=/dev/hda8 bs=1024
>   aborts with I/O error after copying the file system
>   (mount says that it is invalid FS etc..)

1. mke2fs /dev/hda8
2. mount /dev/hda8 /mnt
3. mkdir /mnt/mnt /mnt/proc/
4. cp -a /bin /boot /etc ... /mnt (everything but /proc)

presto, an exact copy. I tend to do this stuff from single user mode, but it 
might not be necessary.

regards,
Borut.

-- 
Zakaj ravno mene?


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: Need help..

[I RATTAN]

Addition to my message:

I copied from hda5 to hda8 the relevant directories using cp -pr
(bin boot dev etc initrd lib home opt sbin tmp var), couldn't copy
proc (is it created and populated at boot time?).

Command

xc_dom_create.py -Dvmid=1
results in error:
...
VM block device(s): "phy:hda8,sda1,w; phy:hda6,sda6,r"
VM cmdline: ...::eth0:off root=/dev/sda1 ro VMID=1 usr=/dev/hda6
Warning: one or more hard disk extents are writable by two or more
	domains simulteneously.
ERROR: This kind of disk sharing is not allowed at current
	safety level (0).

How do I make it work?

-ishwar

On Tue, 20 Apr 2004, I RATTAN wrote:

> I am back to trying xen-1.2 and need a little(?) help.
>
> Hard disk config:
> hda1 (primary swap), hda2(extended): had5(/, 1Gb), hda6(/usr, 2Gb),
> hda7(1Gb), hda8(1Gb)
>
> Installed Fedora-core-1 using / and /usr
> Downloaded precompiled xen-1.2-install.tar.gz
> Installed it
> Able to boot domain-0
>
> How do I put root partition info for dom1 on partition hda8
> I tried dd if=/dev/hda5 of=/dev/hda8 bs=1024
>   aborts with I/O error after copying the file system
>   (mount says that it is invalid FS etc..)
>
> Is there another way? Just want to see if I can boot one more
> domain other than domain-0.
>
> -ishwar
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: Need help..

[Rolf Neugebauer]

does dom0 still have /dev/hda8 mounted?
unmount it.
how does dom0 have /dev/hda6 mounted?
if it is mounted read/write, mount it read-only.

for all partitions:
If you want to mount a partition rw in one domain it *can not* be
mounted in any other domain
If you want to mount a partition in multiple domains it has to mounted
*read-only* in *all* domains.


Rolf

On Tue, 2004-04-20 at 19:02, I RATTAN wrote:
> Addition to my message:
> 
> I copied from hda5 to hda8 the relevant directories using cp -pr
> (bin boot dev etc initrd lib home opt sbin tmp var), couldn't copy
> proc (is it created and populated at boot time?).
> 
> Command
> 
> xc_dom_create.py -Dvmid=1
> results in error:
> ...
> VM block device(s): "phy:hda8,sda1,w; phy:hda6,sda6,r"
> VM cmdline: ...::eth0:off root=/dev/sda1 ro VMID=1 usr=/dev/hda6
> Warning: one or more hard disk extents are writable by two or more
> 	domains simulteneously.
> ERROR: This kind of disk sharing is not allowed at current
> 	safety level (0).
> 
> How do I make it work?
> 
> -ishwar
> 
> On Tue, 20 Apr 2004, I RATTAN wrote:
> 
> > I am back to trying xen-1.2 and need a little(?) help.
> >
> > Hard disk config:
> > hda1 (primary swap), hda2(extended): had5(/, 1Gb), hda6(/usr, 2Gb),
> > hda7(1Gb), hda8(1Gb)
> >
> > Installed Fedora-core-1 using / and /usr
> > Downloaded precompiled xen-1.2-install.tar.gz
> > Installed it
> > Able to boot domain-0
> >
> > How do I put root partition info for dom1 on partition hda8
> > I tried dd if=/dev/hda5 of=/dev/hda8 bs=1024
> >   aborts with I/O error after copying the file system
> >   (mount says that it is invalid FS etc..)
> >
> > Is there another way? Just want to see if I can boot one more
> > domain other than domain-0.
> >
> > -ishwar
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

Re: Need help..

[I RATTAN]

I have the partitions for separate / and /usr for domain-1
but no luck with domain-1 boot success. Domain-0 error about sharing
partitons across domians is gone though. So, I would like to know
how does exactly domain-1 boots(or will) based on the info in it's
/ partition or domain-0 / partiotion.

1. Does it use the /boot/grub info of either dom0 or dom1?
2. Does it use the /etc/fstab entries of dom0 or dom1?

Any other ideas involved that might significant here?

-ishwar

On Tue, 20 Apr 2004, I RATTAN wrote:

> I am back to trying xen-1.2 and need a little(?) help.
>
> Hard disk config:
> hda1 (primary swap), hda2(extended): had5(/, 1Gb), hda6(/usr, 2Gb),
> hda7(1Gb), hda8(1Gb)
>
> Installed Fedora-core-1 using / and /usr
> Downloaded precompiled xen-1.2-install.tar.gz
> Installed it
> Able to boot domain-0
>
> How do I put root partition info for dom1 on partition hda8
> I tried dd if=/dev/hda5 of=/dev/hda8 bs=1024
>   aborts with I/O error after copying the file system
>   (mount says that it is invalid FS etc..)
>
> Is there another way? Just want to see if I can boot one more
> domain other than domain-0.
>
> -ishwar
>
>


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

need help

[Pius Jerry]

Hello,
     I need your help and I hope you can be of help, am a user of linux 
and I want to ask if you can show me how to disable an IP with the linux 
and enable it through the linux
thanks 
am Pius Jerry 

Re: need help

[Nick Piggin]

Pius Jerry wrote:

>Hello,
>     I need your help and I hope you can be of help, am a user of linux 
>and I want to ask if you can show me how to disable an IP with the linux 
>and enable it through the linux
>thanks 
>am Pius Jerry 
>

Hi Pius,
This is the kernel development list. Please ask future questions in a
help list. However, have a look at the manpages for ifconfig(8) and ip(8).

Need HELP

[Vladimir Vanyukov]

Hey,
    I am using the WOLK 4.3 patchset and cpufreq seems to be working 
fine except for 2 problems. the /pro/sys/cpu interface seems to be 
broken, the speed-max and speed-min are both always 0, also i cannot 
change cpu frequency by writing to /proc/sys/cpu/0/speed and speed only 
correctly (at least i think its a correct value) displays the speed 
after i write something to /proc/cpufreq. The other problem is that i 
think the policy setting in /proc/cpufreq is broken, when it is set to 
performance it simply sets the speed to the the maximum and keeps it 
there and when on powersave is simply sets the speed to the minimum and 
keeps it there. Any help would be great, thanx.

need help

[Karthik RC]

Hello ,
   can we do IP/MAC filering through iptables..
regards
from karthik

Re: need help

[hare ram]

Hi

Yes you can do MAC address based Filter using Iptables

hare
----- Original Message ----- 
From: "Karthik RC" <karthikeyan-rc@naturesoft.net>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, April 29, 2003 3:51 PM
Subject: need help


> Hello ,
>    can we do IP/MAC filering through iptables..
> regards
> from karthik
> 
> 
> 

Re: need help

[Julius Wijaya]

You can use MAC match option

example:

IPTABLES -A INPUT -m mac --mac-source 00:00:00:00:01:11

regards.
JW

*********** REPLY SEPARATOR  ***********

On 29/04/2003 at 10:21 AM Karthik RC wrote:

>Hello ,
>   can we do IP/MAC filering through iptables..
>regards
>from karthik

Re: need help

[Maciej Soltysiak]

> Hello ,
>    can we do IP/MAC filering through iptables..
Yes, you can match the source/destination IP address and/or source MAC
address.

Examples:
# iptables -A FORWARD -s 10.20.30.40 -j REJECT
# iptables -A OUTPUT -d 10.12.13.14 -j LOG

# iptables -A FORWARD -m mac --mac-source 00:01:23:45:67:89 -j ACCEPT
# iptables -A FORWARD -m mac --mac-source ! 00:01:23:45:67:89 -j REJECT

Please read
# iptables -m mac --help
# iptables --help
And whatever comes to your mind, the modules have their own help messages.
# iptables -p tcp --help
# iptables -m state --help
etc...

Regards,
Maciej

Need help

[Yates, Ben]

[-- Attachment #1: Type: text/plain, Size: 263 bytes --]

Hi,
I'm a student and wondering if there is anyone out there could send me full
instructions step by step on how to successfully install Linux on a SGI
Indigo2 machine and what particular version of Linux is needed? Thanks for
any help.


Ben Yates
443-677-2693


[-- Attachment #2: Type: text/html, Size: 750 bytes --]

Need Help

[Mohammad Shakir]

[-- Attachment #1: Type: text/html, Size: 1368 bytes --]

Re: Need Help

[Davide]

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

hello,
   this is the iptables version

/sbin/iptables -F 
/sbin/iptables -t nat -F 
 
/sbin/iptables -P INPUT ACCEPT
/sbin/iptables -P FORWARD ACCEPT
/sbin/iptables -P OUTPUT ACCEPT

echo "1" > /proc/sys/net/ipv4/ip_forward

# for trasparent proxy
/sbin/iptables -t nat -A PREROUTING -p tcp -s 0.0.0.0/0 --dport 80 -j REDIRECT --to-ports 8080
# for direct connection excluding HTTP
/sbin/iptables -A FORWARD -p tcp -s 0.0.0.0/0 --dport 80 -j DROP

 
Davide



  ----- Original Message ----- 
  From: Mohammad Shakir 
  To: netfilter@lists.samba.org 
  Sent: Friday, September 27, 2002 1:08 PM
  Subject: Need Help


  Dear Russell,

  I have this setup in ipchains and now I want to convert in iptables. plz help me. 

  /sbin/ipchains  -F forward   
  /sbin/ipchains  -F input     
  /sbin/ipchains  -F output    

  /sbin/ipchains  -P forward   ACCEPT
  /sbin/ipchains  -P input     ACCEPT
  /sbin/ipchains  -P output    ACCEPT

  echo "1" > /proc/sys/net/ipv4/ip_forward

  # for transparent proxy
  /sbin/ipchains -A input -j REDIRECT 8080 -p tcp -s 0.0.0.0/0 -d 0.0.0.0/0 80
  # for direct connection excluding HTTP
  /sbin/ipchains  -A forward -j -p all -s 0.0.0.0/0 -d 0.0.0.0/0

  It was my old setup in RedHat Linux 7.0Rel.

  Now I have installed new verions of RedHat Linux 7.2, with Kernel 2.4.7-10 and iptables version 1.2.3.


  thanks in advance 

  shakir 



------------------------------------------------------------------------------
  Join the world's largest e-mail service with MSN Hotmail. Click Here


[-- Attachment #2: Type: text/html, Size: 4200 bytes --]

Re: Need Help

[Antony Stone]

On Sunday 29 September 2002 11:26 pm, Davide wrote:

> hello,
>    this is the iptables version
>
> /sbin/iptables -F
> /sbin/iptables -t nat -F
>
> /sbin/iptables -P INPUT ACCEPT

Ugh.

> /sbin/iptables -P FORWARD ACCEPT

Ughhh !!!

> /sbin/iptables -P OUTPUT ACCEPT
>
> echo "1" > /proc/sys/net/ipv4/ip_forward

It's a good idea to put this *after* your rules, to avoid any period of time 
when the kernel's forwarding packets, but without a ruleset loaded...

> # for trasparent proxy
> /sbin/iptables -t nat -A PREROUTING -p tcp -s 0.0.0.0/0 --dport 80 -j
> REDIRECT --to-ports 8080

The -s 0.0.0.0/0 is redundant.

> # for direct connection excluding HTTP
> /sbin/iptables -A FORWARD -p tcp -s 0.0.0.0/0 --dport 80 -j DROP

Please do this as an explicit ACCEPT rule for *outbound* packets which do not 
match HTTP, and have a default DROP policy on the FORWARD chain (so you block 
anything trying to come in).

ie:
iptables -P FORWARD DROP
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -p tcp --dport ! 80 -o $extIF -j ACCEPT

Antony.

-- 

G- GIT/E d- s+:--(-) a+ C++++$ UL++++$ P+(---)>++ L+++(++++)$ !E W(-) N(-) o? 
w-- O !M V+++(--) !PS !PE Y+ PGP+> t- tv@ b+++ DI++ D--- e++>+++ h++ r@? 5? 
!X- !R K--?

Need help

[Muhammad Farooq Bhatti]

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

Hi all 

My both client and server are Linux redhat 7.2 box and 
I am getting following error when I mount the file system

mount: RPC: Program not registered

what could be the reason please help

Thanx in advance

Muhammad Farooq Bhatti


[-- Attachment #2: Type: text/html, Size: 999 bytes --]

Re: Need help

[Patrice DUMAS - DOCT]

Hi,

Are you sure that portmap is running on the server (and client), and that
your ip is allowed ?
Is the mounts programm listed in 

$ rpcinfo -p <server>

?

Pat

> My both client and server are Linux redhat 7.2 box and 
> I am getting following error when I mount the file system
> 
> mount: RPC: Program not registered


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: Need help

[Andreas Behnert]

Muhammad Farooq Bhatti wrote:
> Hi all
>  
> My both client and server are Linux redhat 7.2 box and
> I am getting following error when I mount the file system
>  
> mount: RPC: Program not registered
>  
> what could be the reason please help
>  
> Thanx in advance
>  
> Muhammad Farooq Bhatti


Please verify that your portmapper is running, server and client:
http://nfs.sourceforge.net/nfs-howto/server.html#PORTMAPPER

and this exactly describes your problem:
http://nfs.sourceforge.net/nfs-howto/troubleshooting.html#SYMPTOM3


Regards,

Andreas



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: need help

[manjuanth n]

Dear Micheal,
  Thanks for the solution again, it  seems  i dont
have  any luck.  I  have patched the kernel with 
BLIST_LARGELUN  support I have tried all the options  
given by  u
still  success is  far away from me. I have made 
these  changes in the scsi_scan.c 
{"IBM", "AuSaV1S2", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
	{"HITACHI", "OPEN E*4", "*", BLIST_LARGELUN |
BLIST_FORCELUN |  BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*18", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*8", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*36", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},





 I tried  all the  possible  combination of
BLIST_SPARCE, BLIST_FORCE, etc.

  I would like to know whether the LINUX works on SAN
envirnment.  I  am feeling it has its own limitation
in SAN. 
If any one can help to solve my problem it will be a
great help. 

To  my strange  experiance   RedHat 6.2  with  kernel 
2.2-14 without  SMP  options  works fine, withot LUNO
and  without luns  biengin  sequence but  we require
multiple cpu option
if RedHat  6.2  works fine  i dont know why  it is 
not implemented in  RedHat 7.X.  I  have tried  allthe
possible  Redhat vesions
Including the latest  RedHat  7.3. To  my suprise  the
 RedHat does not boot at all if the qlogic  driver is
enabled at  boot.
and  have the same  problem of LUN0 and sequence 
LUNs. Is really Linux  operating sytem is  matured 
enough  to work as  high end 
server????
 
Pl  can  any body help??? 
 The details of  machine 

uname  -a  Linux m1 2.4.19-pre10 #12 SMP Thu Jun 13
05:48:37 IST 2002 i686 unknown

cat /proc/scsi/scsi
Attached devices: 
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi2 Channel: 00 Id: 15 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi2 Channel: 01 Id: 08 Lun: 00
  Vendor: IBM      Model: AuSaV1S2         Rev: 0   
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 01
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 02
  Vendor: HITACHI  Model: OPEN-E*36        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 03
  Vendor: HITACHI  Model: OPEN-E*18        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 04
  Vendor: HITACHI  Model: OPEN-E*2         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02


 
cat  /proc/partition
major minor  #blocks  name     rio rmerge rsect ruse
wio wmerge wsect wuse running use aveq

   8     0   35548160 sda 4426 7059 90710 33350 4064
4259 66776 78920 0 36970 112310
   8     1    5168614 sda1 4135 6674 86466 30360 2569
3334 47464 57210 0 30850 87600
   8     2   23554944 sda2 268 299 3978 2880 1491 922
19280 21680 0 14080 24560
   8     3    2096262 sda3 3 0 24 30 0 0 0 0 0 30 30
   8     4          1 sda4 0 0 0 0 0 0 0 0 0 0 0
   8     5    4720558 sda5 18 80 226 60 4 3 32 40 0 90
100
   8    16   56905920 sdb 1 3 8 0 0 0 0 0 0 0 0
   8    17   56902198 sdb1 0 0 0 0 0 0 0 0 0 0 0
   8    32   56905920 sdc 1 3 8 0 0 0 0 0 0 0 0
   8    33    2097136 sdc1 0 0 0 0 0 0 0 0 0 0 0
   8    48  512153280 sdd 1 3 8 0 0 0 0 0 0 0 0
   8    49  512152168 sdd1 0 0 0 0 0 0 0 0 0 0 0
   8    64  256076640 sde 1 3 8 0 0 0 0 0 0 0 0
   8    65   51207156 sde1 0 0 0 0 0 0 0 0 0 0 0
   8    80   28452960 sdf 1 3 8 0 0 0 0 0 0 0 0
   8    81   28452848 sdf1 0 0 0 0 0 0 0 0 0 0 0
   3     0     653856 hda 1 3 16 30 0 0 0 0 -1145
643450 13929193

--- Michael Clark <michael@metaparadigm.com> wrote:
> Did you try BLIST_SPARSELUN on the Hitachi
> devices?
> 
> Also, your devices are reporting as SCSI level 2 so
> no scanning will be done past lun 7 (This is only
> done for SCSI-3 devices). There is a patch
> floating around that adds BLIST_LARGELUN
> to make the scanning code treat these devices
> as SCSI-3 (255 luns)
> 
> ~mc
> 
> On 06/10/02 22:21, manjuanth n wrote:
> 
> >Dear  Michael,
> >
> >Thanks  for the solution, but  my  problem still 
> >remains  unresolved.  I  added the following lines 
> to
> > scsi_scan.c  and recompiled
> >  {"IBM", "AvSaV1S2", "*", BLIST_FORCELUN |
> >BLIST_SPARSELUN},
> >        {"HITACHI", "OPEN E*4", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*18", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*8", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*36", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "DF400", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF500", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF600", "*", BLIST_FORCELUN},
> >
> > the  out put of the scsi venders  are  as follows
> > cat  /proc/scsi/scsi
> >Attached devices:
> >Host: scsi2 Channel: 00 Id: 00 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Direct-Access                    ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 00 Id: 15 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 01 Id: 08 Lun: 00
> >  Vendor: IBM      Model: AuSaV1S2         Rev: 0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >Host: scsi3 Channel: 00 Id: 00 Lun: 00
> >  Vendor: HITACHI  Model: OPEN-E*4         Rev:
> 0116
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >
> >If u can  help me out where i am doing the  mistake
> 
> >it will be  of great help. 
> >plfind the enclosed scsi_scan.c  file. Is there any
> >method  or commands  to find out  BLIST_FORCELUN is
> >enabled?
> >
> > Thanks and  regards
> >Manjunath
> >
> >
> >--- Michael Clark <michael@metaparadigm.com> wrote:
> >  
> >
> >>2.4.18 needs a hint added to
> >>drivers/scsi/scsi_scan.c
> >>to allow it to scan targets with sparse luns.
> >>
> >>Look in /proc/scsi/scsi for the vendor and model
> and
> >>add them into the device_list array in scsi_scan.c
> >>
> >>...
> >>{"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> >>
> >>If you don't configure lun 0, you may have to use
> >>BLIST_FORCELUN which if my understanding is
> correct
> >>will force scanning of all luns.
> >>
> >>I hear there is some REPORT_LUNS code that will
> >>eliminate the need to do this, although don't know
> >>which kernel has it.
> >>
> >>~mc
> >>
> >>On 06/08/02 19:27, manjuanth n wrote:
> >>
> >>    
> >>
> >>>Dear sir,
> >>>we have SAN environment  with hitachi  storage
> box
> >>>and  brocade  switch. we are trying to  install
> >>>      
> >>>
> >>Linux 
> >>    
> >>
> >>>with  qlogic  HBA card.  we  are facing strange 
> >>>problems 
> >>>1. If  we  disable LUN 0  we will not be able to
> >>>      
> >>>
> >>see
> >>    
> >>
> >>>any LUNs on liunx  machine
> >>>2. If we  enable  LUN 0  we can  see all the 
> LUNS 
> >>>but  it  should be in sequence  i.e LUN0 ,1,2 , 3
> 
> >>>      
> >>>
> >>etc
> >>    
> >>
> >>>if we disable  LUN 3  we will not be able  to see
> >>>      
> >>>
> >>LUNS
> >>    
> >>
> >>>4 and  the  rest
> >>>Is the  above things  are limitation of linux.
> >>>Linux  machine is  running with  2.4.18 kernel
> >>>
> >>>Is there any solutions for  these problems? 
> >>>
> >>>Thanks and Regards
> >>>Manjuanth
> >>>
> >>>
>
>>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Yahoo! - Official partner of 2002 FIFA World Cup
> >>>http://fifaworldcup.yahoo.com
> >>>-
> >>>To unsubscribe from this list: send the line
> >>>      
> >>>
> >>"unsubscribe linux-kernel" in
> >>    
> >>
> >>>the body of a message to
> majordomo@vger.kernel.org
> >>>More majordomo info at 
> >>>      
> >>>
> >>http://vger.kernel.org/majordomo-info.html
> >>    
> >>
> >>>Please read the FAQ at  http://www.tux.org/lkml/
> >>> 
> >>>
> >>>      
> >>>
> >>    
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >
>
>------------------------------------------------------------------------
> >
> >/*
> > *  scsi_scan.c Copyright (C) 2000 Eric Youngdale
> > *
> > *  Bus scan logic.
> > *
> > *  This used to live in scsi.c, but that file was
> just a laundry basket
> > *  full of misc stuff.  This got separated out in
> order to make things
> > *  clearer.
> > */
> >
> >#define __NO_VERSION__
> >#include <linux/config.h>
> >#include <linux/module.h>
> >#include <linux/init.h>
> >
> >#include <linux/blk.h>
> >
> >#include "scsi.h"
> >#include "hosts.h"
> >#include "constants.h"
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: need help

[manjuanth n]

Dear Micheal,
  Thanks for the solution again, it  seems  i dont
have  any luck.  I  have patched the kernel with 
BLIST_LARGELUN  support I have tried all the options  
given by  u
still  success is  far away from me. I have made 
these  changes in the scsi_scan.c 
{"IBM", "AuSaV1S2", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
	{"HITACHI", "OPEN E*4", "*", BLIST_LARGELUN |
BLIST_FORCELUN |  BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*18", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*8", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*36", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},





 I tried  all the  possible  combination of
BLIST_SPARCE, BLIST_FORCE, etc.

  I would like to know whether the LINUX works on SAN
envirnment.  I  am feeling it has its own limitation
in SAN. 
If any one can help to solve my problem it will be a
great help. 

To  my strange  experiance   RedHat 6.2  with  kernel 
2.2-14 without  SMP  options  works fine, withot LUNO
and  without luns  biengin  sequence but  we require
multiple cpu option
if RedHat  6.2  works fine  i dont know why  it is 
not implemented in  RedHat 7.X.  I  have tried  allthe
possible  Redhat vesions
Including the latest  RedHat  7.3. To  my suprise  the
 RedHat does not boot at all if the qlogic  driver is
enabled at  boot.
and  have the same  problem of LUN0 and sequence 
LUNs. Is really Linux  operating sytem is  matured 
enough  to work as  high end 
server????
 
Pl  can  any body help??? 
 The details of  machine 

uname  -a  Linux m1 2.4.19-pre10 #12 SMP Thu Jun 13
05:48:37 IST 2002 i686 unknown

cat /proc/scsi/scsi
Attached devices: 
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi2 Channel: 00 Id: 15 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi2 Channel: 01 Id: 08 Lun: 00
  Vendor: IBM      Model: AuSaV1S2         Rev: 0   
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 01
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 02
  Vendor: HITACHI  Model: OPEN-E*36        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 03
  Vendor: HITACHI  Model: OPEN-E*18        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 04
  Vendor: HITACHI  Model: OPEN-E*2         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02


 
cat  /proc/partition
major minor  #blocks  name     rio rmerge rsect ruse
wio wmerge wsect wuse running use aveq

   8     0   35548160 sda 4426 7059 90710 33350 4064
4259 66776 78920 0 36970 112310
   8     1    5168614 sda1 4135 6674 86466 30360 2569
3334 47464 57210 0 30850 87600
   8     2   23554944 sda2 268 299 3978 2880 1491 922
19280 21680 0 14080 24560
   8     3    2096262 sda3 3 0 24 30 0 0 0 0 0 30 30
   8     4          1 sda4 0 0 0 0 0 0 0 0 0 0 0
   8     5    4720558 sda5 18 80 226 60 4 3 32 40 0 90
100
   8    16   56905920 sdb 1 3 8 0 0 0 0 0 0 0 0
   8    17   56902198 sdb1 0 0 0 0 0 0 0 0 0 0 0
   8    32   56905920 sdc 1 3 8 0 0 0 0 0 0 0 0
   8    33    2097136 sdc1 0 0 0 0 0 0 0 0 0 0 0
   8    48  512153280 sdd 1 3 8 0 0 0 0 0 0 0 0
   8    49  512152168 sdd1 0 0 0 0 0 0 0 0 0 0 0
   8    64  256076640 sde 1 3 8 0 0 0 0 0 0 0 0
   8    65   51207156 sde1 0 0 0 0 0 0 0 0 0 0 0
   8    80   28452960 sdf 1 3 8 0 0 0 0 0 0 0 0
   8    81   28452848 sdf1 0 0 0 0 0 0 0 0 0 0 0
   3     0     653856 hda 1 3 16 30 0 0 0 0 -1145
643450 13929193

--- Michael Clark <michael@metaparadigm.com> wrote:
> Did you try BLIST_SPARSELUN on the Hitachi
> devices?
> 
> Also, your devices are reporting as SCSI level 2 so
> no scanning will be done past lun 7 (This is only
> done for SCSI-3 devices). There is a patch
> floating around that adds BLIST_LARGELUN
> to make the scanning code treat these devices
> as SCSI-3 (255 luns)
> 
> ~mc
> 
> On 06/10/02 22:21, manjuanth n wrote:
> 
> >Dear  Michael,
> >
> >Thanks  for the solution, but  my  problem still 
> >remains  unresolved.  I  added the following lines 
> to
> > scsi_scan.c  and recompiled
> >  {"IBM", "AvSaV1S2", "*", BLIST_FORCELUN |
> >BLIST_SPARSELUN},
> >        {"HITACHI", "OPEN E*4", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*18", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*8", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*36", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "DF400", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF500", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF600", "*", BLIST_FORCELUN},
> >
> > the  out put of the scsi venders  are  as follows
> > cat  /proc/scsi/scsi
> >Attached devices:
> >Host: scsi2 Channel: 00 Id: 00 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Direct-Access                    ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 00 Id: 15 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 01 Id: 08 Lun: 00
> >  Vendor: IBM      Model: AuSaV1S2         Rev: 0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >Host: scsi3 Channel: 00 Id: 00 Lun: 00
> >  Vendor: HITACHI  Model: OPEN-E*4         Rev:
> 0116
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >
> >If u can  help me out where i am doing the  mistake
> 
> >it will be  of great help. 
> >plfind the enclosed scsi_scan.c  file. Is there any
> >method  or commands  to find out  BLIST_FORCELUN is
> >enabled?
> >
> > Thanks and  regards
> >Manjunath
> >
> >
> >--- Michael Clark <michael@metaparadigm.com> wrote:
> >  
> >
> >>2.4.18 needs a hint added to
> >>drivers/scsi/scsi_scan.c
> >>to allow it to scan targets with sparse luns.
> >>
> >>Look in /proc/scsi/scsi for the vendor and model
> and
> >>add them into the device_list array in scsi_scan.c
> >>
> >>...
> >>{"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> >>
> >>If you don't configure lun 0, you may have to use
> >>BLIST_FORCELUN which if my understanding is
> correct
> >>will force scanning of all luns.
> >>
> >>I hear there is some REPORT_LUNS code that will
> >>eliminate the need to do this, although don't know
> >>which kernel has it.
> >>
> >>~mc
> >>
> >>On 06/08/02 19:27, manjuanth n wrote:
> >>
> >>    
> >>
> >>>Dear sir,
> >>>we have SAN environment  with hitachi  storage
> box
> >>>and  brocade  switch. we are trying to  install
> >>>      
> >>>
> >>Linux 
> >>    
> >>
> >>>with  qlogic  HBA card.  we  are facing strange 
> >>>problems 
> >>>1. If  we  disable LUN 0  we will not be able to
> >>>      
> >>>
> >>see
> >>    
> >>
> >>>any LUNs on liunx  machine
> >>>2. If we  enable  LUN 0  we can  see all the 
> LUNS 
> >>>but  it  should be in sequence  i.e LUN0 ,1,2 , 3
> 
> >>>      
> >>>
> >>etc
> >>    
> >>
> >>>if we disable  LUN 3  we will not be able  to see
> >>>      
> >>>
> >>LUNS
> >>    
> >>
> >>>4 and  the  rest
> >>>Is the  above things  are limitation of linux.
> >>>Linux  machine is  running with  2.4.18 kernel
> >>>
> >>>Is there any solutions for  these problems? 
> >>>
> >>>Thanks and Regards
> >>>Manjuanth
> >>>
> >>>
>
>>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Yahoo! - Official partner of 2002 FIFA World Cup
> >>>http://fifaworldcup.yahoo.com
> >>>-
> >>>To unsubscribe from this list: send the line
> >>>      
> >>>
> >>"unsubscribe linux-kernel" in
> >>    
> >>
> >>>the body of a message to
> majordomo@vger.kernel.org
> >>>More majordomo info at 
> >>>      
> >>>
> >>http://vger.kernel.org/majordomo-info.html
> >>    
> >>
> >>>Please read the FAQ at  http://www.tux.org/lkml/
> >>> 
> >>>
> >>>      
> >>>
> >>    
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >
>
>------------------------------------------------------------------------
> >
> >/*
> > *  scsi_scan.c Copyright (C) 2000 Eric Youngdale
> > *
> > *  Bus scan logic.
> > *
> > *  This used to live in scsi.c, but that file was
> just a laundry basket
> > *  full of misc stuff.  This got separated out in
> order to make things
> > *  clearer.
> > */
> >
> >#define __NO_VERSION__
> >#include <linux/config.h>
> >#include <linux/module.h>
> >#include <linux/init.h>
> >
> >#include <linux/blk.h>
> >
> >#include "scsi.h"
> >#include "hosts.h"
> >#include "constants.h"
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

need help

[manjuanth n]

Dear sir,
 we have SAN environment  with hitachi  storage box
and  brocade  switch. we are trying to  install Linux 
with  qlogic  HBA card.  we  are facing strange 
problems 
1. If  we  disable LUN 0  we will not be able to see
any LUNs on liunx  machine
2. If we  enable  LUN 0  we can  see all the  LUNS 
but  it  should be in sequence  i.e LUN0 ,1,2 , 3  etc
if we disable  LUN 3  we will not be able  to see LUNS
4 and  the  rest
 Is the  above things  are limitation of linux.
Linux  machine is  running with  2.4.18 kernel

Is there any solutions for  these problems? 

Thanks and Regards
Manjuanth


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: need help

[Michael Clark]

2.4.18 needs a hint added to drivers/scsi/scsi_scan.c
to allow it to scan targets with sparse luns.

Look in /proc/scsi/scsi for the vendor and model and
add them into the device_list array in scsi_scan.c

...
{"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},

If you don't configure lun 0, you may have to use
BLIST_FORCELUN which if my understanding is correct
will force scanning of all luns.

I hear there is some REPORT_LUNS code that will
eliminate the need to do this, although don't know
which kernel has it.

~mc

On 06/08/02 19:27, manjuanth n wrote:

>Dear sir,
> we have SAN environment  with hitachi  storage box
>and  brocade  switch. we are trying to  install Linux 
>with  qlogic  HBA card.  we  are facing strange 
>problems 
>1. If  we  disable LUN 0  we will not be able to see
>any LUNs on liunx  machine
>2. If we  enable  LUN 0  we can  see all the  LUNS 
>but  it  should be in sequence  i.e LUN0 ,1,2 , 3  etc
>if we disable  LUN 3  we will not be able  to see LUNS
>4 and  the  rest
> Is the  above things  are limitation of linux.
>Linux  machine is  running with  2.4.18 kernel
>
>Is there any solutions for  these problems? 
>
>Thanks and Regards
>Manjuanth
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! - Official partner of 2002 FIFA World Cup
>http://fifaworldcup.yahoo.com
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>

Re: need help

[manjuanth n]

[-- Attachment #1: Type: text/plain, Size: 3446 bytes --]

Dear  Michael,

Thanks  for the solution, but  my  problem still 
remains  unresolved.  I  added the following lines  to
 scsi_scan.c  and recompiled
  {"IBM", "AvSaV1S2", "*", BLIST_FORCELUN |
BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*4", "*", BLIST_FORCELUN},
        {"HITACHI", "OPEN E*18", "*", BLIST_FORCELUN},
        {"HITACHI", "OPEN E*8", "*", BLIST_FORCELUN},
        {"HITACHI", "OPEN E*36", "*", BLIST_FORCELUN},
        {"HITACHI", "DF400", "*", BLIST_FORCELUN},
        {"HITACHI", "DF500", "*", BLIST_FORCELUN},
        {"HITACHI", "DF600", "*", BLIST_FORCELUN},

 the  out put of the scsi venders  are  as follows
 cat  /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor:  IBM     Model:  SERVERAID       Rev:  1.0
  Type:   Direct-Access                    ANSI SCSI
revision: 01
Host: scsi2 Channel: 00 Id: 15 Lun: 00
  Vendor:  IBM     Model:  SERVERAID       Rev:  1.0
  Type:   Processor                        ANSI SCSI
revision: 01
Host: scsi2 Channel: 01 Id: 08 Lun: 00
  Vendor: IBM      Model: AuSaV1S2         Rev: 0
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Processor                        ANSI SCSI
revision: 02

If u can  help me out where i am doing the  mistake 
it will be  of great help. 
plfind the enclosed scsi_scan.c  file. Is there any
method  or commands  to find out  BLIST_FORCELUN is
enabled?

 Thanks and  regards
Manjunath


--- Michael Clark <michael@metaparadigm.com> wrote:
> 2.4.18 needs a hint added to
> drivers/scsi/scsi_scan.c
> to allow it to scan targets with sparse luns.
> 
> Look in /proc/scsi/scsi for the vendor and model and
> add them into the device_list array in scsi_scan.c
> 
> ...
> {"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> 
> If you don't configure lun 0, you may have to use
> BLIST_FORCELUN which if my understanding is correct
> will force scanning of all luns.
> 
> I hear there is some REPORT_LUNS code that will
> eliminate the need to do this, although don't know
> which kernel has it.
> 
> ~mc
> 
> On 06/08/02 19:27, manjuanth n wrote:
> 
> >Dear sir,
> > we have SAN environment  with hitachi  storage box
> >and  brocade  switch. we are trying to  install
> Linux 
> >with  qlogic  HBA card.  we  are facing strange 
> >problems 
> >1. If  we  disable LUN 0  we will not be able to
> see
> >any LUNs on liunx  machine
> >2. If we  enable  LUN 0  we can  see all the  LUNS 
> >but  it  should be in sequence  i.e LUN0 ,1,2 , 3 
> etc
> >if we disable  LUN 3  we will not be able  to see
> LUNS
> >4 and  the  rest
> > Is the  above things  are limitation of linux.
> >Linux  machine is  running with  2.4.18 kernel
> >
> >Is there any solutions for  these problems? 
> >
> >Thanks and Regards
> >Manjuanth
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >-
> >To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> >  
> >
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[-- Attachment #2: scsi_scan.c --]
[-- Type: text/plain, Size: 27474 bytes --]

/*
 *  scsi_scan.c Copyright (C) 2000 Eric Youngdale
 *
 *  Bus scan logic.
 *
 *  This used to live in scsi.c, but that file was just a laundry basket
 *  full of misc stuff.  This got separated out in order to make things
 *  clearer.
 */

#define __NO_VERSION__
#include <linux/config.h>
#include <linux/module.h>
#include <linux/init.h>

#include <linux/blk.h>

#include "scsi.h"
#include "hosts.h"
#include "constants.h"

#ifdef CONFIG_KMOD
#include <linux/kmod.h>
#endif

/* The following devices are known not to tolerate a lun != 0 scan for
 * one reason or another.  Some will respond to all luns, others will
 * lock up.
 */

#define BLIST_NOLUN     	0x001
#define BLIST_FORCELUN  	0x002
#define BLIST_BORKEN    	0x004
#define BLIST_KEY       	0x008
#define BLIST_SINGLELUN 	0x010
#define BLIST_NOTQ		0x020
#define BLIST_SPARSELUN 	0x040
#define BLIST_MAX5LUN		0x080
#define BLIST_ISDISK    	0x100
#define BLIST_ISROM     	0x200

static void print_inquiry(unsigned char *data);
static int scan_scsis_single(unsigned int channel, unsigned int dev,
		unsigned int lun, int lun0_scsi_level, 
		unsigned int *max_scsi_dev, unsigned int *sparse_lun, 
		Scsi_Device ** SDpnt, struct Scsi_Host *shpnt, 
		char *scsi_result);
static int find_lun0_scsi_level(unsigned int channel, unsigned int dev,
				struct Scsi_Host *shpnt);

struct dev_info {
	const char *vendor;
	const char *model;
	const char *revision;	/* Latest revision known to be bad.  Not used yet */
	unsigned flags;
};

/*
 * This is what was previously known as the blacklist.  The concept
 * has been expanded so that we can specify other types of things we
 * need to be aware of.
 */
static struct dev_info device_list[] =
{
	{"Aashima", "IMAGERY 2400SP", "1.03", BLIST_NOLUN},	/* Locks up if polled for lun != 0 */
	{"CHINON", "CD-ROM CDS-431", "H42", BLIST_NOLUN},	/* Locks up if polled for lun != 0 */
	{"CHINON", "CD-ROM CDS-535", "Q14", BLIST_NOLUN},	/* Locks up if polled for lun != 0 */
	{"DENON", "DRD-25X", "V", BLIST_NOLUN},			/* Locks up if probed for lun != 0 */
	{"HITACHI", "DK312C", "CM81", BLIST_NOLUN},		/* Responds to all lun - dtg */
	{"HITACHI", "DK314C", "CR21", BLIST_NOLUN},		/* responds to all lun */
	{"IMS", "CDD521/10", "2.06", BLIST_NOLUN},		/* Locks-up when LUN>0 polled. */
	{"MAXTOR", "XT-3280", "PR02", BLIST_NOLUN},		/* Locks-up when LUN>0 polled. */
	{"MAXTOR", "XT-4380S", "B3C", BLIST_NOLUN},		/* Locks-up when LUN>0 polled. */
	{"MAXTOR", "MXT-1240S", "I1.2", BLIST_NOLUN},		/* Locks up when LUN>0 polled */
	{"MAXTOR", "XT-4170S", "B5A", BLIST_NOLUN},		/* Locks-up sometimes when LUN>0 polled. */
	{"MAXTOR", "XT-8760S", "B7B", BLIST_NOLUN},		/* guess what? */
	{"MEDIAVIS", "RENO CD-ROMX2A", "2.03", BLIST_NOLUN},	/*Responds to all lun */
	{"MICROP", "4110", "*", BLIST_NOTQ},			/* Buggy Tagged Queuing */
	{"NEC", "CD-ROM DRIVE:841", "1.0", BLIST_NOLUN},	/* Locks-up when LUN>0 polled. */
	{"PHILIPS", "PCA80SC", "V4-2", BLIST_NOLUN},		/* Responds to all lun */
	{"RODIME", "RO3000S", "2.33", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"SANYO", "CRD-250S", "1.20", BLIST_NOLUN},		/* causes failed REQUEST SENSE on lun 1
								 * for aha152x controller, which causes
								 * SCSI code to reset bus.*/
	{"SEAGATE", "ST157N", "\004|j", BLIST_NOLUN},		/* causes failed REQUEST SENSE on lun 1
								 * for aha152x controller, which causes
								 * SCSI code to reset bus.*/
	{"SEAGATE", "ST296", "921", BLIST_NOLUN},		/* Responds to all lun */
	{"SEAGATE", "ST1581", "6538", BLIST_NOLUN},		/* Responds to all lun */
	{"SONY", "CD-ROM CDU-541", "4.3d", BLIST_NOLUN},	
	{"SONY", "CD-ROM CDU-55S", "1.0i", BLIST_NOLUN},
	{"SONY", "CD-ROM CDU-561", "1.7x", BLIST_NOLUN},
	{"SONY", "CD-ROM CDU-8012", "*", BLIST_NOLUN},
	{"TANDBERG", "TDC 3600", "U07", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"TEAC", "CD-R55S", "1.0H", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"TEAC", "CD-ROM", "1.06", BLIST_NOLUN},		/* causes failed REQUEST SENSE on lun 1
								 * for seagate controller, which causes
								 * SCSI code to reset bus.*/
	{"TEAC", "MT-2ST/45S2-27", "RV M", BLIST_NOLUN},	/* Responds to all lun */
	{"TEXEL", "CD-ROM", "1.06", BLIST_NOLUN},		/* causes failed REQUEST SENSE on lun 1
								 * for seagate controller, which causes
								 * SCSI code to reset bus.*/
	{"QUANTUM", "LPS525S", "3110", BLIST_NOLUN},		/* Locks sometimes if polled for lun != 0 */
	{"QUANTUM", "PD1225S", "3110", BLIST_NOLUN},		/* Locks sometimes if polled for lun != 0 */
	{"QUANTUM", "FIREBALL ST4.3S", "0F0C", BLIST_NOLUN},	/* Locks up when polled for lun != 0 */
	{"MEDIAVIS", "CDR-H93MV", "1.31", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"SANKYO", "CP525", "6.64", BLIST_NOLUN},		/* causes failed REQ SENSE, extra reset */
	{"HP", "C1750A", "3226", BLIST_NOLUN},			/* scanjet iic */
	{"HP", "C1790A", "", BLIST_NOLUN},			/* scanjet iip */
	{"HP", "C2500A", "", BLIST_NOLUN},			/* scanjet iicx */
	{"YAMAHA", "CDR100", "1.00", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"YAMAHA", "CDR102", "1.00", BLIST_NOLUN},		/* Locks up if polled for lun != 0  
								 * extra reset */
	{"YAMAHA", "CRW8424S", "1.0", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"YAMAHA", "CRW6416S", "1.0c", BLIST_NOLUN},		/* Locks up if polled for lun != 0 */
	{"MITSUMI", "CD-R CR-2201CS", "6119", BLIST_NOLUN},	/* Locks up if polled for lun != 0 */
	{"RELISYS", "Scorpio", "*", BLIST_NOLUN},		/* responds to all LUN */
	{"MICROTEK", "ScanMaker II", "5.61", BLIST_NOLUN},	/* responds to all LUN */

/*
 * Other types of devices that have special flags.
 */
	{"SONY", "CD-ROM CDU-8001", "*", BLIST_BORKEN},
	{"TEXEL", "CD-ROM", "1.06", BLIST_BORKEN},
	{"IOMEGA", "Io20S         *F", "*", BLIST_KEY},
	{"INSITE", "Floptical   F*8I", "*", BLIST_KEY},
	{"INSITE", "I325VM", "*", BLIST_KEY},
	{"LASOUND","CDX7405","3.10", BLIST_MAX5LUN | BLIST_SINGLELUN},
	{"NRC", "MBR-7", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"NRC", "MBR-7.4", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"REGAL", "CDC-4X", "*", BLIST_MAX5LUN | BLIST_SINGLELUN},
	{"NAKAMICH", "MJ-4.8S", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"NAKAMICH", "MJ-5.16S", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"PIONEER", "CD-ROM DRM-600", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"PIONEER", "CD-ROM DRM-602X", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"PIONEER", "CD-ROM DRM-604X", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"EMULEX", "MD21/S2     ESDI", "*", BLIST_SINGLELUN},
	{"CANON", "IPUBJD", "*", BLIST_SPARSELUN},
	{"nCipher", "Fastness Crypto", "*", BLIST_FORCELUN},
	{"DEC","HSG80","*", BLIST_FORCELUN},
	{"COMPAQ","LOGICAL VOLUME","*", BLIST_FORCELUN},
	{"COMPAQ","CR3500","*", BLIST_FORCELUN},
	{"NEC", "PD-1 ODX654P", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"MATSHITA", "PD-1", "*", BLIST_FORCELUN | BLIST_SINGLELUN},
	{"iomega", "jaz 1GB", "J.86", BLIST_NOTQ | BLIST_NOLUN},
 	{"TOSHIBA","CDROM","*", BLIST_ISROM},
 	{"TOSHIBA","CD-ROM","*", BLIST_ISROM},
	{"MegaRAID", "LD", "*", BLIST_FORCELUN},
	{"DGC",  "RAID",      "*", BLIST_SPARSELUN}, // Dell PV 650F (tgt @ LUN 0)
	{"DGC",  "DISK",      "*", BLIST_SPARSELUN}, // Dell PV 650F (no tgt @ LUN 0) 
	{"DELL", "PV660F",   "*", BLIST_SPARSELUN},
	{"DELL", "PV660F   PSEUDO",   "*", BLIST_SPARSELUN},
	{"DELL", "PSEUDO DEVICE .",   "*", BLIST_SPARSELUN}, // Dell PV 530F
	{"DELL", "PV530F",    "*", BLIST_SPARSELUN}, // Dell PV 530F
	{"EMC", "SYMMETRIX", "*", BLIST_SPARSELUN},
	{"CMD", "CRA-7280", "*", BLIST_SPARSELUN},   // CMD RAID Controller
	{"CNSI", "G7324", "*", BLIST_SPARSELUN},     // Chaparral G7324 RAID
	{"CNSi", "G8324", "*", BLIST_SPARSELUN},     // Chaparral G8324 RAID
	{"Zzyzx", "RocketStor 500S", "*", BLIST_SPARSELUN},
	{"Zzyzx", "RocketStor 2000", "*", BLIST_SPARSELUN},
	{"SONY", "TSL",       "*", BLIST_FORCELUN},  // DDS3 & DDS4 autoloaders
	{"DELL", "PERCRAID", "*", BLIST_FORCELUN},
	{"HP", "NetRAID-4M", "*", BLIST_FORCELUN},
	{"ADAPTEC", "AACRAID", "*", BLIST_FORCELUN},
	{"ADAPTEC", "Adaptec 5400S", "*", BLIST_FORCELUN},
	{"COMPAQ", "MSA1000", "*", BLIST_FORCELUN},
	{"IBM", "AvSaV1S2", "*", BLIST_FORCELUN | BLIST_SPARSELUN},
	{"HITACHI", "OPEN E*4", "*", BLIST_FORCELUN},
	{"HITACHI", "OPEN E*18", "*", BLIST_FORCELUN},
	{"HITACHI", "OPEN E*8", "*", BLIST_FORCELUN},
	{"HITACHI", "OPEN E*36", "*", BLIST_FORCELUN},
	{"HITACHI", "DF400", "*", BLIST_FORCELUN},
	{"HITACHI", "DF500", "*", BLIST_FORCELUN},
	{"HITACHI", "DF600", "*", BLIST_FORCELUN},

	/*
	 * Must be at end of list...
	 */
	{NULL, NULL, NULL}
};

#define MAX_SCSI_LUNS 0xFFFFFFFF

#ifdef CONFIG_SCSI_MULTI_LUN
static unsigned int max_scsi_luns = MAX_SCSI_LUNS;
#else
static unsigned int max_scsi_luns = 1;
#endif

#ifdef MODULE

MODULE_PARM(max_scsi_luns, "i");
MODULE_PARM_DESC(max_scsi_luns, "last scsi LUN (should be between 1 and 2^32-1)");

#else

static int __init scsi_luns_setup(char *str)
{
	unsigned int tmp;

	if (get_option(&str, &tmp) == 1) {
		max_scsi_luns = tmp;
		return 1;
	} else {
		printk("scsi_luns_setup : usage max_scsi_luns=n "
		       "(n should be between 1 and 2^32-1)\n");
		return 0;
	}
}

__setup("max_scsi_luns=", scsi_luns_setup);

#endif

static void print_inquiry(unsigned char *data)
{
	int i;

	printk("  Vendor: ");
	for (i = 8; i < 16; i++) {
		if (data[i] >= 0x20 && i < data[4] + 5)
			printk("%c", data[i]);
		else
			printk(" ");
	}

	printk("  Model: ");
	for (i = 16; i < 32; i++) {
		if (data[i] >= 0x20 && i < data[4] + 5)
			printk("%c", data[i]);
		else
			printk(" ");
	}

	printk("  Rev: ");
	for (i = 32; i < 36; i++) {
		if (data[i] >= 0x20 && i < data[4] + 5)
			printk("%c", data[i]);
		else
			printk(" ");
	}

	printk("\n");

	i = data[0] & 0x1f;

	printk("  Type:   %s ",
	       i < MAX_SCSI_DEVICE_CODE ? scsi_device_types[i] : "Unknown          ");
	printk("                 ANSI SCSI revision: %02x", data[2] & 0x07);
	if ((data[2] & 0x07) == 1 && (data[3] & 0x0f) == 1)
		printk(" CCS\n");
	else
		printk("\n");
}

static int get_device_flags(unsigned char *response_data)
{
	int i = 0;
	unsigned char *pnt;
	for (i = 0; 1; i++) {
		if (device_list[i].vendor == NULL)
			return 0;
		pnt = &response_data[8];
		while (*pnt && *pnt == ' ')
			pnt++;
		if (memcmp(device_list[i].vendor, pnt,
			   strlen(device_list[i].vendor)))
			continue;
		pnt = &response_data[16];
		while (*pnt && *pnt == ' ')
			pnt++;
		if (memcmp(device_list[i].model, pnt,
			   strlen(device_list[i].model)))
			continue;
		return device_list[i].flags;
	}
	return 0;
}

/*
 *  Detecting SCSI devices :
 *  We scan all present host adapter's busses,  from ID 0 to ID (max_id).
 *  We use the INQUIRY command, determine device type, and pass the ID /
 *  lun address of all sequential devices to the tape driver, all random
 *  devices to the disk driver.
 */
void scan_scsis(struct Scsi_Host *shpnt,
		       uint hardcoded,
		       uint hchannel,
		       uint hid,
		       uint hlun)
{
	uint channel;
	unsigned int dev;
	unsigned int lun;
	unsigned int max_dev_lun;
	unsigned char *scsi_result;
	unsigned char scsi_result0[256];
	Scsi_Device *SDpnt;
	Scsi_Device *SDtail;
	unsigned int sparse_lun;
	int lun0_sl;

	scsi_result = NULL;

	SDpnt = (Scsi_Device *) kmalloc(sizeof(Scsi_Device),
					GFP_ATOMIC);
	if (SDpnt) {
		memset(SDpnt, 0, sizeof(Scsi_Device));
		/*
		 * Register the queue for the device.  All I/O requests will
		 * come in through here.  We also need to register a pointer to
		 * ourselves, since the queue handler won't know what device
		 * the queue actually represents.   We could look it up, but it
		 * is pointless work.
		 */
		scsi_initialize_queue(SDpnt, shpnt);
		SDpnt->request_queue.queuedata = (void *) SDpnt;
		/* Make sure we have something that is valid for DMA purposes */
		scsi_result = ((!shpnt->unchecked_isa_dma)
			       ? &scsi_result0[0] : kmalloc(512, GFP_DMA));
	}

	if (scsi_result == NULL) {
		printk("Unable to obtain scsi_result buffer\n");
		goto leave;
	}
	/*
	 * We must chain ourself in the host_queue, so commands can time out 
	 */
	SDpnt->queue_depth = 1;
	SDpnt->host = shpnt;
	SDpnt->online = TRUE;

	initialize_merge_fn(SDpnt);

        /*
         * Initialize the object that we will use to wait for command blocks.
         */
	init_waitqueue_head(&SDpnt->scpnt_wait);

	/*
	 * Next, hook the device to the host in question.
	 */
	SDpnt->prev = NULL;
	SDpnt->next = NULL;
	if (shpnt->host_queue != NULL) {
		SDtail = shpnt->host_queue;
		while (SDtail->next != NULL)
			SDtail = SDtail->next;

		SDtail->next = SDpnt;
		SDpnt->prev = SDtail;
	} else {
		shpnt->host_queue = SDpnt;
	}

	/*
	 * We need to increment the counter for this one device so we can track
	 * when things are quiet.
	 */
	if (hardcoded == 1) {
		Scsi_Device *oldSDpnt = SDpnt;
		struct Scsi_Device_Template *sdtpnt;
		channel = hchannel;
		if (channel > shpnt->max_channel)
			goto leave;
		dev = hid;
		if (dev >= shpnt->max_id)
			goto leave;
		lun = hlun;
		if (lun >= shpnt->max_lun)
			goto leave;
		if ((0 == lun) || (lun > 7))
			lun0_sl = SCSI_3; /* actually don't care for 0 == lun */
		else
			lun0_sl = find_lun0_scsi_level(channel, dev, shpnt);
		scan_scsis_single(channel, dev, lun, lun0_sl, &max_dev_lun, 
				  &sparse_lun, &SDpnt, shpnt, scsi_result);
		if (SDpnt != oldSDpnt) {

			/* it could happen the blockdevice hasn't yet been inited */
			/* queue_depth() moved from scsi_proc_info() so that
			   it is called before scsi_build_commandblocks() */
			if (shpnt->select_queue_depths != NULL)
				(shpnt->select_queue_depths)(shpnt,
							     shpnt->host_queue);

			for (sdtpnt = scsi_devicelist; sdtpnt; sdtpnt = sdtpnt->next)
				if (sdtpnt->init && sdtpnt->dev_noticed)
					(*sdtpnt->init) ();

			for (sdtpnt = scsi_devicelist; sdtpnt; sdtpnt = sdtpnt->next) {
				if (sdtpnt->attach) {
					(*sdtpnt->attach) (oldSDpnt);
					if (oldSDpnt->attached) {
						scsi_build_commandblocks(oldSDpnt);
						if (0 == oldSDpnt->has_cmdblocks) {
							printk("scan_scsis: DANGER, no command blocks\n");
							/* What to do now ?? */
						}
					}
				}
			}
			scsi_resize_dma_pool();

			for (sdtpnt = scsi_devicelist; sdtpnt; sdtpnt = sdtpnt->next) {
				if (sdtpnt->finish && sdtpnt->nr_dev) {
					(*sdtpnt->finish) ();
				}
			}
		}
	} else {
		/* Actual LUN. PC ordering is 0->n IBM/spec ordering is n->0 */
		int order_dev;

		for (channel = 0; channel <= shpnt->max_channel; channel++) {
			for (dev = 0; dev < shpnt->max_id; ++dev) {
				if (shpnt->reverse_ordering)
					/* Shift to scanning 15,14,13... or 7,6,5,4, */
					order_dev = shpnt->max_id - dev - 1;
				else
					order_dev = dev;

				if (shpnt->this_id != order_dev) {

					/*
					 * We need the for so our continue, etc. work fine. We put this in
					 * a variable so that we can override it during the scan if we
					 * detect a device *KNOWN* to have multiple logical units.
					 */
					max_dev_lun = (max_scsi_luns < shpnt->max_lun ?
					 max_scsi_luns : shpnt->max_lun);
					sparse_lun = 0;
					for (lun = 0, lun0_sl = SCSI_2; lun < max_dev_lun; ++lun) {
						/* don't probe further for luns > 7 for targets <= SCSI_2 */
						if ((lun0_sl < SCSI_3) && (lun > 7))
							break;

						if (!scan_scsis_single(channel, order_dev, lun, lun0_sl,
							 	       &max_dev_lun, &sparse_lun, &SDpnt, shpnt,
								       scsi_result)
						    && !sparse_lun)
							break;	/* break means don't probe further for luns!=0 */
						if (SDpnt && (0 == lun))
							lun0_sl = SDpnt->scsi_level;
					}	/* for lun ends */
				}	/* if this_id != id ends */
			}	/* for dev ends */
		}		/* for channel ends */
	}			/* if/else hardcoded */

      leave:

	{			/* Unchain SRpnt from host_queue */
		Scsi_Device *prev, *next;
		Scsi_Device *dqptr;

		for (dqptr = shpnt->host_queue; dqptr != SDpnt; dqptr = dqptr->next)
			continue;
		if (dqptr) {
			prev = dqptr->prev;
			next = dqptr->next;
			if (prev)
				prev->next = next;
			else
				shpnt->host_queue = next;
			if (next)
				next->prev = prev;
		}
	}

	/* Last device block does not exist.  Free memory. */
	if (SDpnt != NULL) {
		blk_cleanup_queue(&SDpnt->request_queue);
		kfree((char *) SDpnt);
	}

	/* If we allocated a buffer so we could do DMA, free it now */
	if (scsi_result != &scsi_result0[0] && scsi_result != NULL) {
		kfree(scsi_result);
	} {
		Scsi_Device *sdev;
		Scsi_Cmnd *scmd;

		SCSI_LOG_SCAN_BUS(4, printk("Host status for host %p:\n", shpnt));
		for (sdev = shpnt->host_queue; sdev; sdev = sdev->next) {
			SCSI_LOG_SCAN_BUS(4, printk("Device %d %p: ", sdev->id, sdev));
			for (scmd = sdev->device_queue; scmd; scmd = scmd->next) {
				SCSI_LOG_SCAN_BUS(4, printk("%p ", scmd));
			}
			SCSI_LOG_SCAN_BUS(4, printk("\n"));
		}
	}
}

/*
 * The worker for scan_scsis.
 * Returning 0 means Please don't ask further for lun!=0, 1 means OK go on.
 * Global variables used : scsi_devices(linked list)
 */
static int scan_scsis_single(unsigned int channel, unsigned int dev,
		unsigned int lun, int lun0_scsi_level,
		unsigned int *max_dev_lun, unsigned int *sparse_lun, 
		Scsi_Device ** SDpnt2, struct Scsi_Host *shpnt, 
		char *scsi_result)
{
	char devname[64];
	unsigned char scsi_cmd[MAX_COMMAND_SIZE];
	struct Scsi_Device_Template *sdtpnt;
	Scsi_Device *SDtail, *SDpnt = *SDpnt2;
	Scsi_Request * SRpnt;
	int bflags, type = -1;
	extern devfs_handle_t scsi_devfs_handle;
	int scsi_level;

	SDpnt->host = shpnt;
	SDpnt->id = dev;
	SDpnt->lun = lun;
	SDpnt->channel = channel;
	SDpnt->online = TRUE;

	scsi_build_commandblocks(SDpnt);
 
	/* Some low level driver could use device->type (DB) */
	SDpnt->type = -1;

	/*
	 * Assume that the device will have handshaking problems, and then fix
	 * this field later if it turns out it doesn't
	 */
	SDpnt->borken = 1;
	SDpnt->was_reset = 0;
	SDpnt->expecting_cc_ua = 0;
	SDpnt->starved = 0;

	if (NULL == (SRpnt = scsi_allocate_request(SDpnt))) {
		printk("scan_scsis_single: no memory\n");
		return 0;
	}

	/*
	 * We used to do a TEST_UNIT_READY before the INQUIRY but that was 
	 * not really necessary.  Spec recommends using INQUIRY to scan for
	 * devices (and TEST_UNIT_READY to poll for media change). - Paul G.
	 */

	SCSI_LOG_SCAN_BUS(3, printk("scsi: performing INQUIRY\n"));
	/*
	 * Build an INQUIRY command block.
	 */
	scsi_cmd[0] = INQUIRY;
	if ((lun > 0) && (lun0_scsi_level <= SCSI_2))
		scsi_cmd[1] = (lun << 5) & 0xe0;
	else	
		scsi_cmd[1] = 0;	/* SCSI_3 and higher, don't touch */
	scsi_cmd[2] = 0;
	scsi_cmd[3] = 0;
	scsi_cmd[4] = 255;
	scsi_cmd[5] = 0;
	SRpnt->sr_cmd_len = 0;
	SRpnt->sr_data_direction = SCSI_DATA_READ;

	scsi_wait_req (SRpnt, (void *) scsi_cmd,
	          (void *) scsi_result,
	          256, SCSI_TIMEOUT+4*HZ, 3);

	SCSI_LOG_SCAN_BUS(3, printk("scsi: INQUIRY %s with code 0x%x\n",
		SRpnt->sr_result ? "failed" : "successful", SRpnt->sr_result));

	/*
	 * Now that we don't do TEST_UNIT_READY anymore, we must be prepared
	 * for media change conditions here, so cannot require zero result.
	 */
	if (SRpnt->sr_result) {
		if ((driver_byte(SRpnt->sr_result) & DRIVER_SENSE) != 0 &&
		    (SRpnt->sr_sense_buffer[2] & 0xf) == UNIT_ATTENTION &&
		    SRpnt->sr_sense_buffer[12] == 0x28 &&
		    SRpnt->sr_sense_buffer[13] == 0) {
			/* not-ready to ready transition - good */
		} else {
			/* assume no peripheral if any other sort of error */
			scsi_release_request(SRpnt);
			return 0;
		}
	}

	/*
	 * Check for SPARSELUN before checking the peripheral qualifier,
	 * so sparse lun devices are completely scanned.
	 */

	/*
	 * Get any flags for this device.  
	 */
	bflags = get_device_flags (scsi_result);

	if (bflags & BLIST_SPARSELUN) {
	  *sparse_lun = 1;
	}
	/*
	 * Check the peripheral qualifier field - this tells us whether LUNS
	 * are supported here or not.
	 */
	if ((scsi_result[0] >> 5) == 3) {
		scsi_release_request(SRpnt);
		return 0;	/* assume no peripheral if any sort of error */
	}
	 /*   The Toshiba ROM was "gender-changed" here as an inline hack.
	      This is now much more generic.
	      This is a mess: What we really want is to leave the scsi_result
	      alone, and just change the SDpnt structure. And the SDpnt is what
	      we want print_inquiry to print.  -- REW
	 */
	if (bflags & BLIST_ISDISK) {
		scsi_result[0] = TYPE_DISK;                                                
		scsi_result[1] |= 0x80;     /* removable */
	}

	if (bflags & BLIST_ISROM) {
		scsi_result[0] = TYPE_ROM;
		scsi_result[1] |= 0x80;     /* removable */
	}
    
	memcpy(SDpnt->vendor, scsi_result + 8, 8);
	memcpy(SDpnt->model, scsi_result + 16, 16);
	memcpy(SDpnt->rev, scsi_result + 32, 4);

	SDpnt->removable = (0x80 & scsi_result[1]) >> 7;
	/* Use the peripheral qualifier field to determine online/offline */
	if (((scsi_result[0] >> 5) & 7) == 1) 	SDpnt->online = FALSE;
	else SDpnt->online = TRUE;
	SDpnt->lockable = SDpnt->removable;
	SDpnt->changed = 0;
	SDpnt->access_count = 0;
	SDpnt->busy = 0;
	SDpnt->has_cmdblocks = 0;
	/*
	 * Currently, all sequential devices are assumed to be tapes, all random
	 * devices disk, with the appropriate read only flags set for ROM / WORM
	 * treated as RO.
	 */
	switch (type = (scsi_result[0] & 0x1f)) {
	case TYPE_TAPE:
	case TYPE_DISK:
	case TYPE_PRINTER:
	case TYPE_MOD:
	case TYPE_PROCESSOR:
	case TYPE_SCANNER:
	case TYPE_MEDIUM_CHANGER:
	case TYPE_ENCLOSURE:
	case TYPE_COMM:
		SDpnt->writeable = 1;
		break;
	case TYPE_WORM:
	case TYPE_ROM:
		SDpnt->writeable = 0;
		break;
	default:
		printk("scsi: unknown type %d\n", type);
	}

	SDpnt->device_blocked = FALSE;
	SDpnt->device_busy = 0;
	SDpnt->single_lun = 0;
	SDpnt->soft_reset =
	    (scsi_result[7] & 1) && ((scsi_result[3] & 7) == 2);
	SDpnt->random = (type == TYPE_TAPE) ? 0 : 1;
	SDpnt->type = (type & 0x1f);

	print_inquiry(scsi_result);

        sprintf (devname, "host%d/bus%d/target%d/lun%d",
                 SDpnt->host->host_no, SDpnt->channel, SDpnt->id, SDpnt->lun);
        if (SDpnt->de) printk ("DEBUG: dir: \"%s\" already exists\n", devname);
        else SDpnt->de = devfs_mk_dir (scsi_devfs_handle, devname, NULL);

	for (sdtpnt = scsi_devicelist; sdtpnt;
	     sdtpnt = sdtpnt->next)
		if (sdtpnt->detect)
			SDpnt->attached +=
			    (*sdtpnt->detect) (SDpnt);

	SDpnt->scsi_level = scsi_result[2] & 0x07;
	if (SDpnt->scsi_level >= 2 ||
	    (SDpnt->scsi_level == 1 &&
	     (scsi_result[3] & 0x0f) == 1))
		SDpnt->scsi_level++;
	scsi_level = SDpnt->scsi_level;

	/*
	 * Accommodate drivers that want to sleep when they should be in a polling
	 * loop.
	 */
	SDpnt->disconnect = 0;


	/*
	 * Set the tagged_queue flag for SCSI-II devices that purport to support
	 * tagged queuing in the INQUIRY data.
	 */
	SDpnt->tagged_queue = 0;
	if ((SDpnt->scsi_level >= SCSI_2) &&
	    (scsi_result[7] & 2) &&
	    !(bflags & BLIST_NOTQ)) {
		SDpnt->tagged_supported = 1;
		SDpnt->current_tag = 0;
	}
	/*
	 * Some revisions of the Texel CD ROM drives have handshaking problems when
	 * used with the Seagate controllers.  Before we know what type of device
	 * we're talking to, we assume it's borken and then change it here if it
	 * turns out that it isn't a TEXEL drive.
	 */
	if ((bflags & BLIST_BORKEN) == 0)
		SDpnt->borken = 0;

	/*
	 * If we want to only allow I/O to one of the luns attached to this device
	 * at a time, then we set this flag.
	 */
	if (bflags & BLIST_SINGLELUN)
		SDpnt->single_lun = 1;

	/*
	 * These devices need this "key" to unlock the devices so we can use it
	 */
	if ((bflags & BLIST_KEY) != 0) {
		printk("Unlocked floptical drive.\n");
		SDpnt->lockable = 0;
		scsi_cmd[0] = MODE_SENSE;
		if (shpnt->max_lun <= 8)
			scsi_cmd[1] = (lun << 5) & 0xe0;
		else	scsi_cmd[1] = 0;	/* any other idea? */
		scsi_cmd[2] = 0x2e;
		scsi_cmd[3] = 0;
		scsi_cmd[4] = 0x2a;
		scsi_cmd[5] = 0;
		SRpnt->sr_cmd_len = 0;
		SRpnt->sr_data_direction = SCSI_DATA_READ;
		scsi_wait_req (SRpnt, (void *) scsi_cmd,
	        	(void *) scsi_result, 0x2a,
	        	SCSI_TIMEOUT, 3);
	}

	scsi_release_request(SRpnt);
	SRpnt = NULL;

	scsi_release_commandblocks(SDpnt);

	/*
	 * This device was already hooked up to the host in question,
	 * so at this point we just let go of it and it should be fine.  We do need to
	 * allocate a new one and attach it to the host so that we can further scan the bus.
	 */
	SDpnt = (Scsi_Device *) kmalloc(sizeof(Scsi_Device), GFP_ATOMIC);
	if (!SDpnt) {
		printk("scsi: scan_scsis_single: Cannot malloc\n");
		return 0;
	}
        memset(SDpnt, 0, sizeof(Scsi_Device));

	*SDpnt2 = SDpnt;
	SDpnt->queue_depth = 1;
	SDpnt->host = shpnt;
	SDpnt->online = TRUE;
	SDpnt->scsi_level = scsi_level;

	/*
	 * Register the queue for the device.  All I/O requests will come
	 * in through here.  We also need to register a pointer to
	 * ourselves, since the queue handler won't know what device
	 * the queue actually represents.   We could look it up, but it
	 * is pointless work.
	 */
	scsi_initialize_queue(SDpnt, shpnt);
	SDpnt->host = shpnt;
	initialize_merge_fn(SDpnt);

	/*
	 * Mark this device as online, or otherwise we won't be able to do much with it.
	 */
	SDpnt->online = TRUE;

        /*
         * Initialize the object that we will use to wait for command blocks.
         */
	init_waitqueue_head(&SDpnt->scpnt_wait);

	/*
	 * Since we just found one device, there had damn well better be one in the list
	 * already.
	 */
	if (shpnt->host_queue == NULL)
		panic("scan_scsis_single: Host queue == NULL\n");

	SDtail = shpnt->host_queue;
	while (SDtail->next) {
		SDtail = SDtail->next;
	}

	/* Add this device to the linked list at the end */
	SDtail->next = SDpnt;
	SDpnt->prev = SDtail;
	SDpnt->next = NULL;

	/*
	 * Some scsi devices cannot be polled for lun != 0 due to firmware bugs
	 */
	if (bflags & BLIST_NOLUN)
		return 0;	/* break; */

	/*
	 * If this device is known to support sparse multiple units, override the
	 * other settings, and scan all of them.
	 */
	if (bflags & BLIST_SPARSELUN) {
		*max_dev_lun = shpnt->max_lun;
		*sparse_lun = 1;
		return 1;
	}
	/*
	 * If this device is known to support multiple units, override the other
	 * settings, and scan all of them.
	 */
	if (bflags & BLIST_FORCELUN) {
		/* 
		 * Scanning MAX_SCSI_LUNS units would be a bad idea.
		 * Any better idea?
		 * I think we need REPORT LUNS in future to avoid scanning
		 * of unused LUNs. But, that is another item.
		 */
		if (*max_dev_lun < shpnt->max_lun)
			*max_dev_lun = shpnt->max_lun;
		else 	if ((max_scsi_luns >> 1) >= *max_dev_lun)
				*max_dev_lun += shpnt->max_lun;
			else	*max_dev_lun = max_scsi_luns;
		return 1;
	}
	/*
	 * REGAL CDC-4X: avoid hang after LUN 4
	 */
	if (bflags & BLIST_MAX5LUN) {
		*max_dev_lun = 5;
		return 1;
	}

	/*
	 * We assume the device can't handle lun!=0 if: - it reports scsi-0
	 * (ANSI SCSI Revision 0) (old drives like MAXTOR XT-3280) or - it
	 * reports scsi-1 (ANSI SCSI Revision 1) and Response Data Format 0
	 */
	if (((scsi_result[2] & 0x07) == 0)
	    ||
	    ((scsi_result[2] & 0x07) == 1 &&
	     (scsi_result[3] & 0x0f) == 0))
		return 0;
	return 1;
}

/*
 * The worker for scan_scsis.
 * Returns the scsi_level of lun0 on this host, channel and dev (if already
 * known), otherwise returns SCSI_2.
 */
static int find_lun0_scsi_level(unsigned int channel, unsigned int dev,
				struct Scsi_Host *shpnt)
{
	int res = SCSI_2;
	Scsi_Device *SDpnt;

	for (SDpnt = shpnt->host_queue; SDpnt; SDpnt = SDpnt->next)
	{
		if ((0 == SDpnt->lun) && (dev == SDpnt->id) &&
		    (channel == SDpnt->channel))
			return (int)SDpnt->scsi_level;
	}
	/* haven't found lun0, should send INQUIRY but take easy route */
	return res;
}

Re: need help

[Patrick Mansfield]

On Mon, Jun 10, 2002 at 07:21:39AM -0700, manjuanth n wrote:
> Dear  Michael,
> 
> Thanks  for the solution, but  my  problem still 
> remains  unresolved.  I  added the following lines  to
>  scsi_scan.c  and recompiled

>         {"HITACHI", "OPEN E*4", "*", BLIST_FORCELUN},

>  the  out put of the scsi venders  are  as follows
>  cat  /proc/scsi/scsi

> Host: scsi3 Channel: 00 Id: 00 Lun: 00
>   Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
>   Type:   Processor                        ANSI SCSI
> revision: 02

> 	{"HITACHI", "OPEN E*4", "*", BLIST_FORCELUN},

It looks like you are missing a '-' in the above.

-- Patrick Mansfield

Re: need help

[manjuanth n]

Dear Micheal,
  Thanks for the solution again, it  seems  i dont
have  any luck.  I  have patched the kernel with 
BLIST_LARGELUN  support I have tried all the options  
given by  u
still  success is  far away from me. I have made 
these  changes in the scsi_scan.c 
{"IBM", "AuSaV1S2", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
	{"HITACHI", "OPEN E*4", "*", BLIST_LARGELUN |
BLIST_FORCELUN |  BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*18", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*8", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*36", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},





 I tried  all the  possible  combination of
BLIST_SPARCE, BLIST_FORCE, etc.

  I would like to know whether the LINUX works on SAN
envirnment.  I  am feeling it has its own limitation
in SAN. 
If any one can help to solve my problem it will be a
great help. 

To  my strange  experiance   RedHat 6.2  with  kernel 
2.2-14 without  SMP  options  works fine, withot LUNO
and  without luns  biengin  sequence but  we require
multiple cpu option
if RedHat  6.2  works fine  i dont know why  it is 
not implemented in  RedHat 7.X.  I  have tried  allthe
possible  Redhat vesions
Including the latest  RedHat  7.3. To  my suprise  the
 RedHat does not boot at all if the qlogic  driver is
enabled at  boot.
and  have the same  problem of LUN0 and sequence 
LUNs. Is really Linux  operating sytem is  matured 
enough  to work as  high end 
server????
 
Pl  can  any body help??? 
 The details of  machine 

uname  -a  Linux m1 2.4.19-pre10 #12 SMP Thu Jun 13
05:48:37 IST 2002 i686 unknown

cat /proc/scsi/scsi
Attached devices: 
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi2 Channel: 00 Id: 15 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi2 Channel: 01 Id: 08 Lun: 00
  Vendor: IBM      Model: AuSaV1S2         Rev: 0   
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 01
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 02
  Vendor: HITACHI  Model: OPEN-E*36        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 03
  Vendor: HITACHI  Model: OPEN-E*18        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 04
  Vendor: HITACHI  Model: OPEN-E*2         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02


 
cat  /proc/partition
major minor  #blocks  name     rio rmerge rsect ruse
wio wmerge wsect wuse running use aveq

   8     0   35548160 sda 4426 7059 90710 33350 4064
4259 66776 78920 0 36970 112310
   8     1    5168614 sda1 4135 6674 86466 30360 2569
3334 47464 57210 0 30850 87600
   8     2   23554944 sda2 268 299 3978 2880 1491 922
19280 21680 0 14080 24560
   8     3    2096262 sda3 3 0 24 30 0 0 0 0 0 30 30
   8     4          1 sda4 0 0 0 0 0 0 0 0 0 0 0
   8     5    4720558 sda5 18 80 226 60 4 3 32 40 0 90
100
   8    16   56905920 sdb 1 3 8 0 0 0 0 0 0 0 0
   8    17   56902198 sdb1 0 0 0 0 0 0 0 0 0 0 0
   8    32   56905920 sdc 1 3 8 0 0 0 0 0 0 0 0
   8    33    2097136 sdc1 0 0 0 0 0 0 0 0 0 0 0
   8    48  512153280 sdd 1 3 8 0 0 0 0 0 0 0 0
   8    49  512152168 sdd1 0 0 0 0 0 0 0 0 0 0 0
   8    64  256076640 sde 1 3 8 0 0 0 0 0 0 0 0
   8    65   51207156 sde1 0 0 0 0 0 0 0 0 0 0 0
   8    80   28452960 sdf 1 3 8 0 0 0 0 0 0 0 0
   8    81   28452848 sdf1 0 0 0 0 0 0 0 0 0 0 0
   3     0     653856 hda 1 3 16 30 0 0 0 0 -1145
643450 13929193

--- Michael Clark <michael@metaparadigm.com> wrote:
> Did you try BLIST_SPARSELUN on the Hitachi
> devices?
> 
> Also, your devices are reporting as SCSI level 2 so
> no scanning will be done past lun 7 (This is only
> done for SCSI-3 devices). There is a patch
> floating around that adds BLIST_LARGELUN
> to make the scanning code treat these devices
> as SCSI-3 (255 luns)
> 
> ~mc
> 
> On 06/10/02 22:21, manjuanth n wrote:
> 
> >Dear  Michael,
> >
> >Thanks  for the solution, but  my  problem still 
> >remains  unresolved.  I  added the following lines 
> to
> > scsi_scan.c  and recompiled
> >  {"IBM", "AvSaV1S2", "*", BLIST_FORCELUN |
> >BLIST_SPARSELUN},
> >        {"HITACHI", "OPEN E*4", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*18", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*8", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*36", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "DF400", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF500", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF600", "*", BLIST_FORCELUN},
> >
> > the  out put of the scsi venders  are  as follows
> > cat  /proc/scsi/scsi
> >Attached devices:
> >Host: scsi2 Channel: 00 Id: 00 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Direct-Access                    ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 00 Id: 15 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 01 Id: 08 Lun: 00
> >  Vendor: IBM      Model: AuSaV1S2         Rev: 0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >Host: scsi3 Channel: 00 Id: 00 Lun: 00
> >  Vendor: HITACHI  Model: OPEN-E*4         Rev:
> 0116
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >
> >If u can  help me out where i am doing the  mistake
> 
> >it will be  of great help. 
> >plfind the enclosed scsi_scan.c  file. Is there any
> >method  or commands  to find out  BLIST_FORCELUN is
> >enabled?
> >
> > Thanks and  regards
> >Manjunath
> >
> >
> >--- Michael Clark <michael@metaparadigm.com> wrote:
> >  
> >
> >>2.4.18 needs a hint added to
> >>drivers/scsi/scsi_scan.c
> >>to allow it to scan targets with sparse luns.
> >>
> >>Look in /proc/scsi/scsi for the vendor and model
> and
> >>add them into the device_list array in scsi_scan.c
> >>
> >>...
> >>{"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> >>
> >>If you don't configure lun 0, you may have to use
> >>BLIST_FORCELUN which if my understanding is
> correct
> >>will force scanning of all luns.
> >>
> >>I hear there is some REPORT_LUNS code that will
> >>eliminate the need to do this, although don't know
> >>which kernel has it.
> >>
> >>~mc
> >>
> >>On 06/08/02 19:27, manjuanth n wrote:
> >>
> >>    
> >>
> >>>Dear sir,
> >>>we have SAN environment  with hitachi  storage
> box
> >>>and  brocade  switch. we are trying to  install
> >>>      
> >>>
> >>Linux 
> >>    
> >>
> >>>with  qlogic  HBA card.  we  are facing strange 
> >>>problems 
> >>>1. If  we  disable LUN 0  we will not be able to
> >>>      
> >>>
> >>see
> >>    
> >>
> >>>any LUNs on liunx  machine
> >>>2. If we  enable  LUN 0  we can  see all the 
> LUNS 
> >>>but  it  should be in sequence  i.e LUN0 ,1,2 , 3
> 
> >>>      
> >>>
> >>etc
> >>    
> >>
> >>>if we disable  LUN 3  we will not be able  to see
> >>>      
> >>>
> >>LUNS
> >>    
> >>
> >>>4 and  the  rest
> >>>Is the  above things  are limitation of linux.
> >>>Linux  machine is  running with  2.4.18 kernel
> >>>
> >>>Is there any solutions for  these problems? 
> >>>
> >>>Thanks and Regards
> >>>Manjuanth
> >>>
> >>>
>
>>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Yahoo! - Official partner of 2002 FIFA World Cup
> >>>http://fifaworldcup.yahoo.com
> >>>-
> >>>To unsubscribe from this list: send the line
> >>>      
> >>>
> >>"unsubscribe linux-kernel" in
> >>    
> >>
> >>>the body of a message to
> majordomo@vger.kernel.org
> >>>More majordomo info at 
> >>>      
> >>>
> >>http://vger.kernel.org/majordomo-info.html
> >>    
> >>
> >>>Please read the FAQ at  http://www.tux.org/lkml/
> >>> 
> >>>
> >>>      
> >>>
> >>    
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >
>
>------------------------------------------------------------------------
> >
> >/*
> > *  scsi_scan.c Copyright (C) 2000 Eric Youngdale
> > *
> > *  Bus scan logic.
> > *
> > *  This used to live in scsi.c, but that file was
> just a laundry basket
> > *  full of misc stuff.  This got separated out in
> order to make things
> > *  clearer.
> > */
> >
> >#define __NO_VERSION__
> >#include <linux/config.h>
> >#include <linux/module.h>
> >#include <linux/init.h>
> >
> >#include <linux/blk.h>
> >
> >#include "scsi.h"
> >#include "hosts.h"
> >#include "constants.h"
> 
=== message truncated ===
--- Michael Clark <michael@metaparadigm.com> wrote:
> 2.4.18 needs a hint added to
> drivers/scsi/scsi_scan.c
> to allow it to scan targets with sparse luns.
> 
> Look in /proc/scsi/scsi for the vendor and model and
> add them into the device_list array in scsi_scan.c
> 
> ...
> {"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> 
> If you don't configure lun 0, you may have to use
> BLIST_FORCELUN which if my understanding is correct
> will force scanning of all luns.
> 
> I hear there is some REPORT_LUNS code that will
> eliminate the need to do this, although don't know
> which kernel has it.
> 
> ~mc
> 
> On 06/08/02 19:27, manjuanth n wrote:
> 
> >Dear sir,
> > we have SAN environment  with hitachi  storage box
> >and  brocade  switch. we are trying to  install
> Linux 
> >with  qlogic  HBA card.  we  are facing strange 
> >problems 
> >1. If  we  disable LUN 0  we will not be able to
> see
> >any LUNs on liunx  machine
> >2. If we  enable  LUN 0  we can  see all the  LUNS 
> >but  it  should be in sequence  i.e LUN0 ,1,2 , 3 
> etc
> >if we disable  LUN 3  we will not be able  to see
> LUNS
> >4 and  the  rest
> > Is the  above things  are limitation of linux.
> >Linux  machine is  running with  2.4.18 kernel
> >
> >Is there any solutions for  these problems? 
> >
> >Thanks and Regards
> >Manjuanth
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >-
> >To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> >  
> >
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Re: need help

[manjuanth n]

Dear Micheal,
  Thanks for the solution again, it  seems  i dont
have  any luck.  I  have patched the kernel with 
BLIST_LARGELUN  support I have tried all the options  
given by  u
still  success is  far away from me. I have made 
these  changes in the scsi_scan.c 
{"IBM", "AuSaV1S2", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
	{"HITACHI", "OPEN E*4", "*", BLIST_LARGELUN |
BLIST_FORCELUN |  BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*18", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*8", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},
        {"HITACHI", "OPEN E*36", "*", BLIST_LARGELUN |
BLIST_FORCELUN | BLIST_SPARSELUN},





 I tried  all the  possible  combination of
BLIST_SPARCE, BLIST_FORCE, etc.

  I would like to know whether the LINUX works on SAN
envirnment.  I  am feeling it has its own limitation
in SAN. 
If any one can help to solve my problem it will be a
great help. 

To  my strange  experiance   RedHat 6.2  with  kernel 
2.2-14 without  SMP  options  works fine, withot LUNO
and  without luns  biengin  sequence but  we require
multiple cpu option
if RedHat  6.2  works fine  i dont know why  it is 
not implemented in  RedHat 7.X.  I  have tried  allthe
possible  Redhat vesions
Including the latest  RedHat  7.3. To  my suprise  the
 RedHat does not boot at all if the qlogic  driver is
enabled at  boot.
and  have the same  problem of LUN0 and sequence 
LUNs. Is really Linux  operating sytem is  matured 
enough  to work as  high end 
server????
 
Pl  can  any body help??? 
 The details of  machine 

uname  -a  Linux m1 2.4.19-pre10 #12 SMP Thu Jun 13
05:48:37 IST 2002 i686 unknown

cat /proc/scsi/scsi
Attached devices: 
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi2 Channel: 00 Id: 15 Lun: 00
  Vendor: IBM      Model: SERVERAID        Rev: 1.00
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi2 Channel: 01 Id: 08 Lun: 00
  Vendor: IBM      Model: AuSaV1S2         Rev: 0   
  Type:   Processor                        ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 01
  Vendor: HITACHI  Model: OPEN-E*4         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 02
  Vendor: HITACHI  Model: OPEN-E*36        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 03
  Vendor: HITACHI  Model: OPEN-E*18        Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 04
  Vendor: HITACHI  Model: OPEN-E*2         Rev: 0116
  Type:   Direct-Access                    ANSI SCSI
revision: 02


 
cat  /proc/partition
major minor  #blocks  name     rio rmerge rsect ruse
wio wmerge wsect wuse running use aveq

   8     0   35548160 sda 4426 7059 90710 33350 4064
4259 66776 78920 0 36970 112310
   8     1    5168614 sda1 4135 6674 86466 30360 2569
3334 47464 57210 0 30850 87600
   8     2   23554944 sda2 268 299 3978 2880 1491 922
19280 21680 0 14080 24560
   8     3    2096262 sda3 3 0 24 30 0 0 0 0 0 30 30
   8     4          1 sda4 0 0 0 0 0 0 0 0 0 0 0
   8     5    4720558 sda5 18 80 226 60 4 3 32 40 0 90
100
   8    16   56905920 sdb 1 3 8 0 0 0 0 0 0 0 0
   8    17   56902198 sdb1 0 0 0 0 0 0 0 0 0 0 0
   8    32   56905920 sdc 1 3 8 0 0 0 0 0 0 0 0
   8    33    2097136 sdc1 0 0 0 0 0 0 0 0 0 0 0
   8    48  512153280 sdd 1 3 8 0 0 0 0 0 0 0 0
   8    49  512152168 sdd1 0 0 0 0 0 0 0 0 0 0 0
   8    64  256076640 sde 1 3 8 0 0 0 0 0 0 0 0
   8    65   51207156 sde1 0 0 0 0 0 0 0 0 0 0 0
   8    80   28452960 sdf 1 3 8 0 0 0 0 0 0 0 0
   8    81   28452848 sdf1 0 0 0 0 0 0 0 0 0 0 0
   3     0     653856 hda 1 3 16 30 0 0 0 0 -1145
643450 13929193

--- Michael Clark <michael@metaparadigm.com> wrote:
> Did you try BLIST_SPARSELUN on the Hitachi
> devices?
> 
> Also, your devices are reporting as SCSI level 2 so
> no scanning will be done past lun 7 (This is only
> done for SCSI-3 devices). There is a patch
> floating around that adds BLIST_LARGELUN
> to make the scanning code treat these devices
> as SCSI-3 (255 luns)
> 
> ~mc
> 
> On 06/10/02 22:21, manjuanth n wrote:
> 
> >Dear  Michael,
> >
> >Thanks  for the solution, but  my  problem still 
> >remains  unresolved.  I  added the following lines 
> to
> > scsi_scan.c  and recompiled
> >  {"IBM", "AvSaV1S2", "*", BLIST_FORCELUN |
> >BLIST_SPARSELUN},
> >        {"HITACHI", "OPEN E*4", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*18", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*8", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "OPEN E*36", "*",
> BLIST_FORCELUN},
> >        {"HITACHI", "DF400", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF500", "*", BLIST_FORCELUN},
> >        {"HITACHI", "DF600", "*", BLIST_FORCELUN},
> >
> > the  out put of the scsi venders  are  as follows
> > cat  /proc/scsi/scsi
> >Attached devices:
> >Host: scsi2 Channel: 00 Id: 00 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Direct-Access                    ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 00 Id: 15 Lun: 00
> >  Vendor:  IBM     Model:  SERVERAID       Rev: 
> 1.0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 01
> >Host: scsi2 Channel: 01 Id: 08 Lun: 00
> >  Vendor: IBM      Model: AuSaV1S2         Rev: 0
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >Host: scsi3 Channel: 00 Id: 00 Lun: 00
> >  Vendor: HITACHI  Model: OPEN-E*4         Rev:
> 0116
> >  Type:   Processor                        ANSI
> SCSI
> >revision: 02
> >
> >If u can  help me out where i am doing the  mistake
> 
> >it will be  of great help. 
> >plfind the enclosed scsi_scan.c  file. Is there any
> >method  or commands  to find out  BLIST_FORCELUN is
> >enabled?
> >
> > Thanks and  regards
> >Manjunath
> >
> >
> >--- Michael Clark <michael@metaparadigm.com> wrote:
> >  
> >
> >>2.4.18 needs a hint added to
> >>drivers/scsi/scsi_scan.c
> >>to allow it to scan targets with sparse luns.
> >>
> >>Look in /proc/scsi/scsi for the vendor and model
> and
> >>add them into the device_list array in scsi_scan.c
> >>
> >>...
> >>{"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> >>
> >>If you don't configure lun 0, you may have to use
> >>BLIST_FORCELUN which if my understanding is
> correct
> >>will force scanning of all luns.
> >>
> >>I hear there is some REPORT_LUNS code that will
> >>eliminate the need to do this, although don't know
> >>which kernel has it.
> >>
> >>~mc
> >>
> >>On 06/08/02 19:27, manjuanth n wrote:
> >>
> >>    
> >>
> >>>Dear sir,
> >>>we have SAN environment  with hitachi  storage
> box
> >>>and  brocade  switch. we are trying to  install
> >>>      
> >>>
> >>Linux 
> >>    
> >>
> >>>with  qlogic  HBA card.  we  are facing strange 
> >>>problems 
> >>>1. If  we  disable LUN 0  we will not be able to
> >>>      
> >>>
> >>see
> >>    
> >>
> >>>any LUNs on liunx  machine
> >>>2. If we  enable  LUN 0  we can  see all the 
> LUNS 
> >>>but  it  should be in sequence  i.e LUN0 ,1,2 , 3
> 
> >>>      
> >>>
> >>etc
> >>    
> >>
> >>>if we disable  LUN 3  we will not be able  to see
> >>>      
> >>>
> >>LUNS
> >>    
> >>
> >>>4 and  the  rest
> >>>Is the  above things  are limitation of linux.
> >>>Linux  machine is  running with  2.4.18 kernel
> >>>
> >>>Is there any solutions for  these problems? 
> >>>
> >>>Thanks and Regards
> >>>Manjuanth
> >>>
> >>>
>
>>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Yahoo! - Official partner of 2002 FIFA World Cup
> >>>http://fifaworldcup.yahoo.com
> >>>-
> >>>To unsubscribe from this list: send the line
> >>>      
> >>>
> >>"unsubscribe linux-kernel" in
> >>    
> >>
> >>>the body of a message to
> majordomo@vger.kernel.org
> >>>More majordomo info at 
> >>>      
> >>>
> >>http://vger.kernel.org/majordomo-info.html
> >>    
> >>
> >>>Please read the FAQ at  http://www.tux.org/lkml/
> >>> 
> >>>
> >>>      
> >>>
> >>    
> >>
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >
>
>------------------------------------------------------------------------
> >
> >/*
> > *  scsi_scan.c Copyright (C) 2000 Eric Youngdale
> > *
> > *  Bus scan logic.
> > *
> > *  This used to live in scsi.c, but that file was
> just a laundry basket
> > *  full of misc stuff.  This got separated out in
> order to make things
> > *  clearer.
> > */
> >
> >#define __NO_VERSION__
> >#include <linux/config.h>
> >#include <linux/module.h>
> >#include <linux/init.h>
> >
> >#include <linux/blk.h>
> >
> >#include "scsi.h"
> >#include "hosts.h"
> >#include "constants.h"
> 
=== message truncated ===
--- Michael Clark <michael@metaparadigm.com> wrote:
> 2.4.18 needs a hint added to
> drivers/scsi/scsi_scan.c
> to allow it to scan targets with sparse luns.
> 
> Look in /proc/scsi/scsi for the vendor and model and
> add them into the device_list array in scsi_scan.c
> 
> ...
> {"<VENDOR>", "<MODEL>", "*", BLIST_SPARSELUN},
> 
> If you don't configure lun 0, you may have to use
> BLIST_FORCELUN which if my understanding is correct
> will force scanning of all luns.
> 
> I hear there is some REPORT_LUNS code that will
> eliminate the need to do this, although don't know
> which kernel has it.
> 
> ~mc
> 
> On 06/08/02 19:27, manjuanth n wrote:
> 
> >Dear sir,
> > we have SAN environment  with hitachi  storage box
> >and  brocade  switch. we are trying to  install
> Linux 
> >with  qlogic  HBA card.  we  are facing strange 
> >problems 
> >1. If  we  disable LUN 0  we will not be able to
> see
> >any LUNs on liunx  machine
> >2. If we  enable  LUN 0  we can  see all the  LUNS 
> >but  it  should be in sequence  i.e LUN0 ,1,2 , 3 
> etc
> >if we disable  LUN 3  we will not be able  to see
> LUNS
> >4 and  the  rest
> > Is the  above things  are limitation of linux.
> >Linux  machine is  running with  2.4.18 kernel
> >
> >Is there any solutions for  these problems? 
> >
> >Thanks and Regards
> >Manjuanth
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! - Official partner of 2002 FIFA World Cup
> >http://fifaworldcup.yahoo.com
> >-
> >To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> >  
> >
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Need Help

[Pravin Pathak]

Hi,
I need to port Linux on our hardware with
603e processor and cpc700 MMU. There is no disk support.
We do have flash ROM and ethernet on board.
Can anyone suggest a site I can download this port OR
a close match ?

Regards
Pravin


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Need Help

[Gabriel Paubert]

On Mon, 10 Jan 2000, Pravin Pathak wrote:

> 
> Hi,
> I need to port Linux on our hardware with
> 603e processor and cpc700 MMU. There is no disk support.
> We do have flash ROM and ethernet on board.
> Can anyone suggest a site I can download this port OR
> a close match ?

You might want to see if my patches for MVME2600 and especially the
bootloader part in arch/ppc/prepboot help. They are available at 

	ftp://vlab1.iram.es/pub/linux-2.2/

you will still need to perform the early setup of the CPC700, modify
the UART address etc...but the code includes things like PCI resource
allocation and is flexible enough to be adapted to a variety of PCI I/O
base addresses, memory offsets etc...

	Regards,
	Gabriel.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/