Jan Harkes wrote:
Ok, that is good. I guess the volume replica was successfully removed
>from the 'volume location database'. So what went wrong was removing the
volume from the 'replication database'.
But that is pretty easy to fix,
- on your SCM edit /vice/db/VRList and remove the line that starts with /
- Then run 'volutil makevrdb /vice/db/VRList'
Jan
Hi Jan,
[EMAIL PROTECTED] db]# cd /vice/db/
[EMAIL PROTECTED] db]# cat VRList
The file was emtpy with 0 bytes
[EMAIL PROTECTED] db]# volutil makevrdb /vice/db/VRList
V_BindToServer: binding to host clusty1
VRDB completed.
[EMAIL PROTECTED] db]# l
total 60
drwxr-xr-x 2 root root 4096 Jan 18 11:16 .
drwxr-xr-x 9 root root 4096 Jan 18 11:16 ..
-rw-r--r-- 1 root root 0 Jan 16 09:54 auth2.lock
-rw------- 1 root root 32 Jan 16 09:55 auth2.pw
-rw------- 1 root root 9 Jan 16 09:53 auth2.tk
-rw-r--r-- 1 root root 0 Jan 16 09:54 auth2.tk.BAK
-rw-r--r-- 1 root root 0 Jan 17 15:08 dumplist
-rw-r--r-- 1 root root 133 Jan 16 09:54 files
-rw-r--r-- 1 root root 181 Jan 16 09:54 files.export
-rw-r--r-- 1 root root 11 Jan 16 09:58 maxgroupid
-rw------- 1 root root 2745 Jan 16 09:55 prot_users.cdb
-rw-r--r-- 1 root root 18 Jan 16 09:54 scm
-rw-r--r-- 1 root root 63 Jan 16 10:38 servers
-rw------- 1 root root 9 Jan 16 09:53 update.tk
-rw-r--r-- 1 root root 168 Jan 16 10:51 vicetab
-rw-r--r-- 1 root root 6784 Jan 17 15:09 VLDB
-rw------- 1 root root 9 Jan 16 09:54 volutil.tk
-rw-r--r-- 1 root root 0 Jan 18 11:16 VRDB
-rw-r--r-- 1 root root 0 Jan 17 15:16 VRList
-rw-r--r-- 1 root root 0 Jan 17 15:16 VRList.new
-rw-r--r-- 1 root root 0 Jan 16 09:58 VRList.old
The file VRList is still empty
[EMAIL PROTECTED] db]# createvol_rep / clusty1.mytest.de clusty2.mytest.de
clusty3.mytest.de
/ already exists as a replica on clusty1.mytest.de
Got the same again...
SrvLog of clusty1:
11:16:26 VRDB created, 0 entries
11:16:33 New Data Base received
11:17:33 New Data Base received
Achim
