09-08-2011
One thing to add. You would have to check if there are blocks free on the disk, as you the metadb needs to be on its own slice.
10 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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. 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
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
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
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
how to recovery metadb?
Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
LEARN ABOUT SUNOS
addbadsec
addbadsec(1M) System Administration Commands addbadsec(1M)
NAME
addbadsec - map out defective disk blocks
SYNOPSIS
addbadsec [-p] [ -a blkno [blkno...]] [-f filename] raw_device
DESCRIPTION
addbadsec is used by the system administrator to map out bad disk blocks. Normally, these blocks are identified during surface analysis,
but occasionally the disk subsystem reports unrecoverable data errors indicating a bad block. A block number reported in this way can be
fed directly into addbadsec, and the block will be remapped. addbadsec will first attempt hardware remapping. This is supported on SCSI
drives and takes place at the disk hardware level. If the target is an IDE drive, then software remapping is used. In order for software
remapping to succeed, the partition must contain an alternate slice and there must be room in this slice to perform the mapping.
It should be understood that bad blocks lead to data loss. Remapping a defective block does not repair a damaged file. If a bad block
occurs to a disk-resident file system structure such as a superblock, the entire slice might have to be recovered from a backup.
OPTIONS
The following options are supported:
-a Adds the specified blocks to the hardware or software map. If more than one block number is specified, the entire list should be
quoted and block numbers should be separated by white space.
-f Adds the specified blocks to the hardware or software map. The bad blocks are listed, one per line, in the specified file.
-p Causes addbadsec to print the current software map. The output shows the defective block and the assigned alternate. This option
cannot be used to print the hardware map.
OPERANDS
The following operand is supported:
raw_device The address of the disk drive (see FILES).
FILES
The raw device should be /dev/rdsk/c?[t?]d?p0. See disks(1M) for an explanation of SCSI and IDE device naming conventions.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
disks(1M), diskscan(1M), fdisk(1M), fmthard(1M), format(1M), attributes(5)
NOTES
The format(1M) utility is available to format, label, analyze, and repair SCSI disks. This utility is included with the addbadsec,
diskscan(1M), fdisk(1M), and fmthard(1M) commands available for x86. To format an IDE disk, use the DOS "format" utility; however, to
label, analyze, or repair IDE disks on x86 systems, use the Solaris format(1M) utility.
SunOS 5.10 24 Feb 1998 addbadsec(1M)