I recently modified my 5.0-rc16c server.  I had 3x3TB WD red drives and added 2x3TB green drives and also an old 500GB cache drive (not using the cache drive for anything yet).  My intention is to keep backups and TV shows on the red drives (disk1,disk2) and movies and other static content on the green drives (disk3,disk4).  Bare in mind all of these shares were using disk1,disk2 before the changes and were working fine.  The content I have there I can read from just fine too.

 

Any attempts to write to the shares where I configured to use the new green drives now fails claiming no space left on device.  Here's a sample from syslog:

 

Aug 11 14:49:32 laffy shfs/user: shfs_create: assign_disk: movies/file.mkv (28) No space left on device

 

What have I done wrong here and what do I need to do to correct it?

 

I guess the bigger question is how to you reconfigure a share to use a different set of disks (or, in this case, make new disk restrictions) when you already have content there?

I recently modified my 5.0-rc16c server.  I had 3x3TB WD red drives and added 2x3TB green drives and also an old 500GB cache drive (not using the cache drive for anything yet).  My intention is to keep backups and TV shows on the red drives (disk1,disk2) and movies and other static content on the green drives (disk3,disk4).  Bare in mind all of these shares were using disk1,disk2 before the changes and were working fine.  The content I have there I can read from just fine too.

 

Any attempts to write to the shares where I configured to use the new green drives now fails claiming no space left on device.  Here's a sample from syslog:

 

Aug 11 14:49:32 laffy shfs/user: shfs_create: assign_disk: movies/file.mkv (28) No space left on device

 

What have I done wrong here and what do I need to do to correct it?

 

I guess the bigger question is how to you reconfigure a share to use a different set of disks (or, in this case, make new disk restrictions) when you already have content there?

 

Allocation method and split level only apply to new file writes. Split level has precedence.

Split level for this share is set to 1.  So, that would still allow new files to be written on all disks, right?  Included disks is set to "disk3,disk4", but those disks are still empty right now.

What is the full path?

You mean /mnt/user/movies?

 

I'm just mounting this on my Mac, so it shows up as /Volumes/movies.

To make it even more confusing, I renamed the share movies to old movies.  I then created a new share called movies, but it will not allow me to create the share if I list the included disks--it must be blank to to create the share.  I then go back to add the included disks and it accepts that.  So, I have an empty share, but I'm still unable to write any data to the share (from SMB client or from console (/mnt/user/movies).

If the files are written in /Volumes/movies and not a subdirectory, e.g. /Volumes/movies/new/moviefile.mkv, then split level one is sufficient. What does Settings->Disk Settings show?

Attached screen shot...

Sorry. I meant Settings->Share Settings

Bear in mind I've put the config back to the way it was before.  Before I had the "Included disk(s)" blanked.

That looks like the global settings screenshot for user shares - not those for a specific share. 

 

To achieve what you want I would expect the global settings for user shares to not limit the included shares, but those for individual shares to have included disk limits.

As noted above, you've configured the global settings for shares to only use disk1 and disk2 ... so no share can write to any other disk.    You normally do NOT want to use includes or excludes on the global settings page -- only for the individual shares.

 

I suspect that's exactly what's wrong here.    Just remove the includes from this page and all should be well.  If you have other shares you want to limit to disk1 and disk2, do so on their individual share properties page.

 

Yes, I've had the included disks blank before and still no go.  When I get home from work I'll try it one more time and will create a new share.  Then I'll include snapshots of the current config.  I also have a new disk cache, but I have not enabled it for any of the shares yet.  Was not sure if that might be a factor as well.

 

In hindsight, I feel like I'm overanalyzing the configuration and decided to take a simpler approach by removing the green drives and building the system slowly over time and adding disks as needed.  It seems more useful to let all shares use all drives and not worry about excluding and including disks based on their red/green type.

As noted above, you've configured the global settings for shares to only use disk1 and disk2 ... so no share can write to any other disk.    You normally do NOT want to use includes or excludes on the global settings page -- only for the individual shares.

 

I suspect that's exactly what's wrong here.    Just remove the includes from this page and all should be well.  If you have other shares you want to limit to disk1 and disk2, do so on their individual share properties page.

 

Oh, good grief.  That worked.  The only think I can think of that I did differently was have the share settings included disks as blank BEFORE I created the share.  Guess I have some more options now.  Thanks!