Bigdady92 Posted November 29, 2011 Posted November 29, 2011 For YEARS I have never had the problem with space on my unRAID system. Today I ran across the nefarious error "Not Enough space on the disk." Years I've had no problem then one of my disks decides it wants to hold every single solitary chunk of data and fills itself to full. The system is not carrying the data over to the next drive. I combed the forums, didn't see an answer to my problem, what am I missing? All my data is in one share to make life easy for me. From there I have several folders underneath, and more folders underneath that. Here is my setup: User Shares: Share name: data Allocation Method: High-Water Min Free Space: 10000 Split Level: 99 Export (NFS): /data Syslog obvious parts cut out: Nov 28 19:55:56 ChainDog logger: ./data/Bittorrent/Finished/MAME 0.144 CHDs/mach3/mach3.chd Nov 28 19:55:56 ChainDog logger: >f+++++++++ data/Bittorrent/Finished/MAME 0.144 CHDs/mach3/mach3.chd Nov 28 19:56:22 ChainDog emhttp: shcmd (146): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Nov 28 19:56:22 ChainDog emhttp: shcmd (147): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Nov 28 19:56:22 ChainDog emhttp: shcmd (148): echo '40 3 * * * /usr/local/sbin/mover 2>&1 >/dev/null' >>/var/spool/cron/crontabs/root Nov 28 19:56:22 ChainDog emhttp: shcmd (149): crontab /var/spool/cron/crontabs/root Nov 28 19:56:22 ChainDog emhttp: shcmd (150): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Nov 28 19:56:22 ChainDog emhttp: shcmd (151): cp /etc/exports- /etc/exports Nov 28 19:56:22 ChainDog emhttp: shcmd (152): echo \"/mnt/user/data\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=100' '/data' >>/etc/exports Nov 28 19:56:22 ChainDog emhttp: shcmd (153): killall -HUP smbd Nov 28 19:56:22 ChainDog emhttp: shcmd (154): /etc/rc.d/rc.nfsd restart | logger Nov 28 19:56:22 ChainDog mountd[3424]: Caught signal 15, un-registering and exiting. Nov 28 19:56:23 ChainDog kernel: nfsd: last server has exited, flushing export cache Nov 28 19:56:24 ChainDog logger: Starting NFS server daemons: Nov 28 19:56:24 ChainDog logger: /usr/sbin/exportfs -r Nov 28 19:56:24 ChainDog exportfs[3541]: invalid netmask `data' for Nov 28 19:56:24 ChainDog logger: /usr/sbin/rpc.nfsd 8 Nov 28 19:56:24 ChainDog logger: /usr/sbin/rpc.mountd Nov 28 19:58:14 ChainDog shfs: shfs_write: write: (28) No space left on device Nov 28 19:58:18 ChainDog last message repeated 44 times Nov 28 20:02:14 ChainDog emhttp: shcmd (155): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Nov 28 20:02:14 ChainDog emhttp: shcmd (156): cp /etc/exports- /etc/exports Nov 28 20:02:14 ChainDog emhttp: shcmd (157): echo \"/mnt/user/data\" '-async,no_subtree_check,anongid=0,anonuid=0,all_squash,fsid=100' '/data' >>/etc/exports Nov 28 20:02:14 ChainDog emhttp: shcmd (158): killall -HUP smbd Nov 28 20:02:14 ChainDog emhttp: shcmd (159): /etc/rc.d/rc.nfsd restart | logger Nov 28 20:02:14 ChainDog mountd[3553]: Caught signal 15, un-registering and exiting. Nov 28 20:02:15 ChainDog kernel: nfsd: last server has exited, flushing export cache Nov 28 20:02:16 ChainDog logger: Starting NFS server daemons: Nov 28 20:02:16 ChainDog logger: /usr/sbin/exportfs -r Nov 28 20:02:16 ChainDog exportfs[3625]: invalid netmask `data' for Nov 28 20:02:16 ChainDog logger: /usr/sbin/rpc.nfsd 8 Nov 28 20:02:16 ChainDog logger: /usr/sbin/rpc.mountd And on a fresh boot with a fresh syslog: syslog.txt
Bigdady92 Posted November 30, 2011 Author Posted November 30, 2011 oddly, after the switch back to high water from FILL, I had to physically force the machine to cold boot. Then I got the dreaded parity check which I let run over night. In the morning I started up the raid array and watched as unRaid started moving data around to balance out my storage. I started a large download and was able to see that unRaid was taking up a completely new disk and not going back to the full one.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.