Tuning transfers from landing to pool

[whartsell]

I am running greyhole 7.5.1 and i have an interesting problem. The transfer to the pool from the landing zone is too fast. It takes a large chunk of my IO during the rsync between the landing and the pool. I am using amahi with my sagetv server to catch all my recordings.
These are files ranging from 3-20GB h264 Mpeg2 ts

the following scenario causes the problem:
one show (show A) is recording which goes to a share called recordings.
when that show (show A) finishes another show will start recording (show B).
Greyhole starts moving Show A to the pool
I decide i want to watch Show B while it is recording.
My Wife decides she wants to watch another recording from yesterday (its already in the pool)

The transfer from the landing zone to the pool is using about 50-100MB/s READ from the landing disk and the same in WRITE to the pool disk(s)
this doesnt leave much overhead for streaming media that may be on the same disk which of course causes stutter across the board

any ideas on how i can lower the priority of the transfer process. I tried adjusting nice on greyhole but it diddnt appear to do much.
My other idea was to freeze the directory and just use a cron to unfreeze but i would prefer something less "poll" like

One more thing...this exact scenario worked fine in WHS so i know my hardware is capable of the throughputs. (yes i know WHS diddnt use a landing disk after PP2)

[gboudreau]

If nice doesn't work for you, your only option is frozen directories.