Samba lockup (excesive growth of locking.tdb)

I have a problem with WD My Cloud 2TB NAS drive (Firmware v04.00.00-607):

I’m experiancing at use of the NAS drive samba regular lockups. My investigation shows that the /run mount  is full because of excesice growth of  locking.tdb file. The restart of samba solves the problem. This happens regulary and therefore it makes the NAS drive unusable.

ll /run/samba
total 20800
-rw-r–r-- 1 root root      40200 Aug 25 10:00 brlock.tdb
-rw------- 1 root root        696 Aug 25 10:00 dbwrap_watchers.tdb
-rw-r–r-- 1 root root    6684672 Jul 30 11:36 gencache.tdb
-rw-r–r-- 1 root root    6684672 Jul 30 11:36 gencache_notrans.tdb
-rw-r–r-- 1 root root 4262068224 Aug 25 10:28 locking.tdb (??? after few minutes)
-rw------- 1 root root      65536 Jun 30 17:49 messages.tdb
-rw-r–r-- 1 root root      65536 Aug 25 10:00 notify.tdb
-rw-r–r-- 1 root root      65536 Aug 25 10:00 notify_index.tdb
-rw-r–r-- 1 root root      65536 Aug 25 10:00 printer_list.tdb
-rw-r–r-- 1 root root      65536 Jun 30 17:49 serverid.tdb
-rw------- 1 root root      65536 Aug 25 10:00 smbXsrv_open_global.tdb
-rw------- 1 root root      65536 Aug 25 10:00 smbXsrv_session_global.tdb
-rw------- 1 root root      65536 Aug 25 10:00 smbXsrv_tcon_global.tdb
-rw------- 1 root root      65536 Aug 25 10:00 smbXsrv_version_global.tdb
-rw-r–r-- 1 root root          5 Jun 30 17:49
drwxr-x— 2 root root         60 Jun 30 17:49 winbindd_privileged

Filesystem      1K-blocks       Used Available Use% Mounted on
rootfs            1968336     809588   1058760  44% /
/dev/root         1968336     809588   1058760  44% /
tmpfs               23296      23296         0 100% /run
tmpfs               40960        128     40832   1% /run/lock
tmpfs               10240          0     10240   0% /dev
tmpfs                5120          0      5120   0% /run/shm
tmpfs              102400       3584     98816   4% /tmp
/dev/root         1968336     809588   1058760  44% /var/log.hdd
ramlog-tmpfs        20480       5120     15360  25% /var/log
/dev/sda4      1918220368 1145635952 733608416  61% /DataVolume
/dev/sda4      1918220368 1145635952 733608416  61% /CacheVolume

Any help would be appreciated.

Thank you for support!

Anything in /var/log/smbd.log?

Tons of (log.smbd.old):

[2014/08/25 14:26:43.653536,  0] (fault_report)
[2014/08/25 14:26:43.653959,  0] (fault_report)
  INTERNAL ERROR: Signal 7 in pid 29003 (4.0.0rc5)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2014/08/25 14:26:43.654342,  0] (fault_report)

And (log.smbd):

[2014/08/25 14:28:04.593180, 0] (tdb_wrap_log) tdb(/var/run/samba/smbXsrv_tcon_global.tdb): expand_file write of 8192 bytes failed (No space left on device) [2014/08/25 14:28:04.593797, 0] (smbXsrv_tcon_create) smbXsrv_tcon_create: global_id (0x7b737881) store failed - NT_STATUS_UNSUCCESSFUL [2014/08/25 14:28:04.594136, 0] (smbXsrv_tcon_disconnect) smbXsrv_tcon_disconnect(0x7b737881, ‘(null)’): failed to delete global key ‘7B737881’: NT_STATUS_NOT_FOUND [2014/08/25 14:28:04.594488, 0] (smbXsrv_tcon_destructor) smbXsrv_tcon_destructor: smbXsrv_tcon_disconnect() failed - NT_STATUS_NOT_FOUND

I had been purchasing and installing the mybooklive 2TB NAS from WD for a long while with zero issues.  Since this device has been replaced by the white wdmycloud 2tb almost everywhere I install it I have random lockups on the device.  I am installing these devices so that multiple computers at a business can backup to them across a network.  I see no one from WD addressing these problems and from this point on will no longer be recommending this product to any of my customers.  I will also be blogging this on multiple technology websites to make sure that my devout followers are informed.  It’s a shame WD does not care more about their customers.  This poor man wrote this post 3 months ago and still has no response.  Time to goto Boston and have a tea party.  You might be suprised with social media how many people you can inform these days about poor products.  I had to learn about your companies insufficient customer support the hard way, and WD will learn the hard way by decreased sales.  You guys think you are the only company making network attached storage?  

Just incase someone from WD actually wants to troubleshoot this issue I will provide my diagnostics.  The last two drives I deployed are both experiencing random lockups but both in different ways.  I bought both devices from different retailers just to show that it’s not a bad batch.  One device totally locks up and can not be pinged, can not be reached by the web gui and obviously can not be reached by attempting to access the network share.  The other device you can just not reach the network share but the web gui and pinging the device is fine.  On both devices a simple power cycle solves the issue for a few days or few weeks.  Backup drives are the last thing that I want to be worrying about at night while I’m trying to sleep.  They are the last point of failure for customers when things get real bad.


I have deployed thousands of WD products over the last 10 years and I will moving my business else where unless someone from your company shows some kind of support.  Please help someone out that has supported your company for so long.

this is a user support forum which WD is nice enough to provide for user-user communication

there are seperate phone and email support options to actually contact WD support. I suggest either contacing support or starting a new thread here with lots of details and other users will generally try to help.

personally for business use I would go with a higher end NAS with RAID protection.

1 Like

Thank you for your response. I am not the only one with such problems. It looks like WD forgets about the firmware as soon the sales of drive starts. It is good enough to sell the drives.

With phone and email support, I have had bad experiences. I got the advices like (from person with no actual knowledge about products and services supported):

Did you check the cables? Or Follow the instruction manual page Or …

However, I will check it for this drive now. It is still misbehaving after 5 months.

I will report my experiences here.