samba - Mar 2001 - Samba windows mount problem - some files and directories can't be seen even though they exist!

Hi.

I have mounted a Windows 2000 Pro computer under linux using:

mount -t smbfs -o username=phill,password=xxxxx //winbox/drivec /mnt/winbox

I can then jump into /mnt/winbox/ and navigate around the Win 2000 box.

But...

For some reason some of the files and directories on the windows 
computer are not showing up.

For example, I have just moved a heap of wav files for our
audio-processing work into the C:\audio directory on the Windows box.

Yet /mnt/winbox/audio shows up as completely empty. Moving the wav files
into other directories doesn't seem to help.


Likewise, I want to be able to back up the "Documents and Settings"
directories on the Windows Box and this too shows up as completely 
empty, even though there are many sub-directories existing on the 
Windows box.

There doesn't seem to be a logical connection to the problem. Originally
I thought maybe it was files 4-5 sub-directories deep, but that's not 
the case.  Files appear in some directories and just disappear in others.

Does anyone have any suggestions why files and directories won't appear
under the smbfs mount under Linux and how I can fix this?

It's rather critical as I'd like to back up critical directories on the 
Windows boxen via the smbfs mount.

System details:
Mandrake 7.2
Samba 2.07


Thanks!

On Wed, 28 Mar 2001, Phill Coxon wrote:
> There doesn't seem to be a logical connection to the problem.
Originally
> I thought maybe it was files 4-5 sub-directories deep, but that's not 
> the case.  Files appear in some directories and just disappear in others.
> 
> Does anyone have any suggestions why files and directories won't appear
> under the smbfs mount under Linux and how I can fix this?
Which kernel do you use? (uname -a)

If below 2.2.18, upgrade. There are known bugs related to NT servers
and long directories.


If you do use 2.2.18/19/2.4.2, kernel log messages + some more info would
be nice.

A zip of the actual files of one dir that fails, or a list of the
filenames in one dir that fails. Generate a dummy dir and verify that
smbfs fails on that, if your data/filenames are private.

Off-list if it is large (put it on a http/ftp if it is really large).

A tcpdump tracefile is useful if this isn't a simple "it fails on long
dirs" bug. But the other info first.

/Urban