Re: [OpenAFS] Connection timed out on new mount point
Am 02.12.2016 um 17:48 schrieb Jeffrey Altman: > The client has cached information for the volume group that indicates > that no backup volume exists. > > fs checkvolumes That solved it, indeed. Thanks a lot. Bye... Dirk -- Dirk Heinrichs GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de Tox: he...@toxme.se Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Connection timed out on new mount point
On 12/2/2016 11:35 AM, Dirk Heinrichs wrote: > Hi, > > I'm currently facing a strange problem with connection timeouts after > creating a mount point (fs mkm) for a new volume: > > # fs mkm tester home.tester.backup > # ll > ls: cannot access 'tester': Connection timed out > total 132K > ... > ?? ? ? ? ?? tester > > The mount point has been created from a client workstation and only > becomes available there after reboot or cache manager restart. OTOH, > it's accessible immediately on the server (where /afs is usually not > accessed): > > # ll > total 134K > ... > drwx-- 2 1005 1001 2.0K Dec 1 21:49 tester > > Both server and client are up-to-date Debian Stretch systems running > OpenAFS 1.6.18.3. > > Any ideas what could be causing the problem? > > Thanks... > > Dirk The client has cached information for the volume group that indicates that no backup volume exists. fs checkvolumes Jeffrey Altman <> smime.p7s Description: S/MIME Cryptographic Signature
[OpenAFS] Connection timed out on new mount point
Hi, I'm currently facing a strange problem with connection timeouts after creating a mount point (fs mkm) for a new volume: # fs mkm tester home.tester.backup # ll ls: cannot access 'tester': Connection timed out total 132K ... ?? ? ? ? ?? tester The mount point has been created from a client workstation and only becomes available there after reboot or cache manager restart. OTOH, it's accessible immediately on the server (where /afs is usually not accessed): # ll total 134K ... drwx-- 2 1005 1001 2.0K Dec 1 21:49 tester Both server and client are up-to-date Debian Stretch systems running OpenAFS 1.6.18.3. Any ideas what could be causing the problem? Thanks... Dirk -- Dirk Heinrichs GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de Tox: he...@toxme.se Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
