[OpenAFS] Request for Assistance with OpenAFS

Lars Schimmer l.schimmer@cgv.tugraz.at
Wed, 11 Apr 2012 14:00:01 +0200


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2012-04-11 13:01, James Bricknell wrote:
> Hopefully this is a quick and stupid question.
>=20
>=20
>=20
> I have Mac clients on the network who have data in deep folder=20
> structures with long filename paths, well in excess of the Windows=20
> 256(255) character limit, and they need to copy their data across
> onto a Windows 2008 R2 Server, which obviously fails when the
> length of the filename goes over this limit.
>=20
>=20
>=20
> If I install Open AFS on this Windows server, will this allow the=20
> clients to successfully copy the data to a share on an NTFS
> formatted volume on the Windows box? Also, if version 1.7 is
> implemented as a native Windows file system, would I need to format
> a disk or partition on the Windows box as an AFS volume for the Mac
> users to be able to copy their long filename structures without
> issue, and would this data be able to be browsed locally on the
> Windows server following copying it across?

Sorry, OpenAFS does not work that way.

And the Windows Server of OpenAFS is not really able to run currently,
as untested and not supported.

OpenAFS does NOT share existant filestructures of a existant server to
other clients (thats what SMB/MS filesharing does).

OpenAFS needs dedicated servers with dedicated data partitions which
save OpenAFS data in a own format on disk.

My suggestion for you: do shorten the filepath. Maybe with symlinks or
junction points.


MfG,
Lars Schimmer
- --=20
- -------------------------------------------------------------
TU Graz, Institut f=FCr ComputerGraphik & WissensVisualisierung
Tel: +43 316 873-5405       E-Mail: l.schimmer@cgv.tugraz.at
Fax: +43 316 873-5402       PGP-Key-ID: 0x4A9B1723


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+FckEACgkQmWhuE0qbFyN8nACaA4YOFqdssVZ9QvvKq4qpdCY4
RVAAn3Dm1FHtpOOMBCGPhmVhagUhDO6d
=3D0had
-----END PGP SIGNATURE-----