Sponsored Content
Operating Systems Solaris How can i grow Raid 5 volume in SVM..? Post 302240317 by incredible on Thursday 25th of September 2008 12:16:59 PM
Old 09-25-2008
Assuming you have created your RAID 5 like this:
metainit d6 -r /dev/dsk/c1t0d0s6 /dev/dsk/c2t0d0s6 /dev/dsk/c3t0d0s6 -i 8k
Can't you grow it simply by doing this:?
growfs -M /mountpoint /dev/md/rdsk/d6
Smilie
 

9 More Discussions You Might Find Interesting

1. Solaris

How do you remove a RAID 5 under SVM?

I have this setup, i can only find docs to unmirror a raid 1 set, how do you get rid of a raid 5 set? the same way? metadetach and metaclear? d8: RAID State: Okay Interlace: 32 blocks Size: 142245693 blocks (67 GB) Original device: Size: 142247872 blocks (67 GB) ... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies

2. Solaris

Disksuite Raid 0 Concatenated Volume - booting from cdrom

Hello, If I boot up from install media in single user mode (Solaris 9 - if it matters), will I be able to mount a concatenated volume? I have combined several disks into one non-os filesystem and I want to be able to mount it while booted in single user mode from cdrom. i.e., mount... (0 Replies)
Discussion started by: calmgreen
0 Replies

3. Solaris

how to get back a SVM volume to solaris control

hi.., help me in this case... 1) now the disk is under disksuite, its have some mirrored volume. how can i get back this disk to OS control. 2) how can i know the a SVM volume avalable,used space. and the filesystem size on tht volume please help in this i am bigginer... (5 Replies)
Discussion started by: b.janardhanguru
5 Replies

4. Solaris

RAID controller needed for SVM?

hi this may be a very stupid question, but im quite new to Solaris (gonna buid my first system, Solaris 10 on x86 system, connected to other windows systems in a home network) i wanna put a RAID 5 system in there to back up my other systems at home; iv read that its really so easy with SVM to... (4 Replies)
Discussion started by: Landser
4 Replies

5. Solaris

ZFS and SVM - volume management

pupp, thanks for the information. but is its integrated volume management better than SVM that we use (with ufs i believe)? (2 Replies)
Discussion started by: StarSol
2 Replies

6. Solaris

Setting up bootblock on RAID 0 SVM

Hi All! I'm running Solaris 10 and SPARC and using Let me give a bit of background before asking my question: I have created a RAID 0 (stripe) on 2 disks, I have the OS running on a third disk and I have now performed a ufsdump / ufsrestore from my third disk to the RAID 0 disks... (7 Replies)
Discussion started by: Keepcase
7 Replies

7. UNIX for Dummies Questions & Answers

Help to Grow the Size of volume

I have a 146Gb drive and want to grow the size from 12G to the max available left. I think 20G is being used so I want to max out from 12 G to 126G. Is this possible? Can you help with the command. root@WRPDWI6k-BU # df -h Filesystem size used avail... (3 Replies)
Discussion started by: udubya
3 Replies

8. Solaris

Grow / expand a ZFS volume

Hi, I need to expand a ZFS volume from 500GB to 800GB. I'd like to ask your help to confirm the following procedure: Can I do it on the fly without bothering the users working on this volume? Thank you in advance! (6 Replies)
Discussion started by: aixlover
6 Replies

9. Solaris

2540 volume expand and solaris zfs grow

Hello I hope everyone is having a good day! Situation: 2540 with 3.6TB of usable space volume A is 2.6TB volume B was 1TB Volume A is mounted via a single lun on a solaris server and is running out of space. Volume B was used on another server but is no longer, I deleted the volume in... (7 Replies)
Discussion started by: Metasin
7 Replies
volfs(7FS)                                                         File Systems                                                         volfs(7FS)

NAME
volfs - Volume Management file system DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be /vol for this description. Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a particular piece of hardware). Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk provides character access to random access devices. The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a volume will be the same for both the block and character device. The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777, owner=root, group=sys. Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per- missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys. mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc- tory permissions. The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2). If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the following /vol locations: +-----------------------------------+------------------------------------+ | Location | State of Media | +-----------------------------------+------------------------------------+ |/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block | | | device access | +-----------------------------------+------------------------------------+ |/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw | | | device access | +-----------------------------------+------------------------------------+ |/vol/dev/diskette0/unlabeled | unlabeled floppy-block device | | | access | +-----------------------------------+------------------------------------+ |/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access | +-----------------------------------+------------------------------------+ |/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access | +-----------------------------------+------------------------------------+ |/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access | +-----------------------------------+------------------------------------+ For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M). Partitions Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory. For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then: /vol/dsk/foo/s0 /vol/dsk/foo/s2 /vol/dsk/foo/s5 for block access and /vol/rdsk/foo/s0 /vol/rdsk/foo/s2 /vol/rdsk/foo/s5 for character access. If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout. A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management, however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated and the user may cancel the operation with volcancel(1), if desired. SEE ALSO
volcancel(1), volcheck(1), volmissing(1) rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4) System Administration Guide: Basic Administration SunOS 5.10 8 Feb 1995 volfs(7FS)
All times are GMT -4. The time now is 10:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy