Cannot mount LANServer network storage device.

[Stephen Berryman]

Hi



When I attempt to mount a shared directory from my new network storage
device, I get the following


Mounts OK from Windows XP and 2000.

Can't mount from Linux

$ uname -a
Linux tru64.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:02:29 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux

$ sudo mount -t cifs -o
username=usersname,password=xxxxxx //192.168.88.2/users_space /mnt/users_space --verbose
Password:
parsing options: rw,username=usersname,password=xxxxxx

mount.cifs kernel mount options unc=//192.168.88.2\users_space,
ip=192.168.88.2,ver=1,rw,username=usersname,password=xxxxxx



Appears to work most times but then



$ ll /mnt/users_space
ls: cannot open directory /mnt/users_space: Not a directory



That is the target directory cannot be read!!

I first tried this using smb4k with the same result.

Often I get a failure of the mount command with



mount error 20 = Not a directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)


Same happens on



Linux p3000.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:35:10 EDT 2008
i686 i686 i386 GNU/Linux




so its not a x86_64 problem.

I had to use protocol=RAP to browse in smb4k




Hope you can help


regards


Stephen





_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Günter Kukkukk-2]

Am Donnerstag, 12. Juni 2008 schrieb Stephen Berryman:

> Hi
>
>
>
> When I attempt to mount a shared directory from my new network storage
> device, I get the following
>
>
> Mounts OK from Windows XP and 2000.
>
> Can't mount from Linux
>
> $ uname -a
> Linux tru64.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:02:29 EDT 2008
> x86_64 x86_64 x86_64 GNU/Linux
>
> $ sudo mount -t cifs -o
> username=usersname,password=xxxxxx //192.168.88.2/users_space /mnt/users_space --verbose
> Password:
> parsing options: rw,username=usersname,password=xxxxxx
>
> mount.cifs kernel mount options unc=//192.168.88.2\users_space,
> ip=192.168.88.2,ver=1,rw,username=usersname,password=xxxxxx
>
>
>
> Appears to work most times but then
>
>
>
> $ ll /mnt/users_space
> ls: cannot open directory /mnt/users_space: Not a directory
>
>
>
> That is the target directory cannot be read!!
>
> I first tried this using smb4k with the same result.
>
> Often I get a failure of the mount command with
>
>
>
> mount error 20 = Not a directory
> Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
>
>
> Same happens on
>
>
>
> Linux p3000.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:35:10 EDT 2008
> i686 i686 i386 GNU/Linux
>
>
>
>
> so its not a x86_64 problem.
>
> I had to use protocol=RAP to browse in smb4k

please post the outcome of
  smbclient -L 192.168.88.2 -N   or
  smbclient -L 192.168.88.2 -U username%passwd
so we can have a look at the reported remote SMB server
and version.
Cheers, Günter
_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Jeff Layton-2]

On Thu, 12 Jun 2008 15:03:29 +0200
Günter Kukkukk <linux@...> wrote:

> Am Donnerstag, 12. Juni 2008 schrieb Stephen Berryman:
> > Hi
> >
> >
> >
> > When I attempt to mount a shared directory from my new network storage
> > device, I get the following
> >
> >
> > Mounts OK from Windows XP and 2000.
> >
> > Can't mount from Linux
> >
> > $ uname -a
> > Linux tru64.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:02:29 EDT 2008
> > x86_64 x86_64 x86_64 GNU/Linux
> >
> > $ sudo mount -t cifs -o
> > username=usersname,password=xxxxxx //192.168.88.2/users_space /mnt/users_space --verbose
> > Password:
> > parsing options: rw,username=usersname,password=xxxxxx
> >
> > mount.cifs kernel mount options unc=//192.168.88.2\users_space,
> > ip=192.168.88.2,ver=1,rw,username=usersname,password=xxxxxx
> >
> >
> >
> > Appears to work most times but then
> >
> >
> >
> > $ ll /mnt/users_space
> > ls: cannot open directory /mnt/users_space: Not a directory
> >
> >
> >
> > That is the target directory cannot be read!!
> >
> > I first tried this using smb4k with the same result.
> >
> > Often I get a failure of the mount command with
> >
> >
> >
> > mount error 20 = Not a directory
> > Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
> >
> >
> > Same happens on
> >
> >
> >
> > Linux p3000.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:35:10 EDT 2008
> > i686 i686 i386 GNU/Linux
> >
> >
> >
> >
> > so its not a x86_64 problem.
> >
> > I had to use protocol=RAP to browse in smb4k
>
> please post the outcome of
>   smbclient -L 192.168.88.2 -N   or
>   smbclient -L 192.168.88.2 -U username%passwd
> so we can have a look at the reported remote SMB server
> and version.

I've run into a fair number of these sorts of devices that use a
downrevved version of samba and that have spotty support for unix
extensions. You might want to also give a quick test mounting with '-o
nounix' and see whether that makes any difference.

--
Jeff Layton <jlayton@...>
_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Christopher R. Hertel]

Jeff Layton wrote:
:
> I've run into a fair number of these sorts of devices that use a
> downrevved version of samba and that have spotty support for unix
> extensions. You might want to also give a quick test mounting with '-o
> nounix' and see whether that makes any difference.

There are also one or two new CIFS server implementations coming out of Asia
these days.  The Vantec NexStar LX is one example.  They have a proprietary
CIFS server implementation running on a embedded OS.  I've done some
checking--they claim to support the "Samba Protocol" but it isn't Samba code.

I would really like to have some folks from Vantec at the next CIFS plugfest.

As for the older versions of Samba...  I have had only minimal trouble
accessing a Linksys NSLU2 from my Linux and BSD systems.  The NSLU2 runs
Samba 2.2.mumble.

Chris -)-----

--
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh@...
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh@...
_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Gautam Iyer-4]

On Thu, Jun 12, 2008 at 11:57:47PM -0500, Christopher R. Hertel wrote:

>> I've run into a fair number of these sorts of devices that use a
>> downrevved version of samba and that have spotty support for unix
>> extensions. You might want to also give a quick test mounting with '-o
>> nounix' and see whether that makes any difference.
>
> There are also one or two new CIFS server implementations coming out
> of Asia these days.  The Vantec NexStar LX is one example.

Does someone on this list actually use the Vantec NexStar LX? I had one,
which was working fine on the 2.6.23 kernels, but borks on the 2.6.25
kernels. If I try rsync-ing large directories, or copying multiple large
files simultaneously my syslog is plagued with a whole bunch of lines of
the form

    CIFS VFS: Write2 ret -28, wrote 0
    CIFS VFS: No response to cmd 47 mid 67
    CIFS VFS: Write2 ret -11, wrote 0
    CIFS VFS: Send error in read = -11
    CIFS VFS: Send error in read = -5

It worked great (although at really low speeds) on the 2.6.23 kernels.
And it works fine with other OS's. But with CIFS & 2.6.25, the Vantec
NexStar LX is pretty much a paperweight.

If anyone knows what I can do to avoid these errors (or if anyone has
this working well with recent kernels), please let me know.

Thanks,

GI

--
100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
89. After I captures the hero's superweapon, I will not immediately
disband my legions and relax my guard because I believe whoever holds
the weapon is unstoppable. After all, the hero held the weapon and I
took it from him.


_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Stephen Berryman]

On Thu, 2008-06-12 at 18:02 +1000, Stephen Berryman wrote:

> Hi
>
>
>
> When I attempt to mount a shared directory from my new network storage
> device, I get the following
>
>
> Mounts OK from Windows XP and 2000.
>
> Can't mount from Linux
>
> $ uname -a
> Linux tru64.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:02:29 EDT 2008
> x86_64 x86_64 x86_64 GNU/Linux
>
> $ sudo mount -t cifs -o
> username=usersname,password=xxxxxx //192.168.88.2/users_space /mnt/users_space --verbose
> Password:
> parsing options: rw,username=usersname,password=xxxxxx
>
> mount.cifs kernel mount options unc=//192.168.88.2\users_space,
> ip=192.168.88.2,ver=1,rw,username=usersname,password=xxxxxx
>
>
>
> Appears to work most times but then
>
>
>
> $ ll /mnt/users_space
> ls: cannot open directory /mnt/users_space: Not a directory
>
>
>
> That is the target directory cannot be read!!
>
> I first tried this using smb4k with the same result.
>
> Often I get a failure of the mount command with
>
>
>
> mount error 20 = Not a directory
> Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
>
>
> Same happens on
>
>
>
> Linux p3000.local 2.6.23.17-88.fc7 #1 SMP Thu May 15 00:35:10 EDT 2008
> i686 i686 i386 GNU/Linux
>
>
>
>
> so its not a x86_64 problem.
>
> I had to use protocol=RAP to browse in smb4k
>
>
>
>
> Hope you can help
>
>
> regards
>
>
> Stephen
>
>
>
>

More testing.

I can mount XP, Linux Samba, Win98, Win2000, shares without a problem.

I can mount the device using an old version of ubuntu using smbfs
instead of cifs.

I can access files on the device using Nautilus in Fedora 7 and 9 but
this does mount it.


Clearly cifs does not do everything that the previous samba client did.

I suspect the NAS device may have an old version of the smb protocol but
it is only cifs that has a problem with it.

I have found using google that this problem reported many times with
other NAS devices but my search found no solutions.


Again can you help?






_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client

[Christopher R. Hertel]

Gautam Iyer wrote:
:
> If anyone knows what I can do to avoid these errors (or if anyone has
> this working well with recent kernels), please let me know.

I am looking at getting one of these boxes just so I can test against it.
That's not really a ray of hope, I'm just interested.  Again, the best bet
would be to get the software developers to come to a plugfest (the next one
is in September).  :)

Chris -)-----

--
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh@...
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh@...
_______________________________________________
linux-cifs-client mailing list
linux-cifs-client@...
https://lists.samba.org/mailman/listinfo/linux-cifs-client