ubik recovery and remote use correct file number
authorDerrick Brashear <shadow@dementia.org>
Wed, 8 Sep 2010 00:31:20 +0000 (20:31 -0400)
committerDerrick Brashear <shadow@dementia.org>
Wed, 8 Sep 2010 03:55:39 +0000 (20:55 -0700)
the file propagation "out of band" changes should not hardcode recovery
on file 0, but instead work on any file the interface is acting on.
use the provided file number.

Change-Id: I713671beaab01630bdd21d733f950f75c6456ac3
Reviewed-on: http://gerrit.openafs.org/2715
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>

src/ubik/recovery.c
src/ubik/remote.c

index b6195c3..827f006 100644 (file)
@@ -694,7 +694,7 @@ urecovery_Interact(void *dummy)
                if (!code)
                    code = rename(pbuffer, tbuffer);
                if (!code) {
-                   (*ubik_dbase->open) (ubik_dbase, 0);
+                   (*ubik_dbase->open) (ubik_dbase, file);
 #endif
                    /* after data is good, sync disk with correct label */
                    code =
index b395539..4069cbd 100644 (file)
@@ -593,7 +593,7 @@ SDISK_SendFile(struct rx_call *rxcall, afs_int32 file,
     if (!code)
        code = rename(pbuffer, tbuffer);
     if (!code) {
-       (*ubik_dbase->open) (ubik_dbase, 0);
+       (*ubik_dbase->open) (ubik_dbase, file);
 #endif
        code = (*ubik_dbase->setlabel) (dbase, file, avers);
 #ifndef OLD_URECOVERY