Solaris 8 metainit space issue


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris 8 metainit space issue
# 1  
Old 01-25-2017
Solaris 8 metainit space issue

I am trying to create soft partition

Code:
metaclear -r d109
metainit  d109 -p d100 -o 178423817 -b 33554432

Code:
After i did this i saw the df -k
/dev/md/dsk/d109           0 779600337       0     0%    /test


df -k shows that it is full? also i have tried adding no logging entry in /etc/vfstab but still the same .

Can some one help ? Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Space Issue

Hey Experts, I'm facing an issue related to space in the unix system. I have a mount point where 9.4 T is allocated. The entire mount point is filled and I can trace only for 6.7T but I could not located the rest of the space around 2T. I tried every single command to locate the file starting... (7 Replies)
Discussion started by: panknil
7 Replies

2. Solaris

metainit: Sol10: there are no existing databases

Hi Experts, I am in direction to mirror filesystem in solaris10. Many articles I've read but not much help. Everytime I issued command metainit I always get 'there are no existing databases'. I don't know which steps I missed. bash-3.2# metainit -f d11 1 1 c0t0d0s0 metainit: Sol10: there are... (3 Replies)
Discussion started by: Fandy Abdul
3 Replies

3. UNIX for Advanced & Expert Users

Swap space issue

I have Solaris-10 with mutiple zones running in it. My Big Brother monitoring is complaining for very less swap space available, but I am not able to find, what process has consumed its swap space and how to clear it. All zones including global server have almost blank /tmp with very less data.... (3 Replies)
Discussion started by: solaris_1977
3 Replies

4. HP-UX

Swap space issue.

Hi, I am not sure how many scripts / java processes running on my HP-UX server. I need to calculate the total heap of these processes. I then need to recommend increasing the swap memory to be increase and equal to total heap if that is the right concept. Currently we are facing... (2 Replies)
Discussion started by: mohtashims
2 Replies

5. Solaris

Metainit issue

Hi all, After setting up SUN cluster in two nodes, I created disksets and volumes in the servers. Everything wwas working well and perfect. Today, I created a diskset and added three disks to it. When trying to create a volume, I am getting the following error: lsun3175 /dev/rdsk->... (4 Replies)
Discussion started by: manojsomanath
4 Replies

6. Solaris

swap space issue

HI All, Recently during oracle install I realized that I did not have enough swap space. So I - 1. Created a swap file "swap_fille1" in /rpool using mkfile - # ls -ltr /rpool total 10487121 drwxr-xr-x 3 root root 3 Dec 21 12:09 boot drwxr-xr-x 2 root root ... (10 Replies)
Discussion started by: sumeet
10 Replies

7. Linux

Space bar issue in Vi editor on Linux - Solaris

Hi I have a process generating a file in Solaris. Now we have migrated the process to Linux. When we open the file in vi on solaris and hit space bar, it stops after reaching the end of line. But in linux it continues to go on the next line. So I want to know whether the difference is between the... (4 Replies)
Discussion started by: sudhamacs
4 Replies

8. UNIX for Dummies Questions & Answers

Need help with space issue

Ok, I have a drive on my unix system that looks like this: /dev/hd4 0.38 0.00 100% 4316 3% / I can't find any file on that drive that would account for the 400MB. How can I thoroughly find the culprit of this space? I've done ls -al, but don't see anything that... (1 Reply)
Discussion started by: bbbngowc
1 Replies

9. Solaris

metainit gives coredump

SunOS unknown 5.9 Generic_118558-10 sun4u sparc SUNW,Sun-Fire-880 I'm trying to set up mirroring and am running into a problem: As you can see, I set up the metadb, but am getting a coredump when running metainit. I saw this through google, but don't know the validity of it. Any ideas? #... (5 Replies)
Discussion started by: dangral
5 Replies

10. Solaris

metainit error

Hi I have a sun machine. Recently I have upgraded. After the upgradation I get this error when I reboot the system - metainit: <servername>: there are no existing databases The system is a standalone system and I don't want to configure any raid on this system. Also I have not tried... (1 Reply)
Discussion started by: RajaRC
1 Replies
Login or Register to Ask a Question
metarename(1M)						  System Administration Commands					    metarename(1M)

NAME
metarename - rename metadevice or switch layered metadevice names SYNOPSIS
/usr/sbin/metarename [-s setname] metadevice1 metadevice2 /usr/sbin/metarename [-s setname] [-f] -x metadevice1 metadevice2 /usr/sbin/metarename -h DESCRIPTION
There are two ways to use metarename, one with and one without the -x option. The first method (without -x) renames an existing metadevice to a new name. This makes managing the metadevice namespace easier. The metadevice being renamed cannot be mounted or open, nor can the new name already exist. For example, to rename a metadevice that contains a mounted file system, you would first need to unmount the file sys- tem. With the second way to use metarename, using the -x option, metarename switches (exchanges) the names of an existing layered metadevice and one of its subdevices. In Solaris Volume Manager terms, a layered metadevice can be either a mirror or a trans metadevice. The -x option enables you to switch the metadevice names of a mirror and one of its submirrors, or a trans metadevice and its master device. metarename -x makes it easier to mirror or unmirror an existing stripe or concatenation, and to remove a trans device. When used to mirror an existing stripe or concatenatation, you must stop access to the device. For example, if the device contains a mounted file system, you must first unmount the file system before doing the rename. You can also use the metarename -x command to untrans a trans metadevice from an existing device. This applies only to the master device. You cannot remove a logging device with metarename. Before you can rename a trans device, you must detach the logging device. Then you must stop access to the trans metadevice itself. You cannot rename or switch metadevices that are in an error state or that have subcomponents in an error state, or metadevices actively using a hot spare replacement. You can only switch metadevices that have a direct child/parent relationship. You could not, for example, directly exchange a stripe in a mirror that is a master device with the trans metadevice. You must use the -f flag when switching members of a trans metadevice. Only metadevices can be switched, not slices. OPTIONS
The following options are supported: -f Force the switching of trans metadevice members. -h Display a help message. -s setname Specifies the name of the diskset on which metarename will work. Using the -s option will cause the command to perform its administra- tive function within the specified diskset. Without this option, the command will perform its function on the local metadevices. -x Exchange the metadevice names metadevice1 and metadevice2. metadevice1 Specifies the metadevice to be renamed or switched. metadevice2 Specifies the target metadevice name for the rename or switch operation. EXAMPLES
Example 1: Renaming a Metadevice This example renames a metadevice named d10 to d100. Note that d100 must not exist for the rename to succeed. # metarename d10 d100 Example 2: Creating a Two-Way Mirror This example creates a two-way mirror from an existing stripe named d1 with a mounted file system, /home2. # metainit d2 1 1 c13d0s1 # metainit -f d20 -m d1 # umount /home2 # metarename -x d20 d1 # metattach d1 d2 # mount /home2 First, a second concatenation d2, is created. (d1 already exists.) The metainit command creates a one-way mirror, d20, from d1. Next, you umount the file system and switch d1 for d20, making d1 the top-level device (mirror). You attach the second submirror, d2, to create a two-way mirror. Lastly, you remount the file system. Example 3: Mounting a Mirrored File System on Stripe This example takes an existing mirror named d1 with a mounted file system, and ends up with the file system mounted on a stripe d1. # umount /fs2 # metarename -x d1 d20 # metadetach d20 d1 # metaclear -r d20 # mount /fs2 First, you unmount the file system, then switch the mirror d1 and its submirror d20. This makes the mirror into d20. Next, you detach d1 from d20, then delete the mirror d20 and its other submirror. You then remount the file system. Example 4: Deleting a Trans Metadevice This example deletes a trans metadevice named d10 while its mount point is /myhome. The master device, which is a stripe, is named d2. The logging device, also a stripe, is named d5. # umount /myhome # metadetach d10 # metarename -f -x d10 d2 # metaclear d2 # metaclear d5 # fsck /dev/md/dsk/d10 # mount /myhome You umount the file system first, then detach the trans metadevice's logging device. The trans metadevice is switched with the master device, making the trans metadevice d2 and the underlying stripe d10. You clear the trans metadevice d2 and the logging device d5. d10 must be fsck'd, and then the file system is remounted. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide LIMITATIONS
Renaming and exchanging metadevice names can only be used for metadevices. A physical slice cannot be renamed to a metadevice, nor can a metadevice be exchanged with a physical slice name. Metadevice names are strings of the pattern d<xyz> where xyz is a value between 0 and 8192. You cannot use logical names for metadevices. NOTES
Trans metadevices have been replaced by UFS logging. Existing trans devices are not logging--they pass data directly through to the under- lying device. See mount_ufs(1M) for more information about UFS logging. SunOS 5.10 8 Aug 2003 metarename(1M)