Sponsored Content
Full Discussion: Disk Suite issue
Operating Systems Solaris Disk Suite issue Post 302164369 by BOFH on Monday 4th of February 2008 04:14:36 PM
Old 02-04-2008
Disk Suite issue

Solaris 9

We had a problem server where only root was not mirrored (before my time). When I tried to mirror it, the live root slice bailed with errors at 97% so it couldn't be mirrored.

It's a matched pair of boxes (nfs1 and nfs2) and they are interchangeable with regards to the NFS functions. The slices are the same on all four disks (two mirrored disks in each system).

Since c1t0 on nfs2 was failing and we couldn't mirror it to c1t1, I broke the mirror on nfs1. We took c1t1 out of nfs2 and put it in c1t0's slot. We took c1t1 out of nfs1 and after changing the network information, /etc/system and /etc/vfstab, put it in c1t1 of nfs2.

The box booted fine and is accessible from the 'net. Because we wanted to save the data on c1t0, I modified vfstab to mount c1t1d0s0, c1t1d0s1, c1t0d0s3, c1t0d0s4, c1t0d0s5 and c1t0d0s6. The system rebooted again without a problem.

Problem:

Now I'm trying to mirror the system again. The problem is that I'm getting:

Code:
# metadb -f -a -c 2 c1t0d0s7 c1t1d0s7
metadb: nfs2: Bad address

I did some 'net surfing and didn't find anything that fit into my problem. Basically, there's a config file somewhere with the metainfo from nfs1 that needs to be cleared out.

I've looked at /kernel/drv/md.conf and even copied the file from c1t0. I checked /etc/lvm and removed the metastat info from md.cf since it was inaccurate.

I commented out the meta tools from /etc/inetd.conf and renamed the svm scripts so they wouldn't start.

On boot, I get a

Code:
metainit: nfs2: Bad address

so there's something somewhere that's still holding on to a nfs1 address.

Suggestions for other places to look?

Thanks.

Carl
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disk Suite on Solaris 7

Does anyone know which packages I need to install to run Disk Suite on Solaris 7, or where I can find some documentation? (2 Replies)
Discussion started by: 98_1LE
2 Replies

2. Filesystems, Disks and Memory

Installing DISKS with Solaris Disk Suite

Hi, Ihave a Netra T1405 and would like to add 2 news disk (in mirror with SDS) in order to grow the size of the initial file system. The idea is to mount a new partition in order to setup new products... Could some one tell me the difrents steps to do this or give me links to documents. ... (1 Reply)
Discussion started by: guillaume35
1 Replies

3. UNIX for Dummies Questions & Answers

Size limitations with ufs/disk suite on Solaris 8?

I tried to build a 1.3 TB volume with disk suite, and recieved an error (don't remember the exact verbage, it was very late). It only built a 1 TB volume. newfs completed without error. I rebuilt the volume to be just under 1TB, and all was fine. Is there a limitation with disk suite, or ufs, that... (3 Replies)
Discussion started by: 98_1LE
3 Replies

4. Solaris

Solaris Disk Suite

Hi I'm completely new to Solaris Disk Suite. Where can I go and read up about it. I've seen consultants run the meta- commands, but it doesn't make any sense to me. I would like to learn how it works and how to use it. Thanks (1 Reply)
Discussion started by: soliberus
1 Replies

5. Solaris

Mirroring 2 disks with Solstice Disk Suite

hello everybody, I have a system in Solaris 8 with SDS 4.2.1 I need to mirror the system disk which has the following characteristics : * /dev/rdsk/c0t0d0s2 partition map * * Dimensions: * 512 bytes/sector * 133 sectors/track * 27 tracks/cylinder * 3591 sectors/cylinder... (3 Replies)
Discussion started by: aribault
3 Replies

6. AIX

disk issue

Hi, I have a AIX 4.3 box here with problems cause of a disk in below VG. volume group: workvg lspv hdisk4 000166789869ab2d workvg hdisk5 000166789869b96b workvg now hdisk4 disk has failed and cause the quorum was set, workvg became varied off. I have to replace the... (2 Replies)
Discussion started by: karthikosu
2 Replies

7. UNIX for Dummies Questions & Answers

disk suite to mirror both d0 and d2

I have 2 drives on a sun solaris 8 server that is a live server. I am putting in an additional 2 drives and want to mirror the the first 2. I was thinking of using disksuite but one drive is the root drive with 1 maybe 2 free paritions. The other is only one partition (36G). I was wondering... (2 Replies)
Discussion started by: csgonan
2 Replies

8. Solaris

Please help Disk Suite on Solaris 8 FS full!!!

I am new to Solaris so please bear with me. I have spent enough time searching to get somewhat of a grip here but I am not sure what to do next. I am trying to grow a file system on a Solaris 8 server. B_root@server:>df -k Filesystem kbytes used avail capacity Mounted on... (9 Replies)
Discussion started by: NewSolarisAdmin
9 Replies

9. AIX

Disk I/O Issue

We have a filesystem which contains 8 hard disks but i am facing disk I/O issue becuase data is not spreading across all the disks.Is there any way i can check how data is spreading and any parameter we need to change to spread ata across all disks. OS--AIX 5.3 (3 Replies)
Discussion started by: ukatru
3 Replies

10. Solaris

Solstice Disk Suite

I am doing disk mirroring and this command I entered: metainit d202 1 1 c0t1d0s0 gives me this error "metainit: d202: no such file or directory" The nmd value in /kernel/drv/md.conf is set to 2000. Any ideas what this error means? (3 Replies)
Discussion started by: bluridge
3 Replies
metaroot(1M)															      metaroot(1M)

NAME
metaroot - setup system files for root (/) metadevice SYNOPSIS
/usr/sbin/metaroot -h /usr/sbin/metaroot [-n] [-k system-name] [-v vfstab-name] [-c mddb.cf-name] [-m md.conf-name] [-R root-path] device The metaroot command edits the /etc/vfstab and /etc/system files so that the system may be booted with the root file system (/) on an appropriate metadevice. The only metadevices that support the root file system are a stripe with only a single slice or a mirror on a sin- gle-slice stripe. If necessary, the metaroot command can reset a system that has been configured to boot the root file system (/) on a metadevice so that it uses a physical slice. Root privileges are required for all of the following options except -h. The following options are supported: -c mddb.cf-name Use mddb.cf-name instead of the default /etc/lvm/mddb.cf file as a source of metadevice database locations. -h Display a usage message. -k system-name Edit a user-supplied system-name instead of the default /etc/system system configuration information file. -m md.conf-name Edit the configuration file specified by md.conf-name rather than the default, /kernel/drv/md.conf. -n Print what would be done without actually doing it. -R root-path When metaroot modifies system files, it accesses them in their relative location under root-path. The -R option cannot be used in combination with the -c, -k,-m, or -v options. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -v vfstab-name Edit vfstab-name instead of the default /etc/vfstab table of file system defaults. The following operands are supported: device Specifies either the metadevice or the conventional disk device (slice) used for the root file system (/). Example 1: Specifying Root File System on Metadevice The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on metadevice d0. # metaroot d0 Example 2: Specifying Root File System on SCSI Disk The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on the SCSI disk device /dev/dsk/c0t3d0s0. # metaroot /dev/dsk/c0t3d0s0 /etc/system System configuration information file. See system(4). /etc/vfstab File system defaults. /etc/lvm/mddb.cf Metadevice state database locations. /kernel/drv/md.conf Configuration file for the metadevice driver, md. The following exit values are returned: 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(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) 6 Apr 2005 metaroot(1M)
All times are GMT -4. The time now is 10:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy