Anders, Ragge: This is not a known issue and I can't reproduce it on any of my XP, 2003, 2008 or Win7 systems which makes it difficult to identify.
From the H: drive, what is the output of fs whereis \\afs\ltu.se\staff\r\ragge If that fails, please turn on the pioctl debugging registry key as described in the release notes troubleshooting section and file a bug report to [email protected] with the command line output that is generated from "fs whereis" when the registry key is active. Jeffrey Altman On 6/28/2010 12:27 PM, Anders Hannus wrote: > I'll be happy to provide more details if you can be more specific about what > is needed or if we just need to file a bug report. > > On a Windows 2003 server I know that 1.5.59 is working and 1.5.74 is not. I > don't know exactly when it stopped working as I found out about this as I > have some powershell scripts that stopped working when upgrading from .59 to > .74. It's thus quite annoying as I have to run these scripts on a server we > still have not upgraded. > > As far as I know the problem is present om Windws Server 2003, Windows XP and > Windows 7. Both with the command and from the explorer GUI. It works if afs > is mounted as a letter within windows but not with unc paths. I got one > powershell script working then using the set-location command to change she > execution location to the unc path. Somehow that didn't solve the problem in > another script. > > /anders hannus > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Anders Magnusson > Sent: den 18 juni 2010 13:13 > To: [email protected] > Cc: [email protected] > Subject: Re: [OpenAFS] Windows client: "Mount points must be created within > the AFS file system". > > Jeffrey Altman wrote: >> On 6/18/2010 4:26 AM, Anders Magnusson wrote: >> >>> Hi, >>> >>> we'we discovered a small bug related to mount points which has >>> appeared in some recent windows client. Testing with 1.5.74; mount >>> points cannot be created neither from the explorer shell nor from the >>> command prompt if referring to an UNC path. This worked with older >>> clients (like 1.5.59). >>> >>> Mapping the afs path to a drive letter and then make a mount point works. >>> It's the UNC path that makes it fail. >>> >>> Is this a known bug or should we file a bug report? >>> >>> -- Ragge >>> >> >> I just tried: >> >> [C:\src\openafs\stresstest]fs mkm \\afs\yfs\user\jaltman\dementia >> root.cell -cell dementia.org >> >> [C:\src\openafs\stresstest]fs lsm \\afs\yfs\user\jaltman\dementia >> '\\afs\yfs\user\jaltman\dementia' is a mount point for volume >> '#dementia.org:root.cell' >> >> Can you be more specific about the problem you are experiencing? >> > No problem; H: is my home directory: > > H:\>fs mkm AAAA staff.ragge > > H:\>fs rmm AAAA > > H:\>fs mkm \\afs\ltu.se\staff\r\ragge\AAAA staff.ragge > fs: mount points must be created within the AFS file system > > H:\>fs --version > OpenAFS_1.5.7400 > > -- Ragge > > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > :��
smime.p7s
Description: S/MIME Cryptographic Signature
