Sponsored Content
Full Discussion: RAID 0 for SSD
Special Forums Hardware Filesystems, Disks and Memory RAID 0 for SSD Post 302780583 by figaro on Thursday 14th of March 2013 06:01:29 PM
Old 03-14-2013
I was wondering about the situation when having two disks in RAID 0 setup, with one distinctly faster than the other. Would the faster disk be overkill, because the speed gain is not utilised to its full advantage? In other words, would software have to be written to use the faster disk more often?
 

8 More Discussions You Might Find Interesting

1. BSD

Using SSD in FreeBSD

Now that SSD drives are becoming mainstream, I had a few questions on installing a SSD drive in a FreeBSD environment. Can FreeBSD be made SSD aware, that is, somehow let FreeBSD know that reads and writes should be limited or deferred to extend the disk's life? Is there a setting for wear... (0 Replies)
Discussion started by: figaro
0 Replies

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

3. AIX

SSD with GPFS ?

Hi, does anyone here happen to know if I could run GLVM or GPFS on Solid State Disks? I have a high volume / high transaction Sybase HACMP cluster currently setup with SRDF to the DR datacentre. My business now considers to move everything to SSD storage but we still need to get the data to... (0 Replies)
Discussion started by: zxmaus
0 Replies

4. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies

5. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

6. Red Hat

RAID Configuration for IBM Serveraid-7k SCSI RAID Controller

Hello, I want to delete a RAID configuration an old server has. Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton? I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies

7. UNIX for Dummies Questions & Answers

What should I format my SSD with?

Hello All, I recently received a new SSD that I am going to use for the purpose of Booting Virtual Machines. I use VMWare Player to boot Windows Guest Operating Systems onto my Linux Laptop. I currently have a SSD drive that I use for this exact same purpose that is formatted as ext3 and I'm... (3 Replies)
Discussion started by: mrm5102
3 Replies

8. Linux

CentOS 6.6 SSD trim on HP DL380 G2 RAID 0

I'm running glusterfs on CentOS 6.6 two nodes, (the SSD (samsung 840 1TB x2) is RAID 0 on the HP DL380 G6) x2, and trimming is not enable on it by checking /dev/sdb1/xxxxx/discard_max_bytes=0. Do I still need trimming? Somehow my filesystem is fine with 35-30% free space and running very fast. ... (1 Reply)
Discussion started by: itik
1 Replies
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 01:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy