Busybox mount -- Invalid argument

Denys Vlasenko vda.linux at googlemail.com
Tue Jun 1 21:55:15 UTC 2010


On Tuesday 01 June 2010 20:13, Farkas, Tamas (GE, Corporate, consultant) wrote:
> Dear Vda,
> 
> First of all thank you very much for getting back to me on this one.
> To be honest I've managed to mount my remote share (on my WD TV LIVE)
> using NFS, which is obviously the most efficient one...
> but this smbfs/cifs mounting issue still bothers me.
> Your continous help would be highly appreciated:    
> 
> 1.) My client is an ASUS WL500gp (google coded based on Oleg's firmware ; version is the latest -- 1.9.2.7-d-r1612 )
> 2.) Busybox version --> BusyBox v1.16.1 (2010-05-27 21:28:37 MSD) multi-call binary.

...and its .config file is?...

...and what mount -vvv .... says?...

> 4.) The remote samba/cifs share is OK, from the client I can see it
> (please note that my remote share name is now changed to 'disk-0')a 
> 
> [admin at ftomika root]$ smbclient -L wdtvlive
> added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> Got a positive name query response from 192.168.1.100 ( 192.168.1.100 )
> Domain=[FARKASEK] OS=[Unix] Server=[Samba 3.0.28a]
> 
>         Sharename      Type      Comment
>         ---------      ----      -------
>         disk-0         Disk      disk-0
>         IPC$           IPC       IPC Service (WDTV LIVE)
> 
>         Server               Comment
>         ---------            -------
>         FARKASEKTOP
>         FTOMIKA              FTOMIKA
>         WDTVLIVE             WDTV LIVE
> 
>         Workgroup            Master
>         ---------            -------
>         FARKASEK             WDTVLIVE
>         WORKGROUP            FTOMITOP
> 
> 5.) The share could be mounted on other linux on my other PC under linux (and from Win as well)
> 
> 6.) You could find my strace probes in the attachments
> (for now I've only used BB mount on my WL500gp since this SHOULD work ...
> And again 'standard' mounting works from my other pc).

I need straces of "standard" mount not because I want a proff it works,
but because comparing them to bbox strace will tell me where error is.

> Mostly I'm getting this 'Invalid argument' error, but sometime 'mount: bad address' showed up as well.   

593   getuid()                          = 0
593   brk(0)                            = 0x4c7a74
593   brk(0x4c8a74)                     = 0x4c8a74
593   brk(0x4c9000)                     = 0x4c9000
593   getuid()                          = 0
593   geteuid()                         = 0
593   ioctl(2147483647, TIOCNXCL, 0x7fff79a0) = -1 EBADF (Bad file descriptor)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
was ist das? fd = 2^31-1 ??!

593   brk(0x4ca000)                     = 0x4ca000
593   mount("//192.168.1.100/disk-0", "ttt/", "cifs", MS_MANDLOCK|MS_SILENT, "\5") = -1 EINVAL (Invalid argument)

"\5" looks wrong. Pity you dod not try mount -vvv,
knowing its output would be useful.

593   ioctl(2147483647, TIOCNXCL, 0x7fff7958) = -1 EBADF (Bad file descriptor)
593   brk(0x4cb000)                     = 0x4cb000
593   write(2, "mount: mounting //192.168.1.100/disk-0 on ttt/ failed: Invalid argument\n", 72) = 72
593   exit(-1)                          = ?

-- 
vda


More information about the busybox mailing list