01-07-2009
How to create metadb when there is no free slice
Hi All,
I have to do disk mirroring, for that I have to create a metadb as disk mirroring have to do with SVM. However I do not have any slice free for metadb.
What are the options? Please suggest
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm interested in adding more swap space to my current workstation (Solaris 10). I currently have 2 hard drives installed, however the system was only created with 512MB for swap that resides on drive 1. This drive is already sliced up and all slices are being used.
The second drive has two... (3 Replies)
Discussion started by: here2learn
3 Replies
2. Solaris
Hi there
I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
3. BSD
Now, I had installed free bsd at my office. Unfortunitely, Email server have been using Local PoP3 and SMTP to our ISP with outlook. but my unix firewall sever ( free bsd ) didn't allow these port ( 110 & 25 ).
How can i create the IP table to pass at server. If u have any experience about obvious... (4 Replies)
Discussion started by: Ashraff Ali
4 Replies
4. Linux
We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies
5. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
6. Solaris
Hi Gurus,
For a particular slice I have change the minfree from 10% to 1% with tunefs -m and its allowing the creation of file on that slice, however when I am seeing the same with df -k it says that the slice is 100% full.
What could be reason for this?
Thanks (2 Replies)
Discussion started by: kumarmani
2 Replies
7. Solaris
Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes?
zpool status
pool: rpool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool1 ONLINE 0 0 0
c4t1d0s0 ... (10 Replies)
Discussion started by: incredible
10 Replies
8. Solaris
Hi,
I have inherited a system with two disks mirrored, and only 1 metadb on each, I have deleted the db on c1t1 and recreated 3 which is fine.
But when it comes to c1t0, the metadb -d /dev/dsk/c1t0d0s5 doesnt removed the existing db and the create metadb -a -f -c3 /dev/dsk/c1t0dos5 wont... (0 Replies)
Discussion started by: richard.tarlton
0 Replies
9. Solaris
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
10. Solaris
I have a 240GB disk as rpool. I have installed Solaris 11.3 to a partition which is 110GB. Now I have another 130GB which is unallocated. I want to use that additional space as a temporary folder to be shared between Solaris and Linux. The additional space had no /dev/dsk/c2t4... entry so I used... (8 Replies)
Discussion started by: kebabbert
8 Replies
LEARN ABOUT OSF1
volmirror
volmirror(8) System Manager's Manual volmirror(8)
NAME
volmirror - Mirrors volumes on a disk or control default mirroring
SYNOPSIS
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] medianame [new_medianame...]
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] -a [new_medianame...]
/usr/sbin/volmirror [-g diskgroup] [-d yes|no]
/usr/sbin/volmirror [-g diskgroup] -D
OPTIONS
The volmirror command supports the following options: Limits operation of the command to the given disk group, as specified by disk group
ID or disk group name. The medianame operands will be evaluated relative to the given disk group. If no disk group is supplied to the
volmirror command, rootdg is presumed. Changes the default for subsequent volume creation, depending on the option argument. If the option
argument is yes, all subsequent volumes created using the volassist command will automatically be created as mirrored volumes. If the
option argument supplied is no, mirroring will be turned off for future volumes by default. Displays current default status for mirroring.
Mirrors all existing volumes for the specified disk group.
DESCRIPTION
The volmirror command provides a mechanism to mirror all the contents of a specified disk, to mirror all currently unmirrored volumes in
the specified disk group, or to change or display the current defaults for mirroring. All volumes that have only a single plex (mirror
copy), will be mirrored by adding an additional plex.
Volumes containing subdisks that reside on more than one disk will not be mirrored by volmirror.
The volmirror command is generally called from the voldiskadm menus. It is not an interactive command and once called, will continue until
completion of the operation or until a failure is detected.
Note
Due to the nature of generating mirror copies of volumes, this command may take a considerable time to complete.
In the first listed form of the command, the disk media name is supplied on the command line to volmirror. That name is taken to be the
only disk from which volumes should be mirrored. In the case of mirroring volumes from a specified disk, only simple single-subdisk volumes
are mirrored.
In the first and second listed forms of the command, the new_medianame ... parameter identifies a new disk media name (or set of names).
The mirroring operation being performed will use these names as targets on which to allocate the mirrors. An error will result if the same
disk is specified for both the source and target disk and if no other viable targets are supplied.
EXAMPLES
The following are examples of the use of the volmirror command. The following command mirrors the contents of the disk named disk01 to any
available space on any available disk. Subsequent calls to volassist will cause created volumes to be mirrored by default. volmirror -d
yes disk01 The following command displays the current status of default mirroring. It prints the string yes if mirroring is currently
enabled or no, if not. volmirror -D The following command mirrors any volumes on disk02 onto disk03. volmirror disk02 disk03
FILES
The defaults file for volassist parameters.
SEE ALSO
volintro(8), volassist(8), volrootmir(8)
volmirror(8)