Sponsored Content
Operating Systems Solaris Software RAID on top of Hardware RAID Post 302582406 by fpmurphy on Thursday 15th of December 2011 08:32:37 PM
Old 12-15-2011
What not go the ZFS route instead? It gives you everything that Veritas Volume Manager or SVM provides and lots more.
 

9 More Discussions You Might Find Interesting

1. Solaris

Hardware RAID

I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies

2. Solaris

how to hardware RAID 1 on T5120

Hi, I have t5120 sparc and I have 2 146 G drives in the system. I will be installing solaris 10 and also want the system mirrored using Hardware RAID "1" The System did come preinstalled as it comes from sun. I did not do much on it. I booted system using boot cdrom -s gave format... (6 Replies)
Discussion started by: upengan78
6 Replies

3. Solaris

T2000 Hardware RAID

Hi, I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds. I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this? AVAILABLE DISK SELECTIONS: 0.... (12 Replies)
Discussion started by: honmin
12 Replies

4. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

5. Solaris

Hardware Raid - LiveUpgrade

Hi, I have a question. Do LiveUpgrade supports hardware raid? How to choose the configuration of the system disk for Solaris 10 SPARC? 1st Hardware RAID-1 and UFS 2nd Hardware RAID-1 and ZFS 3rd SVM - UFS and RAID1 4th Software RAID-1 and ZFS I care about this in the future to take... (1 Reply)
Discussion started by: bieszczaders
1 Replies

6. Hardware

Sun T3-1 hardware RAID

Hi all I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS. The documentation doesn't make it clear if: 1. The... (6 Replies)
Discussion started by: soliberus
6 Replies

7. Solaris

Hardware to software RAID migration

We have hardware RAID configured on our T6320 server and two LDOMs are running on this server. One of our disk got failed and replaced. After replacemnt the newly installed disk not detected by RAID controlled so Oracle suggested to upgrade the REM firmware. As this is the standalone production... (0 Replies)
Discussion started by: rock123
0 Replies

8. Solaris

Hardware raid patching

Dear All , we have hardware raid 1 implemented on Solaris Disks. We need to patch the Servers. Kindly let me know how to patch hardware raid implemented Servers. Thanks... Rj (7 Replies)
Discussion started by: jegaraman
7 Replies

9. Solaris

Hardware RAID using three disks

Dear All , Pl find the below command , # raidctl -l Controller: 1 Volume:c1t0d0 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.3.0 # raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 Replies
re(7)							 Miscellaneous Information Manual						     re(7)

NAME
re - SWXCR RAID interface SYNOPSIS
2100 Server Model A500MP DEC SWXCR controller xcrn at * vector xcintr device disk renn at xcrn drive nn DESCRIPTION
The re driver is for the SWXCR RAID Array controller. The following rules are used to determine the major and minor numbers that are associated with an re type disk. There are two major num- bers used to represent re disks. The major numbers are 11 for block devices and 44 for character (raw) devices. The minor number is used to represent both the unit number and partition. A disk partition refers to a designated portion of the physical disk. To accomplish this reference, the 20-bit minor number is divided into three parts. The lowest six bits of the minor number specify a disk partition. The partitions use a letter, a through h, for their name. The next three bits of the minor number specify the RE unit number for a unit attached to an SWXCR controller. The final 11 bits specify the controller number. The device special file names associated with re disks are based on conventions that are closely associated with the minor number assigned to the disk. The standard device names begin with re for block special files and rre for character (raw) special files. Following the re is the unit number and then a letter, a through h, that represents the partition. Throughout this reference page, the question mark (?) character represents the unit number in the name of the device special file. For example, re?b could represent re0b, re1b, and so on. The unit number can be calculated if the major and minor numbers of an re disk are provided. For example, suppose you have a device spe- cial file rre6a, with a major number of 44 and a minor number of 384. The partition is represented by the lower six bits of the number 384. These lower six bits of the number 384 are 0, which specifies the a partition. The next three bits of the minor number 384 specify the unit number, which is 6. The next eleven bits specify the controller number, which is zero. Putting these three pieces together reveals that the major/minor number pair 44/384 refers to the a partition of unit 6 attached to controller number 0. A disk can be accessed through either the block special file or the character special file. The block special file accesses the disk using the file system's normal buffering mechanism. Reads and writes to the block special file can specify any size. This capability avoids the need to limit data transfers to the size of physical disk records and to calculate offsets within disk records. The file system can break up large read and write requests into smaller fixed size transfers to the disk. The character special file provides a raw interface that allows for direct transmission between the disk and the user's read or write buf- fer. A single read or write to the raw interface results in exactly one I/O operation. Consequently, raw I/O may be considerably more efficient for large transfers. For systems with RE disks, the first software boot after the system is powered on may take longer than expected. This delay is normal and is caused by the software spinning up the RE disks. Disk Support The RE driver handles all disk drives that can be connected to the SWXCR controller. To determine which drives are supported for specific CPU types and hardware configurations, see the Installation and Configuration Guide for the StorageWorks RAID Array 200 Subsystem Family. SWXCR RAID Controllers are viewed in all cases as RE type disks. There are some notable differences that should be taken into considera- tion when configuring a RAID device: Currently only sector sizes of 512 bytes are supported. Logical Volume sizes are not fixed sizes as compared to other disk devices. The size of the Logical Volume is configurable based on needs. The dynamic nature of Logical Volume sizes is dealt with by defining RAID devices as DYNAMIC. Only partitions a, b, c, and g are defined. If necessary, the disklabel(8) command can be run to change and define partitions for RAID devices. Usually, the re?a partition is used for the root file system and the re?b partition as a paging area. The re?c partition can be used for disk-to-disk copying because it maps the entire disk. The starting location and length (in 512 byte sectors) of the disk partitions of each drive are shown in the following table. Partition sizes can be changed by using the disklabel(8) command. SWXCR (RAID) partitions for systems based on the Alpha AXP architecture disk start length re?a 0 131072 re?b 131072 262144 re?c 0 end of media re?d 0 0 re?e 0 0 re?f 0 0 re?g 393216 end of media re?h 0 0 FILES
/dev/re??? /dev/rre??? /etc/disktab RELATED INFORMATION
disklabel(8), MAKEDEV(8), uerf(8) delim off re(7)
All times are GMT -4. The time now is 01:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy