ADSM-L

Re: [ADSM-L] NFS mount backup failing after upgrading to 6.2.2

2011-01-06 14:38:00
Subject: Re: [ADSM-L] NFS mount backup failing after upgrading to 6.2.2
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 6 Jan 2011 14:35:17 -0500
We have not been able to figure out what is causing this.  As I mentioned,
WORKS JUST FINE with 6.1.x but fails with 6.2.x although I don't see
anything in the 6.2.x book saying anything has changed with NFS mounted
filesystem processing.  Reinstalling the 6.1.x client resolves the
problem.



From:
Richard Sims <rbs AT BU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
01/06/2011 12:13 PM
Subject:
Re: [ADSM-L] NFS mount backup failing after upgrading to 6.2.2
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Hi, Zoltan -

This sounds like a DNS lookup failure to me, as though the client is
attempting to verify some aspect of the mount.
Naturally, the programmer didn't bother including the lookup name in the
error message, to make pursuit easier.  You may be able to deduce that
based upon mount inspection.

    Richard Sims

On Jan 6, 2011, at 11:32 AM, Zoltan Forray/AC/VCU wrote:

> We have been updating Linux clients to 6.2.2.0 due to the recently
> reported vulnerabilities.
>
> One client that has been backing an NFS mount just with 6.1, is now
> failing.  We get the following errors:
>
> 01/06/2011 10:22:30 ANS3402W psGetHostName(): A system call
> gethostbyaddr() failed with code 1.
> 01/06/2011 10:22:30 ANS5250E An unexpected error was encountered.
>    TSM function name : nsGetNasVolumeInfo():
>    TSM function      : dmMapNfsVolume() failed to map remote volume for
> path: </var/echo360>.
> ...