vdump: can't reset atime for <filename>; [22] Invalid argument

From: John Speakman <speakman_at_biost.mskcc.org>
Date: Fri, 20 Aug 1999 21:16:05 -0400

Hi everyone,

since moving from 4.0B to 4.0E we have been seeing the following
message in our backup logs:

vdump: can't reset atime for <./pathname/.filename>; [22] Invalid argument

where /pathname/filename is the correct path to the file it's backing up.
It
happens on ASE mounted NFS volumes only (AdvFS volumes are OK).
I couldn't swear it happens with every single file on each NFS volume but
certainly a huge number of them (the reason I noticed is that the volume
containing our backup logs filled up). Anyway it seems what it's doing is

backing up the file OK (I hope! I will try a restore next) but then trying
to
set the archive bit or whatever and failing because (I guess) one of the
arguments is now no longer valid on NFS volumes. Here's an example
of the vdump command we use:

vdump -0uN -f /dev/nrmt0h /usr/users

No very exciting arguments there. We backup using the root account
by the way. Anyone have any idea what's going on?

Thanks in advance; I'll summarize.

John
Received on Sat Aug 21 1999 - 01:19:43 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:39 NZDT