Hi, > By any chance was the mount point created before the "user.test" volume > was restored or was the volume restored, removed, and restored again? No. > > I'm thinking the client might have cached a volume id for "user.test" > that is no longer valid. If that is the case, try > > fs checkvolume I tried. No success. > > The other question that comes to mind is, what are the ACLs on the root > directory of the user.test volume? Does the current user have at least > lookup permission? yes, i mounted the restored volume to a folder "user.test" in my user afs home path. I also have a admin token. The user admin is in UserList of AFS server. So i should could do everything. > > Finally, what version of the file server is hosting the volume? 1.6.1 , Solaris 10
Old situation on client:
==============
vos examine user.test
user.test 536875364 RW 1828930 K On-line
vos listvldb user.test
user.test
RWrite: 536875364
number of sites -> 1
server xyz partition /vicepa RW Site
New situation on client:
==============
fs mkmount doesnt work anymore.
fs mkmount -dir user.test -vol user.test
fs:'user.test': No such device
>
> Jeffrey Altman
>
>
regards,
Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
