Results 1 to 11 of 11

Thread: Problem with WL-HDD and Samba...

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Problem with WL-HDD and Samba...

    Hi all,

    some days ago i upgraded my WL-HDD from Olegs firmware 1.9.2.7-7c to 1.9.2.7-9. After reconfiguring the whole thing (and after tapping through all the pitfalls concerning the changes between the old and the latest firmware ) all seems to be ok so far.
    The NFS mounts are working well and the Samba share appears in my Windows-Workgroup.

    But now i discovered a strange problem: I tried to copy a whole directory with some subdirectories an some files in each from my local HDD to a subdirectory on the WL-HDDs share.
    The copy process starts, the network LED and the HDD-LEDs were blinking fast. After about 7 seconds the transfer stalls. The both LEDs doesn't flicker anymore instead they were static on. The Samba connection drops (after about a minute the Explorer says, that the drive doesn't exist anymore) and connecting the WL-HDD via SSH was impossible. The WL-HDD seems to hang (not crash, after a minute the HDD-LED starts to flash with a several seconds cycle, but also the webinterface doesn't work anymore).

    My WL-HDD starts with the following post-boot script:
    Code:
    #!/bin/sh
    
    # Activate swap 
    swapon /dev/discs/disc0/part1
    
    # Set Standby of internal HDD to 10 minutes
    /usr/local/sbin/hdparm -S 120 /dev/discs/disc0/disc
    
    # Start dropbear SSH server
    /usr/sbin/dropbear
    
    mkdir /tmp/harddisk
    # Mount /tmp/harddisk for Samba
    mount /dev/discs/disc0/part2 /tmp/harddisk
    
    # wait for /opt to mount 
    mount /dev/discs/disc0/part2 /opt 
    i=0 
    while [ $i -le 30 ] 
    do 
      if [ -d /opt/etc ] 
      then 
        break 
      fi 
      sleep 1 
      i=`expr $i + 1` 
    done 
    
    # Start Samba and NMBD
    /usr/sbin/nmbd -D -l /opt/var/log/nmbd.log -s /opt/etc/smb.conf
    /usr/sbin/smbd -D -l /opt/var/log/smbd.log -s /opt/etc/smb.conf
    After boot ps shows the following:
    Code:
      PID  Uid     VmSize Stat Command
        1 admin       580 S   /sbin/init 
        2 admin           SW  [keventd]
        3 admin           SWN [ksoftirqd_CPU0]
        4 admin           SW  [kswapd]
        5 admin           SW  [bdflush]
        6 admin           SW  [kupdated]
        7 admin           SW  [mtdblockd]
       51 admin       380 S   httpd 
       54 admin       408 S   syslogd -m 0 -O /tmp/syslog.log -S -l 7 
       56 admin       364 S   klogd 
       57 admin           SW  [khubd]
       72 1           364 S   [portmap]
       74 admin       504 S   /usr/sbin/statd 
       76 admin           SW  [nfsd]
       78 admin           SW  [lockd]
       79 admin           SW  [rpciod]
       80 admin       484 S   /usr/sbin/mountd 
       83 admin       468 S   watchdog 
       85 admin       344 S   ntp 
       96 admin       480 S   /usr/sbin/dropbear 
       98 admin           SW  [kjournald]
      113 admin       728 S   /usr/sbin/dropbear 
      114 admin       576 S   -sh 
      122 admin       980 S   /usr/sbin/nmbd -D -l /opt/var/log/nmbd.log -s /opt/et
      124 admin       996 S   /usr/sbin/smbd -D -l /opt/var/log/smbd.log -s /opt/et
      126 admin       396 R   ps
    The smb.conf is straight forward:
    Code:
    [global]
    	workgroup = WORKGROUP
    	guest account = nobody
    	security = share
    	browseable = yes
    	guest ok = yes
    	guest only = no
    	log level = 1
    	max log size = 100
    	server string = WLHDD-Share
    
    [share]
    	path = /tmp/harddisk
    
    [share$]
    	path = /tmp/harddisk
    	writable = yes
    	browseable = yes
    	force user = admin
    Unfortunately the log smbd.log is empty.
    After googling I did already some tries (e.g. with ading oplocks = no, level2 oplocks = no, locking = yes to my smb.conf) but with no success.
    With the firmware 1.9.2.7-7c huge filetransfer worked very well.
    Now it seems, that the WL-HDD is flodded with data from the network (100Mb/s) and at a specific point HDD transfer is collapsing

    Addendum:
    I also tried to slow down the Ethernet interface with
    Code:
    et -i eth1 speed 10half
    in my post-boot script, but with no success. It seems that the behaviour depends on the amount of data (the copy process stalles at about the same amount of data transceered)...

    Any ideas?

    Thanks in advance...

    Regards, Thorsten
    Last edited by dl9sec; 22-06-2009 at 18:19.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •