On Sat, 19 Feb 2005 12:33:09 -0500, John Brooks <[EMAIL PROTECTED]> wrote: > Okay, I'm a little (lot( shake on network file systems. A friend of > mine is recommending that, instead of giving my mythTV a huge amount > of storage, I throw my disk space at a file server that gets mounted > on the MythTV machine. This way, I have more multi-purpose storage > space. > > Can anyone tell me the merits and flaws of having this sort of setup > in MythTV? Thanks!
When I did my system last summer, I had the backend all working nicely. (I had to tear the whole system down when I moved, so I never actually got to really stress test this in production, with wife and kids beating on it, but I'm confident I was in good shape) My backend, hostname eye, was an Athlon XP1600+, 512meg of ram with three PVR250s and three serial ports to control my directv boxes. It had its primary network (10.10.10.x) on eth0, the on board via-rhine. It also had a 3c905 PCI card running a "Storage Network" (10.10.11.x) This pseudo SAN connection traveled over a crossover cat5 cable and plugged directly into another 3c905 in my fileserver. The fileserver, hostname ark, is almost identical to eye. Athlon 1600, 512meg ram. This box has three 160gig samsung drives in raid5, for a usable amount of 320gig. Eye mounts ark over the point to point net cable. The backend on eye writes the three streams from the three PVR250s over NFS. I tested this with three streams being saved at a time, while watching one frontend on another box doing NFS off the primary network. Both boxes ran Gentoo. Worked like a champ. Unfortunately, for live TV, it was very choppy. I had to mess around with nfs mount options. It worked perfectly with the following entry in fstab: 10.10.11.1:/u/mythtv /u/mythtv nfs rw,noatime,rsize=8192,wsize=8192,soft,nfsvers=3,async _______________ Chris Thompson
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
