Many thanks for all the replies I received. It turned out that in
essence the question had been posted to the list sometime last year by
John Speakman.
And the information can be found in www.tru64.org by searching for
'atime', which was pointed out to me by John Speakman.
In the archives a remedy was suggested to apply the 'latest' patchlevel.
At present the systems are on patchlevel 3 for 4.0e and on patchlevel 2
for 4.0f and the present behaviour on vdump on nfs-mounted filesystems was
already exhibited in 4.0d (patched).
Considering the problem has been lingering through several releases
it looks as if patching is not a solution.
Lydia Heck
Lydia Heck
My original question was:
> > I am using vdump to backup an nfs mounted file system.
> > The backup is done, however with lots and lots of error messages, in fact
> > for every file which is backed up there is a message like
> >
> > vdump: can't reset atime for <./directory/filename;[22] Invalid argument
> >
> > The error message seems to come from vdump, however none of the strings in
> > vdump show 'Invalid argument' with a Capital I.
> >
> > The vdump command I use is (for example on level 5)
> > /sbin/vdump -5 -C -b 64 -F 64 -u -f /dev/nrmt0h /nfs_mount_point
> >
> > The filesystem which is mounted is exported root permitted and is mount
> > rw access.
> > Both fileserver is running 4.0F and backup server is running 4.0E.
> > However the problem already occurred when both were running 4.0E.
> >
> > The backup works, but it is messy and the access times are not reset so
> > the solution is not complete.
> >
> > Recently I tried rdump. But that only works once after a reboot and fails
> > for any later backup because of a resource problem. I have run a sys_check
> > and reconfigured according to the suggestions of the output, but there is
> > no change in the behaviour.
> >
> > So vdump it has to be.
> >
> > Has anybody had a similar experience and found a solution?
> >
> > Best regards,
> > Lydia Heck
> >
Received on Thu Jun 29 2000 - 17:13:39 NZST