SVM - RAID 0 - Concatenation and Stripe Volumes 

This doesn't provide any redundancy but allows you to expand storage capacity. 

There are three of them: 

1. RAID-0 Stripe spreads data equally across all components (disk, slice or
 soft partition). 
2. RAID-0 Concatenation writes data to first available component and then 
moves to next one. 
3. RAID-0 Concatenated Stripe is stripe expanded by additional component. 

You will probably use these guys to create submirrors (in order to create 
mirrors later).  
 
RAID-0 cannot be used for FS that are used during OS upgrade/installation: 
/, /usr, /var, /opt, swap.

Logical data segments (define size in [K|M]bytes or blocks) of volume (RAID-0)
is called interlace. 
Different values can be used to adjust application I/O performance. Default 
is 16Kb (32 blocks).

Creating RAID-0

First you need state database replicas (let's create on 2 slices, total 6 
replicas). 





# metadb -afc 3  c1t0d0s7 c1t1d0s7
# metadb
        flags           first blk       block count
     a        u    r    16              8192            /dev/dsk/c1t0d0s7
     a        u    r    8208            8192            /dev/dsk/c1t0d0s7
     a        u    r    16400           8192            /dev/dsk/c1t0d0s7
     a        u    r    16              8192            /dev/dsk/c1t1d0s7
     a        u    r    8208            8192            /dev/dsk/c1t1d0s7
     a        u    r    16400           8192            /dev/dsk/c1t1d0s7






And get familiar (read man page) with command "metainit". 

Creating Stripe volume - example




# metainit d40 1 2 c1t1d0s4 c1t0d0s4
d40: Concat/Stripe is setup






d40 = volume/metadevice name
1 = number of stripe
2 = two components in stripe



# metastat
d40: Concat/Stripe
    Size: 8388252 blocks (4.0 GB)
    Stripe 0: (interlace: 32 blocks)
        Device     Start Block  Dbase   Reloc
        c1t1d0s4          0     No      No
        c1t0d0s4          0     No      No

Device Relocation Information:
Device   Reloc  Device ID
c1t1d0   No     -
c1t0d0   No     -






Creating Concatenation Volume - example 




# metainit d40 2 1 c1t1d0s4 1 c1t0d0s4
d40: Concat/Stripe is setup






2 = number of stripe
1 = one component per stripe  



# metastat
d40: Concat/Stripe
    Size: 8391888 blocks (4.0 GB)
    Stripe 0:
        Device     Start Block  Dbase   Reloc
        c1t1d0s4          0     No      No
    Stripe 1:
        Device     Start Block  Dbase   Reloc
        c1t0d0s4          0     No      No

Device Relocation Information:
Device   Reloc  Device ID
c1t1d0   No     -
c1t0d0   No     -






Creating new FS

Once you have metadevice, create FS. 



# newfs /dev/md/dsk/d40






Add line in /etc/vfstab file (table of file system defaults) and mount /.0



/dev/md/dsk/d40 /dev/md/rdsk/d40 /.0     ufs     2       yes     -






Expanding storage capacity for existing data

If you have RAID-0 volume (Concatenation or Stripe), you can expand it 
(convert it to concatenation stripe) - no need to reboot or unmount FS! 

Check what do you have. 



# metastat
d40: Concat/Stripe
    Size: 8388252 blocks (4.0 GB)
    Stripe 0: (interlace: 32 blocks)
        Device     Start Block  Dbase   Reloc
        c1t1d0s4          0     No      No
        c1t0d0s4          0     No      No

Device Relocation Information:
Device   Reloc  Device ID
c1t1d0   No     -
c1t0d0   No     - 






Say, stripe is mounted to /.0 file system. 



/dev/md/dsk/d40  3.9G   4.0M   3.9G     1%    /.0






Attach new slices to existing metadevice/volume 



# metattach d40 c1t1d0s5
d40: component is attached






Check what do you have now - see the size is bigger. 



# metastat
d40: Concat/Stripe
    Size: 18201816 blocks (8.7 GB)
    Stripe 0: (interlace: 32 blocks)
        Device     Start Block  Dbase   Reloc
        c1t0d0s4          0     No      No
        c1t1d0s4          0     No      No
    Stripe 1:
        Device     Start Block  Dbase   Reloc
        c1t1d0s5          0     No      No

Device Relocation Information:
Device   Reloc  Device ID
c1t0d0   No     -
c1t1d0   No     -






But your FS still shows same size. 



# df -h /.0
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d40        3.9G   4.0M   3.9G     1%    /.0






Grow the FS



# growfs -M /.0 /dev/md/rdsk/d40






-M = it does "write-lock" of mounted  FS when expanding

Now you have bigger FS. 



# df -h /.0
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d40        8.5G   8.7M   8.5G     1%    /.0






Deleting/Clearing volume (and its data)




# umount /.0

# metaclear d40
d40: Concat/Stripe is cleared

Comments

Post a Comment

Popular posts from this blog

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more

Restart autosys agent

#/etc/init.d/uajm_agent stop CA-UAJM Agent stopped. #/etc/init.d/uajm_agent start CA-UAJM Agent started. Follow the below workaround if the autosys agent does not start. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1.Run the command to check the status of both process, auto_remote and csampmuxf # ps -ef|grep 'auto'     root 14712     1  0   Aug 27 ?        2:42 auto_remote     root 27652     1  0 13:00:22 ?        0:00 auto_remote     root 27782     1  0 13:00:40 ?        0:00 auto_remote     root 29066 24480  0 13:01:07 pts/7    0:00 grep auto 2.There should be two entries for /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux status . If you see one entry then stop agent and check the autore...
Read more

How To Verify Remote System Controller (RSC) is Configured and Current on Sun Fire[TM] 280R/V480/V490/V880/V890 servers

Steps to Follow: How To Verify Remote System Controller(RSC) is Configured and Current 1.Check to see if the RSC software is already installed. # /usr/bin/pkginfo | grep SUNWrsc 2.If the software is installed the command should output the package name and info.   The version of the package installed in Solaris should match the version of firmware installed on the card.   `rscadm version` in Solaris will display the firmware version. 3.If the software is not installed the packages can be found on the supplemental CD that came with the Solaris Operating Environment. If you do not have the CD the software can be downloaded from MOS: RSC 2.2.2 is supported with Solaris 10, but you need to get this from a supplemental CD (for Solaris 9, since there is no supplemental CD for S10). The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are...
Read more