05-06-2008
Disk Replacement SVM
Hello,
Can someone advise the proper procedure for replacing a mirrored disk in SVM. I have checked the docs and various websites but the procedure seems to vary. This is what I would do...
1. Remove the db replicas from the bad disk.
2. Detach it from the mirror
3. Clear it with metaclear.
4. Replace the Disk
5. Copy the label from the good disk using prtvtoc and ftmhard
6. Create new db replicas
7. Create all the metadevices again then attach them which should start the resync?
Is this all necessary or can I just do a metareplace -e ?
I hope this is roughly right, What im not sure about is the need to use cfgadm to deconfig the failed disk then configure the new on back in, is this dependant on what hardware you are running?
Also, is a reboot required for any of this?
Many Thanks.
10 More Discussions You Might Find Interesting
1. Solaris
I dont even know what raid level this is, but its raid 5 mirrored from the looks of it.
I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
Hi All,
I have to remove the disk from SVM.
Kindly guide me or suggest me some link where in I can steps to remove SVM from Solaris 10 .Also I have one metaset which require deletion.
Thanks in anticipation! (10 Replies)
Discussion started by: kumarmani
10 Replies
3. Solaris
Hi Gurus, I've got an issue here:
(1) Hardware: Sun NetraT1, (2) OS: Solaris 10, (3) SVM
metastat shows /var having 12 GB. df shows /var having 4 GB. Real space for /var is about 4 GB since I can't move a big file to it. How is 8 GB space missing? Does /var/run swap need to account? Can I... (5 Replies)
Discussion started by: aixlover
5 Replies
4. Solaris
Dear All,
Please help me to configure root mirroring using SVM in Solaris 9.
Thanks and Regards,
Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies
5. Solaris
The following is the summarry:-
1) Four disks in server ie (c1t0d0. c1t1d0, c1t2d0, c1t3d0). c1t2d0 is the disk to be replaced.
c1t0d0 and c1t2d0 are mirrors.
c1t1d0 and c1t3d0 are mirrors.
Metadb to be deleted is in c1t2d0s7
a) Mirror d35 has 2 submirrors d38 and d39
d38 is a stripe... (0 Replies)
Discussion started by: aji1729
0 Replies
6. Solaris
I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system
and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies
7. Solaris
Hi All
BAsed on the below I would like to verifu two things
(1) The udnerlying mirroris for '/mnt' na dit onlcy contaisne 1 sub-mirror, with one sliceon is one disk and hence, data loss on the mount point (the mount point, '/mnt' is backed up)
(2) the Procedure for renewal
# df -kh /mnt... (2 Replies)
Discussion started by: stevie_velvet
2 Replies
8. Solaris
Hi
Please can you help me on replacing or removing a faulty disk drive on a SUN NETRA X4250server with 4 internal drives only.
the format comand show me the following:
format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <drive type unknown>
... (9 Replies)
Discussion started by: fretagi
9 Replies
9. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
10. AIX
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
Discussion started by: terrya
3 Replies
LEARN ABOUT LINUX
metasync
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
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:
-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 128 512-byte disk blocks (64 Kbytes). It can be no more than 2048 blocks. For best performance (quick-
est 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)
Solaris Volume Manager Administration Guide
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.10 24 Nov 2004 metasync(1M)