So what allocation method do you use with this set up?

 

V

 

I think you're confused. His share settings don't matter. He has the shares read only, so they are never written to. He goes directly to each disk to write anything to the server.

 

Peter

 

So what allocation method do you use with this set up?

 

V

 

I think you're confused. His share settings don't matter. He has the shares read only, so they are never written to. He goes directly to each disk to write anything to the server.

 

Peter

 

 

So you're creating the share folder so its available to others, but writing to the server is a completely different thing and with exception to the disk location and export mode the other settings under 'share' are irrelevant?  You're right I am confused, but I think you're helping clear it up.

 

Thanks.

V

 

 

Could someone check this for me:

 

Movies (Share)

-A (Folder)

--American Gangster (Folder)

---American Gangster.mkv + American Gangster.jpg + American Gangster-fanart + American Gangster-trailer + American Gangster.nfo

-A (Folder)

--Avatar (Folder)

---Avatar.mkv + Avatar.jpg + Avatar-fanart + Avatar-trailer + Avatar.nfo

 

- B (Folder)

---Backdraft (Folder)

---Backdraft.mkv + Backdraft.jpg + Backdraft-fanart + Backdraft-trailer + Backdraft.nfo

 

SPLIT LEVEL 2

 

 

I want to use a folder for each letter because 1900 movies in one directory would be hard work especially keeping track when I'm filling the server.

 

I want each separate movie folder to stay intact.

 

Will split level 2 work OK for this? Can anyone tell why I should maybe use another structure?

 

 

My config is:

 

One user share called 'netstorage'. High Water Allocation, nothing entered for split. Within this directory is Movies TvShows MP3s Storage and Backup.

 

I ignore everything else. UnRaid fills the drives as it needs to, and I don't sweat it. Simplest config I could think of, I'm a huge fan of K.I.S.S.

 

This shows up on every PC in the house as \\NAS\NetStorage\

 

One mount, has everything.

 

The FUSR creates directory structures on each disk, completely transparent to the user. It'll take care of itself.

My config is:

 

One user share called 'netstorage'. High Water Allocation, nothing entered for split. Within this directory is Movies TvShows MP3s Storage and Backup.

 

I ignore everything else. UnRaid fills the drives as it needs to, and I don't sweat it. Simplest config I could think of, I'm a huge fan of K.I.S.S.

 

This shows up on every PC in the house as \\NAS\NetStorage\

 

One mount, has everything.

 

The FUSR creates directory structures on each disk, completely transparent to the user. It'll take care of itself.

 

I too am a big fan of K.I.S.S.  Some questions for anyone smarter than me (ie everyone haha because after reading the user guides I'm still dazed and confused)...

 

* So I don't need to create anything at all on each disk using this approach?  Unraid automatically creates everything it needs on each disk?  So just specify the share settings, including the disks to include, and that's it - nothing else to do?

* How are the other folders created?  Just create them in the mounted share under Windows/Mac etc?

* Why the High Water method?  I was thinking of using the Fill-up method.  I suppose if I understand High Water correctly, the disks will fill up anyway right?

* How does High Water avoid the issue of running out of space in the middle of writing a file (which is why you need to set a minimum free space threshold when using the Fill-Up method)?

  --> re-reading the Unofficial User Manual (http://lime-technology.com/wiki/index.php?title=Un-Official_UnRAID_Manual#High_Water) I see that High Water fills each disk in a fairly uniform way so the only time a file can't be written is when all the disks in the share are nearly full.

* Does using High Water scatter all your files over the disks, making recovery after a failed disk messier?

* Speaking of recovery, what's the preferred method of reading data off the disks if the whole array fails (eg after losing 2 disks)? I read somewhere you need to physically pull out the drive and drop it into say a Windows PC and use a ReiserFS utility to read it, but is it possible to somehow just share out each individual disk and read the contents via the network?

 

You create the folder on the mounted User Share, copy files over, and the directory structure will be written to each disk as it is needed for space by the allocation method. I personally use Split Level 0--which means I have to create the directory structure each time I add a new drive manually--because I wasn't really certain at the time how I was going to design my system, and how many User Shares I would require. I don't have too many drives, so it's not a big issue, but if you plan to keep adding drives and prefer a "set it and forget it" system, then I'd suggest carefully designing your system to your needs now and in the future, and choose the right split level and drive allocation you require.

 

I don't think the allocation methods would make your recovery any more arduous, as eventually the drives will all be filled up evenly.  If you think about it, filling up one drive at a time may cause a higher failure rate as it'd put the drive under my stress over a shorter period of time. But I haven't actually thought deeply into it.

 

In terms of recovery, I'm not certain as I haven't experienced it. Someone else could answer better (probably the above questions too )