Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

Which node should I run "verify" command on?

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


tsukishima.ha at gmail

Jul 22, 2010, 11:53 PM

Post #1 of 2 (405 views)
Permalink
Which node should I run "verify" command on?

Hi,

I am planning to run online verify on a regular basis.
Should I call "drbdadm verify <resource>" on "Primary" node?
or is it no problem to run it on "Secondary"?

I am just a little confusing because there are two connection state
like "VerifyS" and "VerifyT".
If "VerifyS" means that "This node's data is the source for verifing,
it seems that I have to run verify command on Primary node.

and,
drbdadm disconnect/connect <resource> for the resync,
I can run these commands on any node, right?
or should I run these on Primary?

Thanks,
Junko IKEDA

NTT DATA INTELLILINK CORPORATION
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


tsukishima.ha at gmail

Jul 22, 2010, 11:53 PM

Post #2 of 2 (381 views)
Permalink
Which node should I run "verify" command on? [In reply to]

Hi,

I am planning to run online verify on a regular basis.
Should I call "drbdadm verify <resource>" on "Primary" node?
or is it no problem to run it on "Secondary"?

I am just a little confusing because there are two connection state
like "VerifyS" and "VerifyT".
If "VerifyS" means that "This node's data is the source for verifing,
it seems that I have to run verify command on Primary node.

and,
drbdadm disconnect/connect <resource> for the resync,
I can run these commands on any node, right?
or should I run these on Primary?

Thanks,
Junko IKEDA

NTT DATA INTELLILINK CORPORATION
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.