I see the following error in Windows 10 file explorer whenever I try to create a new file or save an existing file:
There is not enough space on Public (\\WDMYCLOUDEX2)
I also can’t create files on the NAS from other devices.
I see the following using putty:
root@WDMyCloudEX2 root # df
Filesystem 1K-blocks Used Available Use% Mounted on
%root% 55529 30959 21703 59% /
/dev/ram0 55529 30959 21703 59% /
mdev 254368 64 254304 0% /dev
ubi0:config 12500 796 11032 7% /usr/local/config
/dev/loop0 96128 96128 0 100% /usr/local/modules
tmpfs 1024 0 1024 0% /mnt
tmpfs 40960 4832 36128 12% /var/log
tmpfs 102400 3776 98624 4% /tmp
/dev/sda4 967576 466692 490564 49% /mnt/HD_a4
/dev/sdb4 967576 17700 939556 2% /mnt/HD_b4
/dev/md1 1948697912 860706084 1068498812 45% /mnt/HD/HD_a2
This is a recent problem, first appearing in the last week after months of use without problems.
I connect to the My Cloud using both wireless and wired connections.
Several of my Windows user folders are on the public share.
I’ve just performed a system restore without any improvement, i.e. System > Utilities > Restore to Default > System Only > Restore.
My Dashboard tells me I’m on Firmware 2.11.142, “The My Cloud system firmware is up to date” and the firmware was last updated 2016 April 06.
I’ve cleared the recycle bin using the Dashboard under Settings > General > Services > Recycle Bin > Clear.
The Recycle Bin is not enabled on any shares.
File size isn’t an issue; attempting to create a new text file from Windows Explorer will trigger the error message.
The error is triggered on a public share. I only have a single user, admin, so user quotas doesn’t seem relevant.
A search of the ‘My Cloud EX2’ subforum returns similar experiences to mine, without suggestions other than the points above.
Deleting a few GB of files allows me to save again. It is disappointing and confusing not to be able to use the final 1TB of available space.
Any help would be appreciated.
23 June 2016 edit:
I logged a support ticket on http://support.wdc.com/. My issue was with inodes and the solution involved running the script /usr/sbin/inode_growth.sh.
