Sponsored Content
Full Discussion: RAID 0 for SSD
Special Forums Hardware Filesystems, Disks and Memory RAID 0 for SSD Post 302780533 by Corona688 on Thursday 14th of March 2013 03:56:05 PM
Old 03-14-2013
Depends for what purpose. It's hard to speak in generalities.
 

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
DH_SAMEVERSIONDEP(1)					User Contributed Perl Documentation				      DH_SAMEVERSIONDEP(1)

NAME
dh_sameversiondep - generate versioned dependency based on the versioned dependencies of the reference package. SYNOPSIS
dh_sameversiondep [debhelper options] DESCRIPTION
dh_sameversiondep is a helper tool which is able to generate a dependency that is versioned the same way as a dependency (coming from the same source) of another reference package. dh_sameversiondep scans debian/control for the specially formatted substvar (see "sameVersionDep substvar SPECIFICATION" section below), determines its value and writes it to debian/package.substvars file. The most common use case for dh_sameversiondep tool is to keep your liba-dev package dependency on the external libb-dev package as tight as your liba package depends on the respective external libb package (see "EXAMPLE" section for more information about this use case). dh_sameversiondep works as follows: o Searches for the sameVersionDep substvar in the Depends, Recommends, Suggests, Enhances and Pre-Depends fields of the requested packages. When one is found, it is parsed and the dependency package name, reference package name and dependency type (either Depends or Recommends etc.) are determined. o All dependencies of the requested type are collected for the dependency package based on the dpkg-query --status output. o All dependencies of the requested type are collected for the reference package either from debian/control (substvars are expanded) or from dpkg-query --status output if the package was not found in debian/control. o Both collections are intersected leaving only common packages in both collections. o Common package list is filtered by leaving only those which come from the same source as dependency package. o Whatever packages are left (most likely only one), their names are replaced with dependency package name preserving all versioning information. This result is written to debian/package.substvars file as a value of the sameVersionDep substvar being processed. dh_sameversiondep is very strict about errors. If either dependency package or the reference package cannot be found or the resulting dependency set is empty, it will fail with an error. dh_sameversiondep MUST be run before dh_gencontrol. However, it is recommended to run dh_sameversiondep after dh_shlibdeps. sameVersionDep substvar SPECIFICATION sameVersionDep substvar can appear in either Depends, Recommends, Suggests, Enhances or Pre-Depends field of any binary package. The field, which the substvar appears in, becomes the default dependency type for that substvar. sameVersionDep should be formatted as follows (everything is case sensitive): ${sameVersionDep:dependency[[:reference]-dependency type]} dependency (mandatory) The name of the package which you want to add as a dependency. reference (optional) The name of the package which dependencies are to be intersected with the dependencies of the dependency package. Defaults to the first package in debian/control if ommited. dependency type (optional) Can be either Depends, Recommends, Suggests, Enhances or Pre-Depends. Defaults to the name of the field which the substvar was found in. Specifies which type of dependencies to consider when analyzing dependency package and reference package. EXAMPLE
Assume we have the following in debian/control: Package: liba Depends: libc (>= 0.1), depa, depb, depc Package: libb Depends: libd (>= 0.2), depd, depe, depf Package: libab-dev Depends: ${sameVersionDep:libc-dev}, ${sameVersionDep:libd-dev:libb} Assumming that libc and libc-dev (both from the same source), as well as libd and libd-dev (both from the same source) are installed, the value of "sameVersionDep:libc-dev" will be libc-dev (>= 0.1) and the value of "sameVersionDep:libd-dev:libb" will be libd-dev (>= 0.2). "sameVersionDep:libc-dev" could also be written as "sameVersionDep:libc-dev:liba-Depends" and "sameVersionDep:libd-dev:libb" as "sameVersionDep:libd-dev:libb-Depends" but it is not necessary because defaults are sufficient. SEE ALSO
debhelper(7) AUTHOR
Modestas Vainius <modax@debian.org> perl v5.14.2 2012-08-05 DH_SAMEVERSIONDEP(1)
All times are GMT -4. The time now is 02:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy