How does SageTV software decide what drive to use?

[MrVining]

Question ?

It is 6:45 PM, at 7:00 PM there are 6 shows about to record...

I have 12 HDDs, they are all very close in the amount of room left ~200GB each, but one (we'll call it HDD a) has 199GB and the rest (HDD b - l) have 200-201GB.

Do those 6 shows all end up getting recorded on HDD a at 7:00?

[Cabalsan]

Is there any way to map a certain tuner to a specific hard drive?

Say all HD broadcasts to a faster SATA, while analog mapped to a slower PATA?

[paulbeers]

Originally Posted by Cabalsan

Is there any way to map a certain tuner to a specific hard drive?

Say all HD broadcasts to a faster SATA, while analog mapped to a slower PATA?

Yes you can map a specific tuner to a hard drive. You just need to update the Sage Properties file.

[Fuzzy]

Originally Posted by paulbeers

Yes you can map a specific tuner to a hard drive. You just need to update the Sage Properties file.

Keep in mind that this might lead to programs being prematurly deleted, as the tuner will not record to any OTHER drive, so if that one fills up, it will have to delete older ones on that drive, instead of recording to the slower drive that has more room.

[MrVining]

Does Sage rotate tuners then? I was thinking about just making a few pools say these two tuners use these 2-3 HDDs, and the other two tuners using the same Ch. line-up use a different 2-3HDDs. This would really only work if the tuners were used round-robin.

PS

Originally Posted by nick_l

Eenie Meenie Miney Moe

Is epic funny!

[Fuzzy]

No, sage does not rotate tuners. It follows the encoder_merit setting in sage.properties.

[MrVining]

Here is my plan, tell me what you think:

5x HD tuners A-E.
5x SD tuners V-Z.
4x 1.5TB HDDs HDD1-HDD4

Tuner A
mmc/encoders/XXX/encoder_merit=5
mmc/encoders/XXX/forced_video_storage_path_prefix=

Tuner B
mmc/encoders/XXX/encoder_merit=4
mmc/encoders/XXX/forced_video_storage_path_prefix=HDD1

Tuner C
mmc/encoders/XXX/encoder_merit=3
mmc/encoders/XXX/forced_video_storage_path_prefix=HDD2

Tuner D
mmc/encoders/XXX/encoder_merit=2
mmc/encoders/XXX/forced_video_storage_path_prefix=HDD3

Tuner E
mmc/encoders/XXX/encoder_merit=1
mmc/encoders/XXX/forced_video_storage_path_prefix=

Tuner V
mmc/encoders/XXX/encoder_merit=5
mmc/encoders/XXX/forced_video_storage_path_prefix=

Tuner W
mmc/encoders/XXX/encoder_merit=4
mmc/encoders/XXX/forced_video_storage_path_prefix=HDD4

Tuner X
mmc/encoders/XXX/encoder_merit=3
mmc/encoders/XXX/forced_video_storage_path_prefix=HDD3

Tuner Y
mmc/encoders/XXX/encoder_merit=2
mmc/encoders/XXX/forced_video_storage_path_prefix=HDD2

Tuner Z
mmc/encoders/XXX/encoder_merit=1
mmc/encoders/XXX/forced_video_storage_path_prefix=

At this point I'm only trying to decide if I want to take 2 of the 1.5s RAID them to a 3TB JBOD for HDD1. Because during prime-time it is more often that 2 shows record then it is any other number of simultaneous recordings.

[martin]

a round-robin strategy was suggested in 2006:

http://forums.sagetv.com/forums/show...89&postcount=5

Originally Posted by 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