Sponsored Content
Full Discussion: Solstice Disk Suite
Operating Systems Solaris Solstice Disk Suite Post 302330267 by DukeNuke2 on Tuesday 30th of June 2009 04:49:06 PM
Old 06-30-2009
you don't need to reboot to create metadevices... this is only for rootmirrors after enter "metaroot" command and change the vfstab entries (afaik).

do you have metadbs created? also please use "copy and paste" and code tags for your output. you might have a typo...
 

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

Solstice DiskSuite

Has anybody every used Solstice DiskSuite? I am having trouble setting it up. I installed it without a problem, but do I really have to blow away the drives on the D1000 just to create a metastate database? (8 Replies)
Discussion started by: hshapiro
8 Replies

6. 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

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

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... (0 Replies)
Discussion started by: BOFH
0 Replies

9. 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

10. Solaris

Looking for Solstice DiskSuite 4.2

Hi all, Do you know where I can download Soltice Disksuite 4.2 for Solaris 2.6 ? I haven't the CD labeled “Solaris Server Intranet Extensions 1.0” . Thanks in advance for your precious help. Bests Regards Hosni (2 Replies)
Discussion started by: hosni
2 Replies
metasync(1M)						  System Administration Commands					      metasync(1M)

NAME
metasync - handle metadevice resync during reboot SYNOPSIS
/usr/sbin/metasync -h /usr/sbin/metasync [-s setname] [buffer_size] metadevice /usr/sbin/metasync [-s setname] -r [buffer_size] /usr/sbin/metasync -p metadevice /usr/sbin/metasync -c metadevice DESCRIPTION
The metasync command starts a resync operation on the specified metadevice. All components that need to be resynced are resynced. If the system crashes during a RAID5 initialization, or during a RAID5 resync, either an initialization or resync restarts when the system reboots. Applications are free to access a metadevice at the same time that it is being resynced by metasync. Also, metasync performs the copy oper- ations from inside the kernel, which makes the utility more efficient. Use the -r option in boot scripts to resync all possible submirrors. OPTIONS
The following options are supported: -c metadevice Cancels the resync that is in progress on the specified metadevice. The resync will be stopped at its current point and can be resumed by running the "metasync metadevice" command. This option only applies to RAID1 volumes. -h Displays usage message. -p metadevice Regenerates parity information for RAID5 metadevices. -s setname Specifies the name of the diskset on which metasync will work. Using the -s option will cause the command to perform its administrative function within the specified diskset. Without this option, the command will perform its function on local metadevices. -r Specifies that the metasync command handle special resync requirements during a system reboot. metasync -r should only be invoked from the svc:/system/mdmonitor service. The metasync command only resyncs those metadevices that need to be resynced. metasync schedules all the mirror resyncs according to their pass numbers. To override the default buffer_size value used by the svc:/system/mdmonitor service, you can edit /etc/system to specify: set md_mirror:md_resync_bufsz = 2048 so that resyncs occur as quickly as possible. OPERANDS
buffer_size Specifies the size (number of 512-byte disk blocks) of the internal copy buffer for the mirror resync. The size defaults to 1024 512-byte disk blocks. It can be no more than 2048 blocks. For best performance (quickest completion of the resync), 2048 blocks is the recommended size. 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), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) NOTES
The metasync service is managed by the service management facility, smf(5), under the service identifier: svc:/system/mdmonitor Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. SunOS 5.11 27 Mar 2006 metasync(1M)
All times are GMT -4. The time now is 08:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy