Sponsored Content
Operating Systems Solaris How to create metadb with zpool in Solaris 11 Post 302553555 by incredible on Thursday 8th of September 2011 01:34:50 AM
Old 09-08-2011
When I installed the OS, I used the whole disk and did not partition with UFS.
So how can I now slice it?
 

10 More Discussions You Might Find Interesting

1. Solaris

solaris with metadb

Hi All, If solaris has metadb services on the disk, it means that it has a HW raid controller. Or what. Thanks in advance. (1 Reply)
Discussion started by: itik
1 Replies

2. Solaris

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 (4 Replies)
Discussion started by: kumarmani
4 Replies

3. Solaris

zpool create - long time creation

Hello, I have a 520GB SAN resource connected to the server via FC (4Gbit). In the next step he wants to create pool storage: After 15 hours Pool has not yet created... Is such a long waiting time is normal? Should I have done? Regards (1 Reply)
Discussion started by: bieszczaders
1 Replies

4. Solaris

Increase root filesystem on solaris zone using zpool

I have a solaris zone of 12 GB and i have to increase the / filesystem to 31GB as requested. Earlier I had expanded filesystems other than / by setting quota to new value like "zfs set quota=new value mountpoint" but I am not sure whether its a good practice in zfs because by default in my... (5 Replies)
Discussion started by: vikkash
5 Replies

5. BSD

Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset

I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error: # zpool create zfspool /dev/da0s1a cannot create 'zfspool': no such pool or dataset # zpool create zfspool /dev/da0 cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies

6. Solaris

Check Solaris VM Databases metadb does not have enough information about logical volumes

Check Solaris VM Databases metadb does not have enough information about logical volumes. Current value is 0% I have checked the SVM status, all disks are good state and synched perfectly. no errors in metadb -i. what is this alert exact mean? what we have to check for the value? Please... (1 Reply)
Discussion started by: Naveen.6025
1 Replies

7. Solaris

Upgrading Solaris - what happens to zpool/zfs versions

Hi everyone, I'm hoping someone can help me out here. I've googled lots and don't think I can find an easy answer to this. We're in the process of upgrading Solaris from v10 5/08 to v10 9/10. The zpools for luns are currently at version 10, and I understand Solaris v10 9/10 has support for... (3 Replies)
Discussion started by: badoshi
3 Replies

8. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
2 Replies

9. Solaris

Solaris 10 Volume Manager - adding slice to metadb

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

Solaris can not boot because metadb lost

how to recovery metadb? Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
extendfs(8)						      System Manager's Manual						       extendfs(8)

NAME
extendfs - Extends UFS file systems SYNOPSIS
/sbin/extendfs [- s] [disk_blocks] device_name DESCRIPTION
Use the extendfs command to increase the storage space in a UFS file system. The file system must not be mounted when you perform this operation. To extend a mounted (in use) UFS file system, use the mount command with the -o extend option. The procedure for increasing the storage space of a UFS file system is as follows: Look at the contents the /etc/fstab file to identify the disk partition that maps to the file system. Ensure that there is available storage space on the target disk as follows: If LSM is in use on your system, use LSM commands to increase the size of the LSM volume as described in the Logical Storage Manager guide. If LSM is not in use on your system, use the disklabel command or the diskconfig graphical user interface to check the current size and use of partitions on the disk. If there is adequate space on an adjacent partition, use the disklabel command to write the current label to a file as fol- lows: # disklabel -r dsk4 > d4label Edit the disklabel file to change the size of the partition on which your UFS file system resides. Increase the number of disk blocks on the partition and decrease the disk block size of the adjacent partition by an equivalent number. Use the disklabel command with the -R option to write the revised label to the raw disk as follows: # disklabel -R /dev/rdisk/dsk4 d4label When the disk label is revised, extend the file system using the extendfs command. You can either use the full extent of the newly sized partition or extend the file system in stages. The following example commands show both methods. To extend the file system to use all the available space, you specify the disk partition on which the file system resides, as follows: # extendfs /dev/disk/dsk4g To extend the file system to use only part of the available space, you specify a number of disk blocks, as follows: # extendfs -s 300000 /dev/disk/dsk4g The remainder of the extended partion is reserved for future use. You can extend a file system as many times as necessary, up to the physical limit of the storage device. When no more space is available on the storage device, you must back up the file system using the dump command and restore the file system to a storage device that has more available space. Once you have extended a file system, the operation cannot be reversed except by a back up and restore operation. Use the dump command to back up the file system. You can then reset the partition sizes manually and restore the file system to the storage device. ERRORS
The disklabel command produces output similar to that of the newfs command. If a list of disk blocks is not displayed on the terminal, the command has failed. Verify the partition settings and the mount status of the target file system. The disklabel command does not permit you to overwrite a partition if it is in use. Refer to the disklabel(8) reference page for more information on label errors. FILES
Specifies the command path. RELATED INFORMATION
diskconfig(8), disklabel(8), mount(8), and fstab(4). extendfs(8)
All times are GMT -4. The time now is 02:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy