March 23, 201412 yr I'm trying to set up some software on my server (Sabnzbd, Sick Beard, etc). For this, I'm trying to create a spot on the cache drive for things to live. I navigate to Shares, enter a name, a min. free space amount, and choose Only for Use cache disk. I hit add share, and then the page just reloads. Looking at my syslog, I find this: Mar 22 21:54:46 Tower emhttp: shcmd (294): mkdir '/mnt/user/apps' Mar 22 21:54:46 Tower shfs/user: shfs_mkdir: assign_disk: apps (28) No space left on device Mar 22 21:54:46 Tower emhttp: _shcmd: shcmd (294): exit status: 1 Mar 22 21:54:46 Tower emhttp: shcmd (295): rm '/boot/config/shares/apps.cfg' Anyone have any ideas? The cache drive is empty, and has 320gb of space available. I'm a bit stumped as to what's going on. I'm running version 5.0, for the record.
March 23, 201412 yr What did you enter for the min. free space? FYI, I have a 250Gig cache. I define min free as '50Meg'.
March 23, 201412 yr Author Nope, flash drive has 1.93GB free. The only problem seems to be in relation to creating shares only on the cache drive. Everything else works as expected.
March 23, 201412 yr Di you have any enhanced GUI installed? If so it is possible that there is a GUI bug when trying to create a cache only share.
March 23, 201412 yr If you have 'Simple Features' installed, delete it. (If you liked it, delete it and try using DYNAMIX, which is supported in v.5) Delete Simple Features: http://lime-technology.com/forum/index.php?topic=28927.msg279478#msg279478 If itimpi's idea isn't the solution, then Post a full syslog. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog
March 23, 201412 yr I'm trying to set up some software on my server (Sabnzbd, Sick Beard, etc). For this, I'm trying to create a spot on the cache drive for things to live. I navigate to Shares, enter a name, a min. free space amount, and choose Only for Use cache disk. I hit add share, and then the page just reloads. Looking at my syslog, I find this: Mar 22 21:54:46 Tower emhttp: shcmd (294): mkdir '/mnt/user/apps' Mar 22 21:54:46 Tower shfs/user: shfs_mkdir: assign_disk: apps (28) No space left on device Mar 22 21:54:46 Tower emhttp: _shcmd: shcmd (294): exit status: 1 Mar 22 21:54:46 Tower emhttp: shcmd (295): rm '/boot/config/shares/apps.cfg' Anyone have any ideas? The cache drive is empty, and has 320gb of space available. I'm a bit stumped as to what's going on. I'm running version 5.0, for the record. Search for smb-extra.conf. Will let you create shares anywhere on your unRAID server.
March 23, 201412 yr Search for smb-extra.conf. Will let you create shares anywhere on your unRAID server. Does it let you create a cache-only share? That is, a share that resides on the cache drive and is ignored by mover?
March 23, 201412 yr Author Di you have any enhanced GUI installed? If so it is possible that there is a GUI bug when trying to create a cache only share. Nope, stock GUI. If itimpi's idea isn't the solution, then Post a full syslog. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog I've attached it. syslog.txt
March 23, 201412 yr Search for smb-extra.conf. Will let you create shares anywhere on your unRAID server. Does it let you create a cache-only share? That is, a share that resides on the cache drive and is ignored by mover? It will let you create shares anywhere, including subdirectories on the cache drive. The ignoring by the mover has nothing to do with the share. I believe if you name the directory on the cache drive with a "." then the mover script will ignore it. But you can name the share anything you want in the smb-extra file. Do some searching about the feature, and feel free to ask me questions. I use this extensively to create shares to subdirectories on some of my array disks, cache drive, and other custom mounts on my server.
March 23, 201412 yr Search for smb-extra.conf. Will let you create shares anywhere on your unRAID server. Does it let you create a cache-only share? That is, a share that resides on the cache drive and is ignored by mover? It will let you create shares anywhere, including subdirectories on the cache drive. The ignoring by the mover has nothing to do with the share. I believe if you name the directory on the cache drive with a "." then the mover script will ignore it. But you can name the share anything you want in the smb-extra file. Do some searching about the feature, and feel free to ask me questions. I use this extensively to create shares to subdirectories on some of my array disks, cache drive, and other custom mounts on my server. The problem with hidden "." folders is they are not browsable. unRAID 5 introduced cache-only shares, a way of creating a share that is only stored on the cache drive and will be ignored by mover. This is the recommended way in unRAID 5 to have a share that stays on the cache drive.
March 23, 201412 yr It appears there was a disk error when making the reiserfs so I think your cache drive is hosed. As a simple test manually create the share directory on the cache drive and see what happens. You might also want to run a reiserfsck on the drive. You need to fix the problem. There is no need to be using smb-extra.conf or a period in front of the directory name to perform a simple task like creating a cache only user share.
March 23, 201412 yr Author It appears there was a disk error when making the reiserfs so I think your cache drive is hosed. As a simple test manually create the share directory on the cache drive and see what happens. You might also want to run a reiserfsck on the drive. You need to fix the problem. There is no need to be using smb-extra.conf or a period in front of the directory name to perform a simple task like creating a cache only user share. Thank you! I unmounted the drive and ran reiserfsck, and it failed talking about bad blocks. I swapped in a spare drive I had laying around, got it formatted and added in, and I'm able to create shares as expected. I wouldn't have guessed hardware problems, so I appreciate the help!
March 23, 201412 yr The problem with hidden "." folders is they are not browsable. unRAID 5 introduced cache-only shares, a way of creating a share that is only stored on the cache drive and will be ignored by mover. This is the recommended way in unRAID 5 to have a share that stays on the cache drive. Thanks. Since I have not had any issues with my custom shares I have not researched this feature in the past. But I am pretty confident that the smb-extra.conf file allows you to create browseable shares to any place on your array, including ANY folder on your cache drive, any subdirectory on your array, and even to non-unRAID custom mounted drives on your unRAID box. It also lets you map your windows usernames to unRAID usernames - a handy feature. It also lets you implement security on your non-user shares, indicating what users can update, what users can view only, and what users have no access. Let's you decide what is browsable and what is not. It also let's you give your disks intelligent names like "Software" or "Photos", rather than the highly undescriptive "disk1" and "disk2". You might want to check it out! Glad OP got their answer! Cheers.
March 23, 201412 yr Lots of good info but I'm quite positive smb-extra.conf won't fix the OP's problem....
March 24, 201412 yr Lots of good info but I'm quite positive smb-extra.conf won't fix the OP's problem.... Agreed.
Archived
This topic is now archived and is closed to further replies.