Sponsored Content
Full Discussion: Raid 0 stripe size
Operating Systems Linux Raid 0 stripe size Post 302347228 by supermiguel on Tuesday 25th of August 2009 09:47:13 AM
Old 08-25-2009
i do my backups on a raid 5 (3x500gb)... So this perc 5 card, has 3x 36g (15K) hds in raid 0, and a raid 5 of 3x500gb, where my data is going to go. So?? best stripe for raid 0? 128k?

---------- Post updated at 09:47 AM ---------- Previous update was at 07:39 AM ----------

any one?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

MSR magnetic stripe card reader

Hi all I am working on MSR110 ...Can anyone plz tell me how to use the configuration commands with magnetic reader???. Please help me out as i have to develop API in C on linux platform.MSR110 is not responding to the configuration commands. Please help... Regards Mahima (0 Replies)
Discussion started by: mahima_er
0 Replies

2. UNIX for Advanced & Expert Users

Resizing veritas mirror-stripe volume

Hi, Is there are any special preocedure for extending veritas mirror-stripe volume? In my case , volume lay out looks as below v test - ENABLED ACTIVE 419430400 SELECT - fsgen pl test-01 test ENABLED ACTIVE 419454720 STRIPE 3/128 RW sd... (0 Replies)
Discussion started by: 2k7.vipin
0 Replies

3. AIX

AIX striped LV - lslv stripe width has wrong value

Hello all. I have a volume group with 8 PV's, and a logical volume striped across these 8 volumes. However, an lslv is showing: STRIPE WIDTH: 9 STRIPE SIZE: 64k There's really only eight disks, so how can the stripe width be 9? ODM also showed this: # odmget CuAt |... (4 Replies)
Discussion started by: Scott
4 Replies

4. Emergency UNIX and Linux Support

AIX : Create LV with poor man stripe

Hi all I have just had SAN allocate 4*30 GB of disks and had created a new scalable vg and assigned the disks to it: I used smitty to create vg and the command is: x -y'vgdata1' hdisk82 hdisk83 hdisk84 hdisk85 root@aadcxs08 / : lsvg vgdata1 VOLUME GROUP: vgdata1 VG... (4 Replies)
Discussion started by: hedkandi
4 Replies

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

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

7. Solaris

solaris volume manager- stripe?

Hello Admins.. I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation. There is an eample for concatenation: # metainit d25 1 1 c0t1d0s2 d25: Concat/Stripe is setup the... (5 Replies)
Discussion started by: snchaudhari2
5 Replies

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

9. Shell Programming and Scripting

awk or sed or any commands to stripe data

Say i have: g_gateway domain="abc.com" to="123.123.123.123" relay="false" how do i use awk or sed or any method to get the result below: abc.com 123.123.123.123 (3 Replies)
Discussion started by: timmywong
3 Replies
LVS(8)							      System Manager's Manual							    LVS(8)

NAME
       lvs - report information about logical volumes

SYNOPSIS
       lvs  [-a|--all] [--aligned] [-d|--debug] [-h|-?|--help] [--ignorelockingfailure] [--nameprefixes] [--noheadings] [--nosuffix] [-o|--options
       [+]Field[,Field]] [-O|--sort [+|-]Key1[,[+|-]Key2[,...]]]  [-P|--partial]  [--rows]  [--segments]  [--separator	Separator]  [--unbuffered]
       [--units hHbBsSkKmMgGtTpPeE] [--unquoted] [-v|--verbose] [--version] [VolumeGroupName [VolumeGroupName...]]

DESCRIPTION
       lvs produces formatted output about logical volumes.

OPTIONS
       See lvm(8) for common options.

       --all  Include information in the output about internal Logical Volumes that are components of normally-accessible Logical Volumes, such as
	      mirrors, but which are not independently accessible (e.g. not mountable).  The names of such Logical  Volumes  are  enclosed  within
	      square  brackets in the output.  For example, after creating a mirror using 'lvcreate -m1 --mirrorlog disk', this option will reveal
	      three internal Logical Volumes, with suffixes mimage_0, mimage_1, and mlog.

       --aligned
	      Use with --separator to align the output columns.

       --nameprefixes
	      Add an "LVM2_" prefix plus the field name to the output.	Useful with --noheadings to produce a list of field=value pairs  that  can
	      be used to set environment variables (for example, in udev(7) rules).

       --noheadings
	      Suppress the headings line that is normally the first line of output.  Useful if grepping the output.

       --nosuffix
	      Suppress the suffix on output sizes.  Use with --units (except h and H) if processing the output.

       -o, --options
	      Comma-separated ordered list of columns.	Precede the list with '+' to append to the default selection of columns instead of replac-
	      ing it.

	      Use -o lv_all to select all logical volume columns, and -o seg_all to select all logical volume segment columns.

	      Use -o help to view the full list of columns available.

	      Column names include: lv_uuid, lv_name, lv_path,	lv_attr,  lv_major,  lv_minor,	lv_read_ahead,	lv_kernel_major,  lv_kernel_minor,
	      lv_kernel_read_ahead, lv_size, seg_count, origin, origin_size, snap_percent, copy_percent, move_pv, convert_lv, lv_tags, mirror_log,
	      thin_pool, modules, segtype, stripes, stripesize, regionsize, chunksize, seg_start, seg_start_pe, seg_size, seg_tags, seg_pe_ranges,
	      devices.

	      With  --segments, any "seg_" prefixes are optional; otherwise any "lv_" prefixes are optional.  Columns mentioned in vgs(8) can also
	      be chosen.

	      The lv_attr bits are:

	      1  Volume type: (m)irrored, (M)irrored without initial sync, (o)rigin, (O)rigin with merging snapshot, (r)aid, (R)aid  without  ini-
		 tial  sync, (s)napshot, merging (S)napshot, (p)vmove, (v)irtual, mirror or raid (i)mage, mirror or raid (I)mage out-of-sync, mir-
		 ror (l)og device, under (c)onversion, thin (V)olume, (t)hin pool, (T)hin pool data, raid or thin pool m(e)tadata

	      2  Permissions: (w)riteable, (r)ead-only, (R)ead-only activation of non-read-only volume

	      3  Allocation policy: (c)ontiguous, c(l)ing, (n)ormal, (a)nywhere, (i)nherited This is capitalised if the volume is currently locked
		 against allocation changes, for example during pvmove(8).

	      4  fixed (m)inor

	      5  State:  (a)ctive,  (s)uspended,  (I)nvalid  snapshot,	invalid  (S)uspended snapshot, snapshot (m)erge failed, suspended snapshot
		 (M)erge failed, mapped (d)evice present without tables, mapped device present with (i)nactive table

	      6  device (o)pen

	      7  Target type: (m)irror, (r)aid, (s)napshot, (t)hin, (u)nknown, (v)irtual.  This groups logical volumes related to the same  kernel
		 target  together.  So, for example, mirror images, mirror logs as well as mirrors themselves appear as (m) if they use the origi-
		 nal device-mapper mirror kernel driver; whereas the raid equivalents using the md raid kernel driver all appear  as  (r).   Snap-
		 shots	using  the  original device-mapper driver appear as (s); whereas snapshots of thin volumes using the new thin provisioning
		 driver appear as (t).

	      8  Newly-allocated data blocks are overwritten with blocks of (z)eroes before use.

       --segments
	      Use default columns that emphasize segment information.

       -O, --sort
	      Comma-separated ordered list of columns to sort by.  Replaces the default selection. Precede any column with - for a reverse sort on
	      that column.

       --rows Output columns as rows.

       --separator Separator
	      String to use to separate each column.  Useful if grepping the output.

       --unbuffered
	      Produce output immediately without sorting or aligning the columns properly.

       --units hHbBsSkKmMgGtTpPeE
	      All  sizes  are  output  in  these  units: (h)uman-readable, (b)ytes, (s)ectors, (k)ilobytes, (m)egabytes, (g)igabytes, (t)erabytes,
	      (p)etabytes, (e)xabytes.	Capitalise to use multiples of 1000 (S.I.) instead of 1024.  Can also specify custom units e.g. --units 3M

       --unquoted
	      When used with --nameprefixes, output values in the field=value pairs are not quoted.

SEE ALSO
       lvm(8), lvdisplay(8), pvs(8), vgs(8)

Sistina Software UK					 LVM TOOLS 2.02.95(2) (2012-03-06)						    LVS(8)
All times are GMT -4. The time now is 08:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy