Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Split level.....Need some help

Featured Replies

Hello

 

I have 4 shares (MOVIES, TV SHOWS, MSUIC and PHOTOS) and 3 data disks

All my shares are set to high-water

For TV SHOWS, the structure is as follow:

TV SHOWS\SHOW|Seasons\Episode

Ex: TV SHOWS\E.R\Season 1\S01 Ep01

What should be the split level to have the possibility to split the Seasons for 1 current show on different disks, and any new Show as well?

 

Thanks

Level 2 I believe. That would allow the E.R. folder to be created on each disk, and then season 1 would reside on one disk, and season 2 COULD potentially reside on another disk depending on space etc. Hopefully I'm following your question correctly.

 

I can't figure out how to embed a link, but take a look at the un-official unRAID manual here

 

http://lime-technology.com/wiki/index.php?title=Un-Official_UnRAID_Manual#Split_level

 

It has a great explanation of how split levels work, and I think it even uses your setup in one of the examples. Hope this helps!

  • 3 months later...

Level 2 I believe. That would allow the E.R. folder to be created on each disk, and then season 1 would reside on one disk, and season 2 COULD potentially reside on another disk depending on space etc.

There is something i still don't really understand when using this scenario. Lets say we're using 2 disks, and we're collecting E.R. episodes using highwater. Initially you have created a user share, which is on disk1 of a 2 disk system (for sake of the example) and you allready have some seasons/episodes in there, so:

 

disk 1 : has a structure with user share described as above (/tvshows/ER/season1/s01ep01.mkv etc

disk 2 : still empty..

 

Now when you start collecting ER episodes, the system will use the high water allocation method and starts filling up disk1 until it's 50% full if i'm correct.

 

My question is, what happens if the 50% is reached? Is the folder structure from disk1 automatically replicated on disk2? And will the system then transparantly save your ER episodes to the structure on disk2 in a season folder, until that one is filled up 50%?

 

Furthermore, using split level 2, the seasons folder is 'kept together as a whole on one disk'. But what if in this example, i've allready got 10 episodes of season 2 on disk 1, and with the 11th episode, the 50% highwater level is reached? Will unraid MOVE the complete season2 folder to the next disk, since the season folder is split level2 and should be kept together?

 

Level 2 I believe. That would allow the E.R. folder to be created on each disk, and then season 1 would reside on one disk, and season 2 COULD potentially reside on another disk depending on space etc.

There is something i still don't really understand when using this scenario. Lets say we're using 2 disks, and we're collecting E.R. episodes using highwater. Initially you have created a user share, which is on disk1 of a 2 disk system (for sake of the example) and you allready have some seasons/episodes in there, so:

 

disk 1 : has a structure with user share described as above (/tvshows/ER/season1/s01ep01.mkv etc

disk 2 : still empty..

 

Now when you start collecting ER episodes, the system will use the high water allocation method and starts filling up disk1 until it's 50% full if i'm correct.

If they are the same size.

My question is, what happens if the 50% is reached?

That depends.

Is the folder structure from disk1 automatically replicated on disk2?

Yes.

And will the system then transparantly save your ER episodes to the structure on disk2 in a season folder, until that one is filled up 50%?

Yes.

Furthermore, using split level 2, the seasons folder is 'kept together as a whole on one disk'. But what if in this example, i've allready got 10 episodes of season 2 on disk 1, and with the 11th episode, the 50% highwater level is reached?

Split level take precedence over allocation.

Will unraid MOVE the complete season2 folder to the next disk, since the season folder is split level2 and should be kept together?

unRAID will never move a file once its in the array.

 

Split level take precedence over allocation.

Ok, so in this particular case, since season 2 was allready allocated on disk1, it stays on disk1 (cuz' its kept together forced by splitlevel), even when the high watermark is reached by adding episodes halfway the season, but if i would create a new season 3 folder, and add episodes to it, that would be created on disk2.

Well that is pretty cool 8) Yesterday i was busy filling up my first drive out of 5 with series and movies, and when it got over the 50% mark, it indeed continued the copying of a new movie on disk2. And when i added another season on a series that was allready on disk1, it continued there, but adding a new series was done on disk2. Nice to see it work :) very powerfull system.

 

Still, calling it 'splitlevel' is confusing IMHO. When you split something, it basically forms multiple 'branches'. But in this case, it's the other way around. If i set a splitlevel of 2, everything after that is not split, it is kept together... the stuff before and including the splitlevelfolder, is split or spanned over multiple disks. I guess it's just how you look at it.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.