Sponsored Content
Full Discussion: problem with disks on SAN
Operating Systems Linux problem with disks on SAN Post 75025 by TioTony on Wednesday 15th of June 2005 12:15:55 AM
Old 06-15-2005
I agree the blocksize may be part of the issue but you may also want to check your EMC. EMCs are funny beasts, if your RAID group contains too few disks you may have a problem. We ran into this in our AIX 5.3->EMC Clariion environment.

Other things worth checking are your firmware and driver versions for your HBA.
 

9 More Discussions You Might Find Interesting

1. AIX

mksysb restore ( vgs on SAN disks)

I have my application vendor looking at this but I want to do my own investigation. I restored from mksysb and I see my vgs that contain my internal disks. But I do not see my vgs that contain disks from the SAN. This scares me .. {{ Ha, ha!! My AIX expert boss just told me I have nothing... (0 Replies)
Discussion started by: Skyybugg
0 Replies

2. Solaris

Problem with accessing SAN disks

Hi, I'm having a problem when attempting to define the OCR location for my 10g RAC setup on Solaris 10. I get the following error: The specified shared raw partition /dev/did/rdsk/d1s0 may not have the correct permission. Verify that the partition is owned by Oracle user. As per the Oracle10g... (15 Replies)
Discussion started by: michael.chow
15 Replies

3. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

4. Solaris

SAN DISKS - Number of slices ?

Good morning to one and all :-) Thank god its Friday, as its bee na rubbish week for me ! So, a quick question. Disks ! Ive got a few local disks, and a few SAN disks used on my solaris server. Whats confusing me, and Im not sure if there's an issue at the SAN end, or my end, regarding the... (3 Replies)
Discussion started by: sbk1972
3 Replies

5. Filesystems, Disks and Memory

Help with finding WWN of SAN disks

Hi, I'm new to SAN storage so I was wondering if someone can assist me with a problem. I have a solaris 10 OS with 3 SAN devices attached. We are trying to troubleshoot performance so I was asked to get the WWN of each SAN disk and show what it's attached to via the SVM mount in the metastat... (1 Reply)
Discussion started by: rkruck
1 Replies

6. UNIX for Dummies Questions & Answers

Identify SAN disks

Hello everybody, I'm using the binary inqraid (Linux RHEL) in order to retrieve information about SAN disks. The questions are: Given an LDEV, how do I know if the SAN disk related to this LDEV is being used by the OS? I mean, how can I demonstrate to "Storage department" that all disks of... (4 Replies)
Discussion started by: asanchez
4 Replies

7. Red Hat

Identify SAN disks not in use

Hello, How can I identify SAN disks not in use by the OS? Thank you. (8 Replies)
Discussion started by: asanchez
8 Replies

8. AIX

Issue with increasing size of SAN disks on AIX

HI, I have had an issue last night while trying to extend a filesystsem . chvg -g <vg> command cameback with an error 0516-1790 chvg: Failed bootinfo -s hdisk9. Ensure the physical volume is available and try again. 0516-732 chvg: Unable to change volume group u01vg. the VG has 1... (1 Reply)
Discussion started by: xmen01
1 Replies

9. Solaris

Sense key unit attention & iostat hardware and transport errors on SAN disks

Hello, I'm trying to get to the bottom of SAN disk errors we've been seeing. Server is Sun Fire X4270 M2 running Solaris 10 8/11 u10 X86 since April 2012. SAN HBAs are SG-PCIE2FC-QF8-Z-Sun-branded Qlogic. SAN storage system is Hitachi VSP. We have 32 LUNs in use and another 8 LUNs not brought... (4 Replies)
Discussion started by: TKD
4 Replies
sasmgr(1M)																sasmgr(1M)

NAME
sasmgr - utility to manage HP-UX Serial Attached SCSI (SAS) Mass Storage I/O cards / HBAs SYNOPSIS
lun_dsf} phy_id} phy_id} sasaddr} rvol_id | lun_dsf} lun_dsf} phy_id} phy_id} offset} sasaddr} phy_id} phy_id} sasaddr} DESCRIPTION
is a common diagnostic tool used for all Serial Attached SCSI (SAS) I/O cards / Host Bus Adapters (HBAs). requires the use of a device file to indicate the interface over which the requested command needs to be performed. Options recognizes the following command-line options: Suppresses the warning messages and continues executing the command. Provides a brief description of what the command does. Displays information for persistent device files (see intro(7)). If the command also displays hardware path information, then it shows the hardware path corresponding to the persistent device file. For example, if you use this option with the command and the and qualifiers, will print information for the persistent device files and display the corresponding lun hardware paths. Describes the command's qualifiers. A command is defined by a set of qualifiers which must be specified after the command name. Each qualifier is proceeded by the option. Some qualifiers can take one or more values and are given as ={x | y} where qualifier_name can take either the value x or y. Provides verbose information. For example, if you use this option with the command and qualifiers and will print additional header information. Commands recognizes the following commands. A command is defined by a set of qualifiers. Qualifiers are specified with the option. All keywords are case-sensitive. One of the following sets of qualifiers must be specified with the command: This set of qualifiers is used to create a RAID volume with the specified RAID level, volume size and physical disks. The value specified for the qualifier determines the RAID level for the volume. For example, specifies that a RAID1 volume should be created. The qualifier defines or specifies the enclosure and bay of each physical disk of the RAID volume. If the physical disks in a RAID volume are different sizes, then some disk space will be wasted. Volume expansion is not supported; once a volume has been created, its size cannot be increased. If the qualifier is not specified, then the volume is created with a maximum possible size based on the size of the physical disks specified. If the qualifier is not specified, then the default of 20% will be used for the volume. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning and executes the command. This command requires superuser privileges. Refer to the section below. This set of qualifiers is used to add a global spare disk. The global spare disk is used whenever a physical disk in any RAID volume on the Core I/O card / HBA fails. The qual- ifier defines or specifies the enclosure and bay of the global spare disk. The size of the disk specified should be greater than the size of at least one of the physical disks in the volume. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. The following qualifier must be specified with the command: Resets the specified target device. This is a destructive operation. If the option is not specified with this command, displays a warning message before continuing. Otherwise, it sup- presses the warning message and executes the command. When the command is run without qualifiers, it clears statistics of the SAS I/O card / HBA represented by device_file. The following qualifiers are specified with the command: Clears all statistics for the SAS I/O card / HBA, all PHYs, all ports, and all targets. Clears statistics for all PHYs or a specific PHY. Clears statistics for a port to which the specified PHY belongs to or clears statistics for all ports. Clears statistics for a specific target or all targets. One of the following sets of qualifiers must be specified with the command: This set of qualifiers is used to delete the RAID volume given by the volume ID. The volume ID can be obtained from the command using the qualifier. If a volume ID of is specified, then all the RAID volumes will be deleted. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. This set of qualifiers is used to delete the Core I/O card / HBA spare disk. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. Disables the SAS I/O card / HBA. This is a destructive operation. The SAS I/O card / HBA will become offline, all current I/Os will be aborted, and new I/Os will fail. An enable operation must be performed in order to bring the SAS I/O card / HBA back online. If the option is not specified with this command, displays a warning message before continuing. Otherwise, it suppresses the warning message and executes the command. The following qualifiers must be specified with the command: Updates the firmware on a SAS disk. The command will update disk firmware for regular physical disks, as well as those that are part of a RAID volume. The qualifier takes the name of the file containing the new disk firmware. The qualifier takes the enclosure and bay of the disk for which the firmware update is to be done. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. Updates the firmware on the specified enclosure. The qualifier takes the name of the file containing the new firmware. The qualifier takes the enclosure device file for which the firmware update is to be done. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. Updates the firmware on the specified HBA. The qualifier takes the name of the file containing the new firmware. If the option is not specified, displays a warning message before continuing the command. Otherwise, it suppresses the warning message and continues executing the command. This command requires superuser privileges. Refer to the section below. NOTE: If the firmware is being downgraded to a lower version, an incompatible older version of the firmware may get rejected. This typically happens if the downgraded version of firmware is very old compared to the current one on the card. Enables the SAS I/O card / HBA and brings it back online. This command causes the driver to initialize the SAS I/O card / HBA. When the command is run without qualifiers, it returns information about the SAS I/O card / HBA represented by device_file. The following qualifiers are specified with the command: Shows hardware path and SAS address information for a specific lun or all luns. If the option and the qualifier are specified with this command, then it displays persistent device file information. Shows lun location information for the lun specified with the qualifier. If the option and the qualifier are specified with this command, then it displays persistent device file information with the lun location information. Shows PCI ID information for the SAS I/O card / HBA. Shows information about all PHYs or a specific PHY. Shows information about a port to which the specified PHY belongs or provides information about all ports. Shows RAID configuration information for the Core I/O card / HBA. If the option is specified with this command, then it displays persistent device file information. Displays the contents of a specific PCI config space or MMIO register or all PCI config spaces or MMIO registers. PCI config space or MMIO register type is specified with the qualifier. If is not specified, then the command assumes a default register type of MMIO. Issues a SMP command. The file_name must contain the SMP request frame. Shows the SMP initiator SAS address to send SMP requests. Shows information about a specific target or all targets. Shows vital product data information for the SAS I/O card / HBA. When the command is run without qualifiers, it shows statistics about the SAS I/O card / HBA represented by device_file. The following qualifiers are specified with the command: Shows statistics for all PHYs or a specific PHY. Shows statistics for a port to which the specified PHY belongs to or provides statistics for all ports. Shows statistics for a specific target or all targets. The following qualifiers must be specified with the command: Allows the lun_dsf specified with to be associated with a new SAS target, which is specified with the qualifier. The lun_dsf must be the legacy device file and the new_hw_path must be the legacy hardware path. This command does not allow a persistent device file or the new style hardware path to be specified with the and qualifiers. For persistent device files, please use the command. See io_redirect_dsf(1M) for more information. This command is typically intended for replacing a bad drive. This operation must not be used while there are outstanding I/O requests to the lun_dsf or to any LUNs under the new_hw_path. If the option is not specified, displays a warning message before proceeding. Otherwise, it suppresses the warning message and executes the command. Allows the lun_dsf specified with to be associated with a new SAS target, which is specified with the qualifier. The lun_dsf must be the legacy device file. This command does not allow persistent device files to be specified with the and qualifiers. For persistent device files, please use the command. See io_redirect_dsf(1M) for more information. This command is typically intended for replacing a bad drive. This operation must not be used while there are outstanding I/O requests to the new lun_dsf. If the option is not specified, displays a warning message before proceeding. Otherwise, it suppresses the warning message and executes the command. Allows the HW path specified with to be associated with a new SAS target, which is specified with the qualifier. The and the must be the legacy hard- ware paths. This command does not allow the new style hardware paths to be specified with the and qualifiers. For persistent lun hardware paths, please use the command. See io_redirect_dsf(1M) for more information. This command is typically intended for replacing a bad drive. This operation must not be used while there are outstanding I/O requests to any LUNs under the If the option is not specified, displays a warning message before proceeding. Otherwise, it suppresses the warning message and executes the command. Resets the SAS I/O card / HBA and performs a complete re-initialization. This is a destructive operation. Some I/Os can be aborted by this command. If the option is not specified with this command, displays a warning message before continuing. Otherwise, it suppresses the warning message and executes the command. One of the following sets of qualifiers must be specified with the command: This set of qualifiers is used to turn on or off the locate LED for the specified lun. If it is a RAID device lun, then this command turns on or off the LOCATE LED for all the physical disks that are part of the RAID volume. This set of qualifiers is used to change the state of the volume based on the value specified by the qualifier and the volume specified by If the option is not specified, displays a warning message before proceeding with the operation. Otherwise, it sup- presses the warning message and continues executing the command. This set of qualifiers is used to change the rebuild rate of the volume specified by based on the rate specified by the If the option is not specified, displays a warning message before proceeding with the operation. Otherwise, it sup- presses the warning message and continues executing the command. Security Restrictions requires either superuser privilege or and privileges for RAID configurations. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. EXAMPLES
Display all PHY statistics of the SAS I/O card / HBA whose device file is Display all RAID volume information of the Core I/O card / HBA whose device file is Clear statistics for a port with PHY ID 1 of the SAS I/O card / HBA whose device file is Forcefully issue disable request to the SAS I/O card / HBA whose device file is Add a RAID volume with size 34000 (MB), level 1 (RAID1), and enc_bay 1:4,1:5 to the Core I/O card / HBA whose device file is Add a spare disk to the Core I/O card / HBA whose device file is Delete a RAID volume with volume ID 4 to the Core I/O card / HBA whose device file is Delete the Core I/O card / HBA Spare on the HBA whose device file is Change the state to ACTIVE for the RAID volume with volume id 3. Change the rebuild rate to 20% for the RAID volume with volume id 3. Update the firmware on the specified HBA. AUTHOR
was developed by HP. SEE ALSO
privileges(5), intro(7). at sasmgr(1M)
All times are GMT -4. The time now is 02:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy