Hi,
I have noticed the following behavior of dasalvager:
(Tested on RHEL5 + RHEL6 with openafs-1.6.2 + openafs-1.6.4)
Salvaging a RW-volume on a DAFS server like the following works fine:
/usr/afs/bin/dasalvager -partition PARTITION -volumeid RW-VOLID -showlog
-forceDAFS -debug
Putting this into a script and execute the script from CMD-line works also fine.
# /tmp/salvage.sh
@(#) OpenAFS 1.6.4 built 2013-06-28
07/08/2013 16:12:59 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/dasalvager
-partition /vicephf -volumeid 536912830 -showlog -forceDAFS -debug)
07/08/2013 16:12:59 2 nVolumesInInodeFile 56
07/08/2013 16:12:59 CHECKING CLONED VOLUME 536912831.
07/08/2013 16:12:59 A.e.seka.readonly (536912831) updated 07/06/2013 18:29
07/08/2013 16:12:59 SALVAGING VOLUME 536912830.
07/08/2013 16:12:59 A.e.seka (536912830) updated 07/06/2013 18:29
07/08/2013 16:12:59 totalInodes 345
07/08/2013 16:12:59 Salvaged A.e.seka (536912830): 338 files, 481 blocks
But executing the script from cron doesn't work.
Here the output from the scripts:
(RHEL5 openafs-1.6.4)
@(#) OpenAFS 1.6.4 built 2013-06-28
07/08/2013 15:58:01 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/dasalvager
-partition /vicephf -volumeid 536912830 -showlog -forceDAFS -debug)
07/08/2013 15:58:01 _VLockFd: fcntl failed with error 9 when trying to lock fd
0 (locktype=2, offset=536912830)
Error 5 trying to lock volume 536912830; Aborted
/tmp/salvage.sh: line 1: 743 Aborted /usr/afs/bin/dasalvager
-partition /vicephf -volumeid 536912830 -showlog -forceDAFS -debug
Same behavior (RHEL6 openafs-1.6.2)
@(#) OpenAFS 1.6.2 built 2013-02-22
07/08/2013 10:02:01 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/dasalvager
-partition /vicepf -volumeid 536884732 -showlog -forceDAFS -debug)
07/08/2013 10:02:01 _VLockFd: fcntl failed with error 9 when trying to lock fd
0 (locktype=2, offset=536884732)
Error 5 trying to lock volume 536884732; Aborted
/tmp/salvage.sh: line 1: 8690 Aborted (core dumped)
/usr/afs/bin/dasalvager -partition /vicepf -volumeid 536884732 -showlog
-forceDAFS -debug
Is there any chance to get this also running via cron?
-- Kind regards
Ralf
