Folks-
Recently, I've seen "backup.lock/backup.unlock" error messages such
as those shown below when backing up or verifying an Advfs file system on
V5.0 of True64. The Advfs manual doesn't address this issue at all. What
are Advfs or vdump "backup.lock/backup.unlock" errors, do they cause
problems I haven't found yet, and how do I get rid of them?
Thanks.
Mike
lizrdegg_at_ntrnet.net
># /sbin/vdump -0 -u -f /dev/ntape/tape0_d7 /
>path : /
>dev/fset : root_domain#root
>type : advfs
>advfs id : 0x38d224de.0000cde0.1
>vdump: error [13] posting event: sys.unix.fs.advfs.fset.backup.lock
>vdump: Date of last level 0 dump: the start of the epoch
>vdump: Dumping directories
>vdump: Dumping 81366162 bytes, 245 directories, 2556 files
>vdump: Dumping regular files
>
>vdump: Status at Wed Jan 17 14:39:12 2001
>vdump: Dumped 81487113 of 81366162 bytes; 100.1% completed
>vdump: Dumped 246 of 245 directories; 100.4% completed
>vdump: Dumped 2555 of 2556 files; 100.0% completed
>vdump: Dump completed at Wed Jan 17 14:39:12 2001
>vdump: error [13] posting event: sys.unix.fs.advfs.fset.backup.unlock
tru64-unix-managers_at_ornl.gov
Received on Tue Jan 30 2001 - 03:16:05 NZDT