August 26, 201411 yr unRAID OS Version: 6.0-beta7-x86_64 Description: Can't create a share with "cache only" Fresh install. Copied old config (5.0.5) except go file over to the usb. Reformated my cache to btrfs. Cache disk: 991 GB free formatted as btrfs Array: Total 442 GB free (min. disk 126GB free) formatted as resiserfs Expected results: The share and should be created Actual results: It just silently exists the operation. And the share is not created. Syslog Aug 26 19:19:09 Tower emhttp: shcmd (224): mkdir '/mnt/user/test' Aug 26 19:19:09 Tower shfs/user: shfs_mkdir: assign_disk: test (28) No space left on device Aug 26 19:19:09 Tower emhttp: _shcmd: shcmd (224): exit status: 1 Aug 26 19:19:09 Tower emhttp: shcmd (225): rm '/boot/config/shares/test.cfg' Aug 26 19:19:09 Tower emhttp: shcmd (226): :>/etc/samba/smb-shares.conf Aug 26 19:19:09 Tower avahi-daemon[1821]: Files changed, reloading. Aug 26 19:19:09 Tower emhttp: Restart SMB... Aug 26 19:19:09 Tower emhttp: shcmd (227): killall -HUP smbd Aug 26 19:19:09 Tower emhttp: shcmd (228): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Aug 26 19:19:09 Tower avahi-daemon[1821]: Files changed, reloading. Aug 26 19:19:09 Tower avahi-daemon[1821]: Service group file /etc/avahi/services/smb.service changed, reloading. Aug 26 19:19:09 Tower emhttp: shcmd (229): ps axc | grep -q rpc.mountd Aug 26 19:19:09 Tower emhttp: _shcmd: shcmd (229): exit status: 1 Aug 26 19:19:09 Tower emhttp: shcmd (230): /usr/local/sbin/emhttp_event svcs_restarted Aug 26 19:19:09 Tower emhttp_event: svcs_restarted Aug 26 19:19:10 Tower avahi-daemon[1821]: Service "Tower" (/etc/avahi/services/smb.service) successfully established.
August 26, 201411 yr It would be a good idea to include the syslog. It would be a good idea is necessary to include the syslog.
August 26, 201411 yr Something is a little "off" when you first format the cache drive as BTRFS. Just stop and restart the array and it should work. Also, if you already enabled Docker, check the settings on your Docker share and make sure it is "cache only"
August 26, 201411 yr Author It would be a good idea to include the syslog. It would be a good idea is necessary to include the syslog. Yes off-cause. I have updated the original post. It seems it tries to mkdir into /mnt/user instead of /mnt/cache
August 26, 201411 yr Author Something is a little "off" when you first format the cache drive as BTRFS. Just stop and restart the array and it should work. Also, if you already enabled Docker, check the settings on your Docker share and make sure it is "cache only" Edit: You were right. After I restarted the array the folders popped up. (And the appdata folder is set to cache only) I'll try to restart the array when the kids has finished their movie. But I'm quite sure this has already been done after the BTRFS format. Regarding Docker I don't share that folder, it's stored in the /mnt/cache/appdata/docker. Thanks for your reply!
September 20, 201411 yr Can this be closed now? Not unless you made changes that fix this in the upcoming beta 10, or consider this to be either reasonable behaviour or user error. I saw the same problem earlier, "No space left on device" when trying to create a cache only share on a newly formatted BTRFS drive. I could however create the folder manually with "mkdir /mnt/cache/appdata" and start using it right away, and couldn't reproduce it after a restart so I didn't think too much about it back then. Seeing this topic and reading ljm42's post made me remember I had this problem, so I sacrificed the cache drive on my lab server and reproduced it with the following steps: 1. Set cache drive to BTRFS 2. Start array 3. Format unformatted disks 4. Try to add a cache only share "appdata". Silently fails in the web ui and a "No space left on device" message in the log. 5. Repeat 4, identical result. 6. Stop array 7. Start array 8. Try to add a cache only share "appdata". OK System Log attached. 6b9_btrfscache_cacheonlyfailed.txt.gz
September 21, 201411 yr Can this be closed now? Not unless you made changes that fix this in the upcoming beta 10, or consider this to be either reasonable behaviour or user error. I saw the same problem earlier, "No space left on device" when trying to create a cache only share on a newly formatted BTRFS drive. I could however create the folder manually with "mkdir /mnt/cache/appdata" and start using it right away, and couldn't reproduce it after a restart so I didn't think too much about it back then. Seeing this topic and reading ljm42's post made me remember I had this problem, so I sacrificed the cache drive on my lab server and reproduced it with the following steps: 1. Set cache drive to BTRFS 2. Start array 3. Format unformatted disks 4. Try to add a cache only share "appdata". Silently fails in the web ui and a "No space left on device" message in the log. 5. Repeat 4, identical result. 6. Stop array 7. Start array 8. Try to add a cache only share "appdata". OK System Log attached. Awesome report, thank you! I see what the problem is now...
Archived
This topic is now archived and is closed to further replies.