[b][i]Moved this to it’s own thread, since the original thread got a little hijacked by myself and autoboy… –Skirge01[/i][/b]
[quote=”autoboy”]I have a WD Green drive as the system drive in my WHS as well. Ripping a BD and playing one back at the same time is a no go. Doing a PC backup at the same time as watching a BD is a mess.[/quote]
Trying to find differences between your and my setups. Are you running a GigE network? I’ve been recording up to 5 HD streams from a combination of OTA and DirecTV while running a backup and comskip, so I can’t imagine it’s a drive pool issue you’re seeing.
[quote]The server is an Athlon X2 4800+ 2GB ram Nvidia 6100/430 board. System drive is a WD green 1TB. Other drive in drivepool is a WD Caviar 750GB. Two recording drives are Seagate 1TB drives.
Should I partition the drivepool drives to 64K clusters as well? Or maybe something like 32K?
[/quote]
The drive’s in the pool should be 64k clusters if you’re primarily storing large files on them. Even SageTV themselves recommend 64k clusters for the recording drives. As farscapesg1 said, you’ll waste some space on small (non-video) files, but I doubt it’ll be any space you’ll actually miss. If you’re going to take the time to change the cluster size, you may as well go to 64k. I don’t know if you’ll gain anything at 32k.
I just checked out my setup to ensure I wasn’t lying and I did take note of one thing. My system drive is a 7200rpm Samsung F1 drive. Prior to any building, I do recall making a conscious decision to do that for the OS drive just in case I may have run into performance issues using a slower drive for the OS. I can’t say whether this has/had any impact or not, though. I do know that the Samsung drive gets hammered every so often, so it certainly isn’t hurting anything.
.
