Cannot mount Samba shares with 10.2 - Slackware

This is a discussion on Cannot mount Samba shares with 10.2 - Slackware ; I have a 20th century computer on my back porch (Celeron 400, 128 MB RAM) that I figured Slack would be a good fit for. It runs OK, even with KDE. I set it up when 10.2 was more or ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Cannot mount Samba shares with 10.2

  1. Cannot mount Samba shares with 10.2

    I have a 20th century computer on my back porch (Celeron 400, 128 MB
    RAM) that I figured Slack would be a good fit for. It runs OK, even with
    KDE. I set it up when 10.2 was more or less current, but I break the
    system down during the rainy season. Anywho, I dusted it off and set it
    up yesterday for the summer and found my Samba shares on my Debian
    server no longer mount properly.

    The shares appear to mount properly but I can't even see the local mount
    directory with 'ls' or konqueror until I unmount the shares.

    When I try the 'df' command I get this:

    df
    Filesystem Size Used Avail Use% Mounted on
    /dev/hda1 2.6G 2.2G 465M 83% /
    df: `/home/me/share': Input/output error


    The only thing that changed in the interim was that I upgraded my server
    from Debian stable Sarge to Debian stable Etch. No other machine on my
    little LAN has trouble resolving the shares from FSTAB.

    Here is what my FSTAB entry looks like:

    //server/share /home/me/share smbfs
    credentials=/root/.smbcredentials,dmask=777,fmask=777 0 0


    The smb.conf on the server looks like this:

    [SHARE]
    case sensitive = no
    valid users = me, wife, guest
    path = /home/share
    read only = yes
    hosts allow = 192.168.3.
    hosts deny = 192.168.3.254


    I've also tried it with the 'hosts deny' line remmed out. No dice.

    Manual mounts yield the same result, even if I append uid=44,gid=44.

    The kernel is 2.4.31, Smbclient is:

    # smbclient -V
    Version 3.0.23

    Here is some random gibberish from dmesg:


    smb_get_length: recv error = 5
    smb_trans2_request: result=-5, setting invalid
    smb_retry: caught signal
    smb_get_length: recv error = 5
    smb_trans2_request: result=-5, setting invalid
    smb_retry: caught signal
    parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
    lp0: using parport0 (polling).
    smb_retry: signal failed, error=-3
    smb_retry: signal failed, error=-3


    Here is the log.smbd:
    Quote:
    [2007/06/20 08:39:27, 0] smbd/server.c:main(847)
    smbd version 3.0.23 started.
    Copyright Andrew Tridgell and the Samba Team 1992-2006
    [2007/06/20 08:39:27, 0] param/loadparm.c:map_parameter(2690)
    Unknown parameter encountered: "deny"
    [2007/06/20 08:39:27, 0] param/loadparm.c:lp_do_parameter(3420)
    Ignoring unknown parameter "deny"
    [2007/06/20 09:38:40, 0] smbd/server.c:main(847)
    smbd version 3.0.23 started.
    Copyright Andrew Tridgell and the Samba Team 1992-2006
    [2007/06/20 09:38:40, 0] param/loadparm.c:map_parameter(2690)
    Unknown parameter encountered: "deny"
    [2007/06/20 09:38:40, 0] param/loadparm.c:lp_do_parameter(3420)
    Ignoring unknown parameter "deny"


    I did a search of the usenet and web and seen the problem alluded to,
    but never saw a solution.

    BTW, I can browse samba shares from Konqueror just fine using the
    'smb://server/share' stuff. But if I can't automatically mount a share
    in a specific directory I'm not going to be happy.

    Frankly, the romance of Slackware is beginning to wear somewhat thin
    with me. I don't consider it a feature that I still have to edit my
    xorg.conf to get a bleeding mouse scroll wheel to work. Maybe it is time
    to upgrade to some tweaked XFCE version of Slackware like Zenwalk,
    Vectorlinux, etc., but everything else is working OK, so I'd like to see
    if I can fix this issue.

    Thanks muchly for solving all my problems for me.

  2. Re: Cannot mount Samba shares with 10.2

    Praxis wrote:

    > The only thing that changed in the interim was that I upgraded my server
    > from Debian stable Sarge to Debian stable Etch. No other machine on my
    > little LAN has trouble resolving the shares from FSTAB.


    This "only" thing that changed is a major distribution update, including
    an update from samba 3.0.14 to 3.0.24

    >
    > The smb.conf on the server looks like this:
    >
    > [SHARE]
    > case sensitive = no
    > valid users = me, wife, guest
    > path = /home/share
    > read only = yes
    > hosts allow = 192.168.3.
    > hosts deny = 192.168.3.254
    >
    >
    > I've also tried it with the 'hosts deny' line remmed out. No dice.
    >
    > Manual mounts yield the same result, even if I append uid=44,gid=44.
    >
    > The kernel is 2.4.31, Smbclient is:
    >
    > # smbclient -V
    > Version 3.0.23


    And the 2.4 kernels a not too recent either. That means the smbfs
    implementation is plain old.

    The smbclient version is not important for mounting smbfs share.

    >
    > Here is some random gibberish from dmesg:
    >
    >
    > smb_get_length: recv error = 5
    > smb_trans2_request: result=-5, setting invalid
    > smb_retry: caught signal
    > smb_get_length: recv error = 5
    > smb_trans2_request: result=-5, setting invalid
    > smb_retry: caught signal
    > parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
    > lp0: using parport0 (polling).
    > smb_retry: signal failed, error=-3
    > smb_retry: signal failed, error=-3
    >


    I'm not sure about the source of these messages.
    It could be from the smbfs kernel module.

    >
    > Here is the log.smbd:
    > Quote:
    > [2007/06/20 08:39:27, 0] smbd/server.c:main(847)
    > smbd version 3.0.23 started.
    > Copyright Andrew Tridgell and the Samba Team 1992-2006
    > [2007/06/20 08:39:27, 0] param/loadparm.c:map_parameter(2690)
    > Unknown parameter encountered: "deny"
    > [2007/06/20 08:39:27, 0] param/loadparm.c:lp_do_parameter(3420)
    > Ignoring unknown parameter "deny"
    > [2007/06/20 09:38:40, 0] smbd/server.c:main(847)
    > smbd version 3.0.23 started.
    > Copyright Andrew Tridgell and the Samba Team 1992-2006
    > [2007/06/20 09:38:40, 0] param/loadparm.c:map_parameter(2690)
    > Unknown parameter encountered: "deny"
    > [2007/06/20 09:38:40, 0] param/loadparm.c:lp_do_parameter(3420)
    > Ignoring unknown parameter "deny"


    Log.smbd has nothing to do with mounting a smbfs share. Its from
    samba the smb *server* implementation. Are you running samba on
    that system? This looks like some errors in smb.conf.
    This log might have been generated by running smbclient which
    is part of the samba package. It has nothing to do with
    smbmount (or mount -t smbfs).

    >
    >
    > I did a search of the usenet and web and seen the problem alluded to,
    > but never saw a solution.
    >
    > BTW, I can browse samba shares from Konqueror just fine using the
    > 'smb://server/share' stuff. But if I can't automatically mount a share
    > in a specific directory I'm not going to be happy.


    Just guessing, but the 'smb://server/share' implementation in Konqueror
    is probably just a graphic shell around 'smbclient'.

    Try running a 2.6 kernel - there are 2.6.13 kernel packages in slackware
    10.2 under testing/packages/linux-2.6.13. That will give you a more
    recent smbfs implementation *and* cifs support.


    Regards,

    Kees.

    --
    Kees Theunissen.

  3. Re: Cannot mount Samba shares with 10.2

    > Try running a 2.6 kernel - there are 2.6.13 kernel packages in slackware
    > 10.2 under testing/packages/linux-2.6.13. That will give you a more
    > recent smbfs implementation *and* cifs support.
    >
    >
    > Regards,
    >
    > Kees.


    Thanks for the suggestion, Kees, but I just did a slapt-get --upgrade, and
    that installed a later version of Samba and all was well.



    > Executing install script for samba-3.0.25a-i486-1_slack10.2...
    >
    > Package samba-3.0.23-i486-2_slack10.2 upgraded with new

    package /var/slapt-get/./patches/packages/samba-3.0.25a-i486-1_slack10.2.tgz.

    Though Slack is quite a bit more of a PITA than some other distros, I have
    to say, if gives "spanking" performance on my old rig, even running KDE. I
    screwed around with it for hours running updates and many fairly heavy
    programs and my memory footprint is still minuscule, according to htop I'm
    using 70 out of 122 MB of RAM and 43 out of 454 MB of swap and less than
    10% of my 400 MHz Celeron running 70 processes including Firefox, Kate,
    Knode, KFM, XMMS & multiple terminals.


+ Reply to Thread