SageTV recording storage question

[sunray]

As I understand it, when using multiple storage paths, Sage automatically picks the hard drive with the most free space in which to store its recordings. So if you have several drives its very possible for Sage to scattershot the recordings all over the place. Is there a way to tell Sage to fill up one drive first before it starts storing recordings on another drive? I have several drives of various sizes I want to use to store Sage recordings and I dont want to have to hunt for them if I decide to use a non-Sage media player to view them.

[Opus4]

Originally Posted by sunray

Is there a way to tell Sage to fill up one drive first before it starts storing recordings on another drive?

No, SageTV automatically determines where to store the next recording & that isn't configurable. (Well, except for the new property to tell SageTV where a specific tuner's recordings should go, but I don't believe that would do what you want.)

- Andy

[ignarps]

Is that new feature in a menu somewhere.

That might fix the thing I don't like with the destinations.

I have about 4 HD's right now and 4 tuner cards. I wish sage would use a different path per capture device so it doesn't cause as much filesystem fragmentation or performance bottlenecks.

[Opus4]

The mmc/encoders/<number>/forced_video_storage_path_prefix property for each tuner can be set to the first few characters of a recording dir from the seeker/video_storage property to limit the tuner to a recording directory starting with those characters.

- Andy

[martin]

It would be better if a round-robin strategy was used to choose which path to use for the next recording. The current strategy of choosing the drive with the most available space means that concurrent recordings will all write to the same drive, causing fragmentation and thrashing, at the same time other drives are idle.

With each tuner writing to a separate drive in round robin, the amount of disk arm movement is reduced, as would fragmentation.

I hope this is changed in a future release

[sunray]

Thanks for the information Opus. I was hoping that wasnt the case. Since I have drives of different sizes for storing Sage files, they are going to end up scattered all over the place. Hope Frey considers making some changes here.

[padre]

Originally Posted by Opus4

The mmc/encoders/<number>/forced_video_storage_path_prefix property for each tuner can be set to the first few characters of a recording dir from the seeker/video_storage property to limit the tuner to a recording directory starting with those characters.

- Andy

Andy,

I want to make sure I have this right; In my one machine, I have a PVR250 and a HDHR connected (direct). If I want, I can have the PRV250 record to one drive, the 1st tuner of the HDHR to a 2nd drive and the 2nd tuner of the HDHR to a 3rd drive - using the mmc/encoders/<number>/forced_video_storage_path_prefix property? That statement isn't already there in the properties file, you need to add it. Right?

I have my stuff recording to the root of each drive (not expecting to save much more than 10 files per drive), so an example might be:

mmc/encoders/12345678/forced_video_storage_path_prefix=D
mmc/encoders/23456781/forced_video_storage_path_prefix=E
mmc/encoders/34567812/forced_video_storage_path_prefix=F

Will that work okay? Oh, forgot to ask, what version of Sage do I need to support this?

[Opus4]

Originally Posted by padre

I have my stuff recording to the root of each drive (not expecting to save much more than 10 files per drive), so an example might be:

mmc/encoders/12345678/forced_video_storage_path_prefix=D
mmc/encoders/23456781/forced_video_storage_path_prefix=E
mmc/encoders/34567812/forced_video_storage_path_prefix=F

Will that work okay?

I didn't check the spelling, but provided that the lines are added for the correct number after existing mmc/encoders lines & the recording dir path settings start with those letters, it looks like it should work.

Oh, forgot to ask, what version of Sage do I need to support this?

I don't remember, but it has been a while, so any recent version would have it. What version are you using?

- Andy

[padre]

The version I'll be using for this will be v6.1. It's already running using the PVR card, adding the HDHR on Friday.

Are those property features listed in a document somewhere?

Thanks Andy!

[Opus4]

Originally Posted by padre

Are those property features listed in a document somewhere?

The properties mentioned above? Not really -- they are mentioned in various posts & I believe that's about it.

- Andy