08-30-2011
Do the read and write policies apply to resync process? At least I thought the read and write policies are to tell the md driver how to handle incoming I/O calls from the user space.The resync process perhaps does not fall into that category. But my understanding maybe flawed.
Let me know if you find any links/doc that shows mirror resyncs are done within the confines of the I/O policies. I would like to read it up and learn. Thanks in advance.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am using raidctl on a v440 disk and noticed it resyncs after every boot, which takes about 30 minutes because of the size of the partition. I am concerned with what happens during the resync if "writes" happen to the disk before it is complete?
Any info would be helpful.
Thanks (0 Replies)
Discussion started by: csgonan
0 Replies
2. Linux
Can anyone could tell me what is the meaning of this problem:
Last successful check resync is greater than min sync interval (1195785433 > 7200)
And what can do to solve this problem.
Thank you..Please HElp me! (4 Replies)
Discussion started by: o_m_g
4 Replies
3. AIX
Hi,
I have NTP configured:
vi /etc/ntp.conf
broadcastclient
server 128.127.1.3
driftfile /etc/ntp.drift
tracefile /etc/ntp.trace
# xntpdc
xntpdc> sysinfo
system peer: 128.127.1.3
system peer mode: client
leap indicator: 00
stratum: 12
precision: ... (0 Replies)
Discussion started by: victorcheung
0 Replies
4. Shell Programming and Scripting
Hi All,
i am aware that there is a difference between:
1. rsync -n -av /tmp .
2. rsync -n -av /tmp/ .
I would like to do the first option. But if i use a variable (rsync -av $log .), the command behaves like a second option (with the trailing slash)
Is there any way to use a... (2 Replies)
Discussion started by: c00kie88
2 Replies
5. Solaris
Hi,
I am having two metadevices d50 and d100 which are used to created soft partitions as and when required.
d50 and d100 are metadevices formed on different disks.
d50 -- disks 0 & 1
d100 -- disks 2 & 3
I have a soft partition d70 os 50 GB on d50. Now there is no free space on d50.
... (1 Reply)
Discussion started by: sag71155
1 Replies
6. Solaris
hi all
i am very new to solaris...i am trying configure raid 0 in my ultrascsi box which is having 6 sun36GB hard disks. I have created 4 state database replicas in the following slices /dev/dsk/c1t1d0s7 /dev/dsk/c1t2d0s7 /dev/dsk/c1t3d0s7 and /dev/dsk/c1t4d0s7. i could not use any other... (7 Replies)
Discussion started by: kingston
7 Replies
7. Solaris
At a new job, I've inherited a handful of Solaris 10 SunFire V240 servers.
I noticed that the metadevices are not consistent, in a way that I've not seen before....
internal mirrored disks:
metadevice d60 has c1t0d0s6 as submirror 0 (d61) and c1t1d0s6 as submirror 1 (d62)
metadevice... (1 Reply)
Discussion started by: Max Power
1 Replies
8. AIX
Hi All,
I have two mount points have the same data with little changes between them
/appabc1
/appabc2
Both of them have the same data, there is some little changes on the data between them
I want /appabc2 to has the same data of /appabc1 exactly including to those little changes... (6 Replies)
Discussion started by: Mr.AIX
6 Replies
9. Solaris
Dear Team,
This time i am facing some new problems which is beyond my thinking. I need some expert advice.
We are having 4 Servers ( 2 nos Sun SPARC Enterprise T5220 & 2 nos of SF e2900 Servers ). Both the T5220 Servers are Termed as Node A and Node B . The same things are followed with... (1 Reply)
Discussion started by: sudhansu
1 Replies
10. Shell Programming and Scripting
Good Morning,
I'm trying to automate the resync process after a mirror replacement on Solaris. To avoid resyncing all the drives at once, I'm trying to use metastat for each drive to determine if the drive is still resyncing or if it is done (Okay). The following test lines seem to always show... (4 Replies)
Discussion started by: Stellaman1977
4 Replies
LEARN ABOUT OPENSOLARIS
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
/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)