Feisty smbmount fails with Error

Bug #118328 reported by Zeus-101
4
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: smbfs

Releveant fstab

/vera.bu.edu/drivec /samba/vera/drivec smbfs username=mike,password=,,,,netbiosname=CNS,rw

//vera.bu.edu/drived /samba/vera/drived smbfs username=mike,password=,,netbiosname=CNS,rw

//vera.bu.edu/driveg /samba/vera/driveg smbfs username=mike,password=,,,,netbiosname=CNS,rw
mike@bluebeard:~$

Samba intermittently fails to mount these shares. I use a mount -a command and obtain

20225: tree connect failed: ERRDOS - ERRnomem (Insufficient server memory to perform the requested function.)
SMB connection failed
20226: tree connect failed: ERRDOS - ERRnomem (Insufficient server memory to perform the requested function.)
SMB connection failed
20227: tree connect failed: ERRDOS - ERRnomem (Insufficient server memory to perform the requested function.)
SMB connection failed

This happens from time to time and I have no idea what causes it or how to fix.

Revision history for this message
yus budiyono (yusbu) wrote :

We have 2 windows (xp and 2k) with plenty of shared folder inside which actively accessed by 17 Ubuntu Edgy/Feisty clients.
For many time, shared folder connected through samba may disconnects. This also occured in computer having automount during bootup via /etc/fstab.

If this is the case, you may do daisy-chain (as the solver name out there) mounting by using 1 Linux computer automounting the share and other Linux box access the shared folder through this computer.

It was said that XP home only accept 5 connection and XP Pro accept 10 connection.

My case: Windows shared folder is just not very pleasantly smbmounted.

Revision history for this message
yus budiyono (yusbu) wrote :

Wait, I hope you put 0 0 or 0 1 in the end of your /etc/fstab line

Revision history for this message
Michael Cohen (mike1947) wrote : Re: [Bug 118328] Re: Feisty smbmount fails with Error

I have some more information. I was able to fix the problem by mounting
immediately after reboot of the windows share.. Also a smbmount from
another linux machine shows the same error when this is occuring. I
suspect the windows share is leaking. As it no suprise I can find no
information on this on the Windows end. As is usual with this the two file
systems I am serving up from the Unix box to the windows machine never gives
me any trouble.
            --Best
                MIke

On 6/3/07, yus budiyono <email address hidden> wrote:
>
> Wait, I hope you put 0 0 or 0 1 in the end of your /etc/fstab line
>
> --
> Feisty smbmount fails with Error
> https://bugs.launchpad.net/bugs/118328
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Michael Cohen
Work: 677 Beacon St Rm 213, Boston Mass
Home: 25 Stearns Road #3 Brookline, MA
Ph: 1-617-353-9484(w) 617-734-8828(h) Fax: 617-353-7755

Revision history for this message
Mathias Gug (mathiaz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you specify which OS runing on your server ?

Changed in samba:
status: New → Incomplete
Revision history for this message
Michael Cohen (mike1947) wrote :

Feisty. I researched the bug and it was a bug on the windows side. Some
stack needed more capacity which I gave it
           --mike

On 9/19/07, Mathias Gug <email address hidden> wrote:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Could you specify which OS runing on your server ?
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
> --
> Feisty smbmount fails with Error
> https://bugs.launchpad.net/bugs/118328
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Michael Cohen
Work: 677 Beacon St Rm 213, Boston Mass
Home: 25 Stearns Road #3 Brookline, MA
Ph: 1-617-353-9484(w) 617-734-8828(h) Fax: 617-353-7755

Mathias Gug (mathiaz)
Changed in samba:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.