Sponsored Content
Full Discussion: SAN/LVM question
Operating Systems Linux Red Hat SAN/LVM question Post 302534813 by mark54g on Tuesday 28th of June 2011 10:27:46 PM
Old 06-28-2011
My experience with MSA storage (which the P2000 is the next generation of) has not been stellar. I have had a tremendous amount of failures. Also, isn't the P2000 an arbitrated loop system? If you plan on chaining them together, that may mean downtime.

It's too bad you can't do something like use an IBM SVC in front of your storage, as it would make a lot of your issues go away.

I agree wholeheartedly with cjcox. Large file systems on low budgets are asking for problems. I would create a VG for each array and then create LVs for each "client" logging server.

Also, I would suggest at LEAST 1 hot spare in your groups, as losing a 2TB drive will degrade performance, since they are 7200rpm to begin with, but the time to rebuild RAID 5 should be considered. You are talking many hours. If you have a second failure during that time, data is gone.

Also, your 2TB drives are really 1.85TB, and each array you create is about 9TB in size. Carve up your LUNs and treat them as PVs, using a rather large extent size.

Do you have to keep the logs around full time? My suggestion would be to have your server keep the latest data in an uncompressed format and then archive it to compressed formats later on, or at least move them into other drives to keep your file systems smaller.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Multiple Paths to SAN with LVM in Linux?

I'm setting up a CentOS 5 server that will be connected to an HP EVA4000. My previous experience is with an HP VA7400 and HP-UX. In HP-UX I can add "alternate paths" to a volume group in order to have redundant paths to the SAN via dual fiber channel HBAs just by either adding them with... (3 Replies)
Discussion started by: deckard
3 Replies

2. AIX

Question about IBM San Ds4500

I have a question about SAN commands I have almost 15Tb of disk on my san but assigned and something else I have almost 11Tb There is a command to know, what its my real total storage capacity and another command to know how much I used .? Thanks again in advance (0 Replies)
Discussion started by: lo-lp-kl
0 Replies

3. Linux

LVM snapshot question

Hi All, I am planning to do a LVM replicate to another server. Example : server1.foo.com has / , /boot , swap and few LVM partitions. All are in /dev/sda disk of size 80GB. /dev/sda5 is a LVM partition which has only one vg00 and it has 2 LV's (/var and /usr) and a SAN storage connected to... (0 Replies)
Discussion started by: rakrhn
0 Replies

4. Filesystems, Disks and Memory

LVM snapshot question

Hi All, I am planning to do a LVM replicate to another server. Example : server1.foo.com has / , /boot , swap and few LVM partitions. All are in /dev/sda disk of size 80GB. /dev/sda5 is a LVM partition which has only one vg00 and it has 2 LV's (/var and /usr) and a SAN storage connected to... (0 Replies)
Discussion started by: rakrhn
0 Replies

5. Red Hat

LVM question

Hi all; I have a quick question about LVM. 2.6.18-92.1.18.el5 Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 5.3 (Tikanga) Release: 5.3 Codename: Tikanga I was going through /etc/lvm.conf and I am not clear with lvm meta... (0 Replies)
Discussion started by: maverick_here
0 Replies

6. UNIX for Dummies Questions & Answers

Linux LVM Question

I've three partitions on /dev/sda: sda1, sda2 sda3. There is FREE space between sda2 and sda3 and sda3 ends on the last sector. sda2 and sda3 have the same number of sectors allocated and so are the exact same size. /dev/sda2 is already part of the VG VolGroup. However, what puzzles me is that... (0 Replies)
Discussion started by: Devyn
0 Replies

7. AIX

HACMP two-node cluster with two SAN storages mirrored using LVM

HACMP two-node cluster with mirrored LVM. HACMP two-node cluster with two SAN storages mirrored using LVM. Configured 2 disk heartbeat networks - 1 per each SAN storage. While performing redundancy tests. Once one of SAN storage is down - cluster is going to ERROR state. What are the guidelines... (2 Replies)
Discussion started by: OdilPVC
2 Replies

8. UNIX for Dummies Questions & Answers

Question about lvm file creation

Hi, I have below code for disk creation disk_list=$(ls /dev/sd) for disk in $disk_list do pvcreate $i done So what my understanding is first it is checking the disk under /dev sdb,sdc,sdd,...sdz whether 25 disk are existing if not then its creating the 25 physical volume. I... (4 Replies)
Discussion started by: stew
4 Replies

9. HP-UX

SAN Migration question

Hi, I am very new to HP-UX, and we're going to be doing a SAN migration. We're going to take down the machine, and zone it to the new SAN. My question is, will the device names change and will that interfere with the LVM? If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

10. Filesystems, Disks and Memory

Some question about SAN on HP 4400 EVA

Good morning. For testing purpose i have buy a SAN DISK SHELF i need now a controller(hsv300) and a switch SAN Is my first SAN so i'm a little confused about cables. For testing we use an old rx2600 hp server the adapter is HP A6795AX A6795-62001 Some fast questions: i need an fc/fc cable... (7 Replies)
Discussion started by: Linusolaradm1
7 Replies
sautil(1M)																sautil(1M)

NAME
sautil - support utility for the HP SmartArray RAID controller family SYNOPSIS
device_file [-N] device_file [-s] device_file fw_image device_file fw_image physical_drive_id device_file fw_image encl_physical_drive_id device_file device_file device_file device_file logical_drive_number device_file rate device_file device_file device_file device_file [-raw] device_file device_file physical_drive_id [-raw] device_file device_file device_file DESCRIPTION
The command is a support tool for the HP SmartArray RAID Controller Family. This command allows the system administrator to perform tasks such as: 1) Retrieving RAID configuration and status information for the controller, logical drive, physical disk, cache, etc.; 2) Retrieving RAID driver information (driver state, trace log, statistics, etc.); 3) Downloading new revisions of controller or disk firmware; 4) Sending instructions to the firmware (reset controller, scan SCSI bus, etc.); and 5) Recreating the controller device file(s). Prerequisites Some of the options are intended for use by HP support personnel and require detailed knowledge of the RAID SA driver or firmware to inter- pret the output. Security Restrictions requires either the superuser privilege or and privileges. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. Options recognizes the following options and parameters as indicated in the section above. Keyword options are order-dependent, but are not case- sensitive. device_file Most options require a device file parameter, e.g., The device file for a specific RAID SA controller can be determined from the output. When the device file parameter is specified without any options, will display information such as the RAID SA driver state, controller hardware path, firmware revision, capacity expansion and rebuild priority settings, cache status and settings, logical drive configuration and physical drive properties. When the optional argument is specified, persistent device files (see intro(7)) are displayed for logical drives. When the optional argument is specified, a subset of the information is displayed. This option downloads the specified firmware image file (fw_image) to the controller. The image file name is case-sensitive. The firmware download process usually completes within one minute, but could theoretically take up to eight minutes. All I/O to the controller are temporarily halted dur- ing this time. This option downloads the specified firmware image file (fw_image) to physical disk specified by the (physical_drive_id). The image file name is case-sensitive. physical_drive_id To specify the SCSI physical disk. It can be represented as such as: 4:12. Valid channel numbers are between 1 and 4. Valid target numbers are between 0 and 15. To specify the SAS/SATA physical disk. It can be represented as either such as: 2I:1:10 or (wwid), such as: 0x500000e010f16432. This option downloads the specified firmware image file (fw_image) to the storage enclosure processor. This option is supported on SAS Smart Array HBAs only. The image file name is case-sensitive. The firmware download process takes ten to fifteen minutes. All I/O to the controller are temporarily halted during this time. encl_physical_drive_id To specify the storage enclosure processor. It can be represented as either such as: 1E:1:0 or (wwid), such as: 0x500000e010f16432. This option resets the controller. Some situations that may require a controller reset are: 1) OLR was performed and the logical drives on the replacement controller are not detected; 2) a disk enclosure with an existing RAID configuration was hot-added and the logical drives on that enclosure are not detected. This option tells the controller to rescan all SCSI buses. A situation that may require a scan is when a physical disk is hot-inserted into the system's internal drive bay. This option tells the controller to start rebuilding any logical drives that are in state. All logical drives in this state will eventually transition to Heavy I/O to the controller may delay this transition. There is no adverse impact if this option is invoked when no logical drives are in state. This option grants permission to the controller to set the state of the specified failed logical drive (logical_drive_number) to "OK" and to set the states of all failed physical disks that have been replaced via hot-plug exchanges to "OK". WARNING: While this option preserves the RAID configuration (logical drive configurations, controller settings, etc.), data on the failed logical drive may have already been compromised. If more disks have failed than the RAID level can accommo- date, you will need to restore your data from backup media. This option tells the controller to set the SCSI transfer rate to a lower speed than it would normally allow. Valid arguments for the rate field are (and ultra-160 for controllers that support Ultra-320). This option displays statistics counters maintained by the RAID SA "ciss" driver. This option clears the statistics counters maintained by the RAID SA "ciss" driver. This option displays the trace buffer of the RAID SA "ciss" driver. This option displays the firmware error log of the RAID SA controller. When the optional argument is specified, the raw data (in bytes) are displayed. This option clears the firmware error log of the RAID160 SA controller. It is not available for SmartArray 640x controllers. This option displays the error log for the physical disk specified by the (physical_drive_id). When the optional argument is specified, the raw data (in bytes) are displayed. This option displays the RAID SA controller's PCI configuration header. This option allows interactive reading of the RAID SA controller's registers. WARNING: Reading an invalid register may cause a system crash. This option is only available for SAS/SATA. Vital Product Data contains Product Description, Part Number, Engineering Date Code, Serial Number, Miscellaneous Informa- tion, Manufacturing Date Code, EFI Version, Asset Tag, HBA Firmware Version, and WWN. This option runs the RAID SA startup script to recreate the device files (/dev/cissX). Logical Drive State Definitions All physical disks in the logical drive are operational. Some possible causes: 1) Multiple physical disks in a fault-tolerant (RAID 1, 1+0, 5, ADG) logical drive have failed. 2) One or more disks in a RAID 0 logical drive have failed. 3) Cache data loss has occurred. 4) Array expansion was aborted. 5) The logical drive is temporarily disabled because another logical drive on the controller had a missing disk at power-up. Also known as "degraded" state. A physical disk in a fault tolerant logical drive has failed. For RAID 1, 1+0 or 5, data loss may result if a second disk should fail. For RAID ADG, data loss may result if two additional disks should fail. A replacement disk is present, but rebuild hasn't started yet (another logical drive may be currently rebuilding). The logical drive will also return to this state if the rebuild had been aborted due to unrecoverable read errors from another disk. One or more physical disks in this logical drive are being rebuilt. While the logical drive was in a degraded state, the system was powered off and a disk other than the failed disk was replaced. Shut off the system and replace the correct (failed) disk. While the system was off, one or more disks were removed. Note: the other logical drives are held in a temporary "failed" state when this occurs. The data in the logical drive is being reorganized because: 1) Physical disks have been added to the array (capacity expansion). 2) The stripe size is being changed (stripe-size migration). 3) The RAID level is being changed (RAID-level migration). A capacity expansion operation is in progress (or is queued up) that will make room on the disks for this new logical drive. Until room has been made on the physical disks, this newly configured logical drive cannot be read or written. The logical drive is waiting to undergo data reorganization (see above). Possible causes for the delay are a rebuild or expansion operation may already be in progress. Physical Disk State Definitions The physical disk is configured in one or more logical drives and is operational. The physical disk is configured as a spare disk. The physical disk has not been configured in any logical drives. The configured physical disk has failed. RETURN VALUE
returns the following values: Successful completion. Command line syntax error. Incompatible CISS driver API. Failure opening a file. Other error. EXAMPLES
Display RAID subsystem information for the controller Update the firmware on the controller using the firmware image file Update the firmware on the physical disk (SCSI ID "13") connected to channel "2" of controller using the firmware image file located in the current directory: Recreate the device files for all RAID SA controllers in the system: AUTHOR
was developed by HP. FILES
Executable file. Device files. SEE ALSO
saconfig(1M), privileges(5), intro(7). sautil(1M)
All times are GMT -4. The time now is 04:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy