Possible long filenames problem with smbtar

[David C. M. Bilsby]

Hi
	I am using Samba 2.0.6 on a SUN SPARC Solaris 2.6 machine. I compiled 
Samba using SUN cc with CFLAGS of "-fast". All the remaining configure 
parameters were left unspecified.
	
	I have been trying to use Samba to backup a nerwork of PCs onto the UNIX 
box. Each PC has a shared network drive, and the user issues an smbtar or 
smbclient backup command. eg.
	
% smbclient //dcmbpc/C "" -N -d 0 -U backup -D "/" -TcXqa test.tar "" 
"Entertainment" "My Documents/My Music" "Export/Game Demo
s" "Export/Unreal Tournament" "Windows/Win386.swp" "Win98"

	The backup itself seems to run without a problem. When I come to restore 
or list the tar file however, the long filenames get truncated. I have tried to 
list the tar with the SUN tar command and also restore it with smbtar and 
smbclient with no success. The output from a restore with smbclient is as 
follows:
	
....
restore tar file \My Documents\Office Documents\Application Framework - 
Tracee\Design Flow Diagrams\Backup\v0.04\Wo of size 29683 bytes
restore tar file \My Documents\Office Documents\Application Framework - 
Tracee\Design Flow Diagrams\Backup\v0.04\Wo of size 57389 bytes
restore tar file \My Documents\Office Documents\Application Framework - 
Tracee\Design Flow Diagrams\Backup\v0.04\Wo of size 53524 bytes
restore directory \My Documents\Office Documents\Application Framework - 
Tracee\Design Flow Diagrams\Backup\v0.04\rc
restore directory \My Documents\Office Documents\Application Framework - 
Tracee\Design Flow Diagrams\New Folder\
restore directory \My Documents\Office Documents\Application Framework - 
Tracee\Design Flow Diagrams\New Folder\RCS\
abandoning restore
Abandoning restore

	As you can see the filenames are truncatedto just "Wo". Also the restore 
aborts itself. The tar listing is as follows:
	
-rw-r--r--   0/0    65812 Jul 13 10:29 1999 ./My Documents/Office 
Documents/Application Framework - Tracee/Design Flow Diagrams/New Folder/Work
----------   0/0      120 Jan  1 01:00 1970 ././@LongLink
-rw-r--r--   0/0    53177 Jul  7 16:55 1999 ./My Documents/Office 
Documents/Application Framework - Tracee/Design Flow Diagrams/Backup/v0.04/In
----------   0/0      117 Jan  1 01:00 1970 ././@LongLink
-rw-r--r--   0/0    51694 Jul  7 16:56 1999 ./My Documents/Office 
Documents/Application Framework - Tracee/Design Flow Diagrams/Backup/v0.04/Re
----------   0/0      120 Jan  1 01:00 1970 ././@LongLink
-rw-r--r--   0/0    57340 May 26 10:24 1999 ./My Documents/Office 
Documents/Application Framework - Tracee/Design Flow Diagrams/Backup/v0.04/Tr
----------   0/0      130 Jan  1 01:00 1970 ././@LongLink
-rw-r--r--   0/0    65812 May 26 10:28 1999 ./My Documents/Office 
Documents/Application Framework - Tracee/Design Flow Diagrams/Backup/v0.04/Wo
----------   0/0      122 Jan  1 01:00 1970 ././@LongLink
-rw-r--r--   0/0    29683 Jul  7 16:55 1999 ./My Documents/Office 
Documents/Application Framework - Tracee/Design Flow Diagrams/Backup/v0.04/Wo
----------   0/0      121 Jan  1 01:00 1970 ././@LongLink

	The manual for smbtar states a limit of 1024 bytes for the filename and 
pathname. The filenames above do not exceed this limit, the number of bytes 
chopped off is only about 10-15 more.
	
	I would appreciate any suggestions as to why this might be happening.
	
		Cheers
				David.
-----------------------------------------------------------------------------
| Image Processing & Interpretation  | David Bilsby    (Senior Engineer)    |
| email: d.bilsby at signal.dera.gov.uk | Defence Evaluation & Research Agency |
| Tel:  +44 (1684) 896158            | Room E306, St Andrews Road,          |
| Fax:  +44 (1684) 894952            | Malvern, Worcs, WR14 3PS, ENGLAND    |
-----------------------------------------------------------------------------

The Information contained in this e-mail and any subsequent correspondence 
is private and is intended solely for the intended recipient(s). For those 
other than the intended recipient any disclosure, copying, distribution, or 
any action taken or omitted to be taken in reliance on such information is 
prohibited and may be unlawful.

The views expressed herein are entirely those of the author and do not
represent the views, policy or understanding of any other person or
official body.