Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Version 3 should work... the internal filesize is a 64bit value... Do a search for NFS v2/v3 and you can read up on it all. (It is boring and just a simple footnote...) On Tue, 2 Aug 2005, Mark Knecht wrote: On 8/2/05, Bryan Whitehead [EMAIL PROTECTED] wrote: BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the 4gb filesize limit. OK, I've built the kernels on both machines and have support for both V3 and V3 clients and servers built in. Ethereal tells me now that I'm using V3. We'll see if that stays on line longer than the V2 protocol did. thanks! - Mark -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Right, sorry. I should have responded back. The system was rebuilt with V3 and V4 support. I'm running version 3. It's now been up for about 4 days without going offline again so I suppose it's fixed. Thanks to all for the help. I was hesitant to say it was fixed for fear it would immediately go offline...;-) Cheers, Mark On 8/8/05, Bryan Whitehead [EMAIL PROTECTED] wrote: Version 3 should work... the internal filesize is a 64bit value... Do a search for NFS v2/v3 and you can read up on it all. (It is boring and just a simple footnote...) On Tue, 2 Aug 2005, Mark Knecht wrote: On 8/2/05, Bryan Whitehead [EMAIL PROTECTED] wrote: BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the 4gb filesize limit. OK, I've built the kernels on both machines and have support for both V3 and V3 clients and servers built in. Ethereal tells me now that I'm using V3. We'll see if that stays on line longer than the V2 protocol did. thanks! - Mark -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Quick... knock on wood!On 8/8/05, Mark Knecht [EMAIL PROTECTED] wrote: Right, sorry. I should have responded back. The system was rebuiltwith V3 and V4 support. I'm running version 3. It's now been up forabout 4 days without going offline again so I suppose it's fixed.Thanks to all for the help. I was hesitant to say it was fixed for fear it would immediately gooffline...;-)Cheers,MarkOn 8/8/05, Bryan Whitehead [EMAIL PROTECTED] wrote: Version 3 should work... the internal filesize is a 64bit value... Do a search for NFS v2/v3 and you can read up on it all. (It is boring and just a simple footnote...) On Tue, 2 Aug 2005, Mark Knecht wrote: On 8/2/05, Bryan Whitehead [EMAIL PROTECTED] wrote: BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the 4gb filesize limit.OK, I've built the kernels on both machines and have support for both V3 and V3 clients and servers built in. Ethereal tells me now that I'm using V3. We'll see if that stays on line longer than the V2 protocol did. thanks! - Mark -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list-- gentoo-user@gentoo.org mailing list-- Michael E. CruteSoftware DeveloperSoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates?
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Oh oops... sorry... thats the way Windoze works (or rather doesn't work). Glad everything finally worked out for you. -MikeOn 8/9/05, Michael Crute [EMAIL PROTECTED] wrote: Quick... knock on wood!On 8/8/05, Mark Knecht [EMAIL PROTECTED] wrote: Right, sorry. I should have responded back. The system was rebuiltwith V3 and V4 support. I'm running version 3. It's now been up forabout 4 days without going offline again so I suppose it's fixed.Thanks to all for the help. I was hesitant to say it was fixed for fear it would immediately gooffline...;-)Cheers,MarkOn 8/8/05, Bryan Whitehead [EMAIL PROTECTED] wrote: Version 3 should work... the internal filesize is a 64bit value... Do a search for NFS v2/v3 and you can read up on it all. (It is boring and just a simple footnote...) On Tue, 2 Aug 2005, Mark Knecht wrote: On 8/2/05, Bryan Whitehead [EMAIL PROTECTED] wrote: BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the 4gb filesize limit.OK, I've built the kernels on both machines and have support for both V3 and V3 clients and servers built in. Ethereal tells me now that I'm using V3. We'll see if that stays on line longer than the V2 protocol did. thanks! - Mark -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list-- gentoo-user@gentoo.org mailing list-- Michael E. CruteSoftware Developer SoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates? -- Michael E. CruteSoftware DeveloperSoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates?
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
When you emerge nfs use the tcpd use flag to get TCP support. -MikeOn 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: Hi, I have set up a large NFS mount for use as remote storage for ourMythTV server. It works, but since setting it up the mythbackendprogram has twice shut down in the middle of the night. Prior tosetting up this storage mythbackend had never, to the best of my knowledge, ever shut down unexpectantly. Obviously I'm suspicious thatthis change is the root cause. From the MythTV-Users list I've seen people talking about using NFSdevices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this. Any comments on whether this is likely to yield better results andhow I might look at going about it? Pointers to the right Gentoo docsmuch appreciated. Thanks,Mark--gentoo-user@gentoo.org mailing list-- Michael E. Crute Software DeveloperSoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates?
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: From the MythTV-Users list I've seen people talking about using NFS devices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this. IIRC, there is also a kernel config option that enables NFS over TCP, which you need to enable on the server (maybe also client?). Matt -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Matthew Cline wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: From the MythTV-Users list I've seen people talking about using NFS devices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this. IIRC, there is also a kernel config option that enables NFS over TCP, which you need to enable on the server (maybe also client?). You should also add 'tcp' to your mount options in fstab. See 'man mount'. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Matthew, Michael and Richard, Thanks for the responses. They seem to outline the options pretty clearly. One question - once I get it converted and I think I'm running NFS using tcp, how do I determine that I actually am? Thanks, Mark On 8/2/05, Richard Fish [EMAIL PROTECTED] wrote: Matthew Cline wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: From the MythTV-Users list I've seen people talking about using NFS devices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this. IIRC, there is also a kernel config option that enables NFS over TCP, which you need to enable on the server (maybe also client?). You should also add 'tcp' to your mount options in fstab. See 'man mount'. -Richard -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 02 August 2005 17:43, Mark Knecht wrote: Matthew, Michael and Richard, Thanks for the responses. They seem to outline the options pretty clearly. One question - once I get it converted and I think I'm running NFS using tcp, how do I determine that I actually am? Several possibilities: - Close the NFS UDP port on the server. If it still works you ae using TCP. - Analyse the traffic with tcpdump or some such. - Use netstat. Uwe -- 95% of all programmers rate themselves among the top 5% of all software developers. - Linus Torvalds http://www.uwix.iway.na (last updated: 20.06.2004) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
I would use 'sudo netstat -lp | grep nfs' to see what nfs is listening on. -MikeOn 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: Matthew, Michael and Richard, Thanks for the responses. They seem to outline the options pretty clearly. One question - once I get it converted and I think I'm running NFSusing tcp, how do I determine that I actually am? Thanks,MarkOn 8/2/05, Richard Fish [EMAIL PROTECTED] wrote: Matthew Cline wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote:From the MythTV-Users list I've seen people talking about using NFS devices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this.IIRC, there is also a kernel config option that enables NFS over TCP, which you need to enable on the server (maybe also client?).You should also add 'tcp' to your mount options in fstab.See 'man mount'. -Richard -- gentoo-user@gentoo.org mailing list--gentoo-user@gentoo.org mailing list -- Michael E. CruteSoftware DeveloperSoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates?
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: I would use 'sudo netstat -lp | grep nfs' to see what nfs is listening on. -Mike Thanks Mike, it appears that both ends are currently listening on tcp which is good. However, am I not supposed to also use the tcp mount option on the mythbackend server to tell it to mount /video using tcp? The man pages tell me the default for NFS mounts is udp. Or does the tcp build flag for nfs-utils override all of this? Cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: Using the tcp flag when you mount should override the default behavior for nfs to use udp. I'm not sure if its strictly necessary but what the heck, it can't hurt. -Mike That's what I thought also. However, even though I can see the server is listening on tcp it seems to still have a udp component: dragonfly ~ # netstat -lp | grep nfs tcp0 0 *:nfs *:* LISTEN - udp0 0 *:nfs *:* - dragonfly ~ # This side is the mythbackend server which is mounting the remote NFS partition. The remote nfs server looks the same way. What I can't figure out yet is how to be sure the actual mount happened using tcp. Sure, I placed it in the mount command in fstab: dragonfly ~ # cat /etc/fstab | grep video myth14:/video /video nfs auto,user,rw,_netdev,tcp,rsize=8192 0 0 dragonfly ~ # but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Matt -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Matt I could give it a try. I've never used ethereal so I don't know how it works at all. Emerging it now to try it out. Thanks, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show that I'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems to verify that both options I was looking for ar indeed working. Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. It happened again just a few minutes ago. This all started happening after I brought this NFS mount on-line as storage for the mythbackend server. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really this disk/PC/network connection. Thanks again for your help. Cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Mark, Here is my suggestion to get the best of both worlds (note my limited knowledge of mythtv). Setup a shell script to copy all your video files from the myth capture directory over to the nfs share and delete the files thus clearing your local space and also allowing you to capture 135 hours. You could even cron it so you don't have to think about it. Pardon me if this is a gross misunderstanding of mythtv but if its not it should work like a charm. -MikeOn 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used.Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show thatI'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems toverify that both options I was looking for ar indeed working.Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. Ithappened again just a few minutes ago. This all started happeningafter I brought this NFS mount on-line as storage for the mythbackendserver. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really thisdisk/PC/network connection. Thanks again for your help.Cheers,Mark--gentoo-user@gentoo.org mailing list-- Michael E. CruteSoftware DeveloperSoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates?
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
The best way is to ask the portmapper (example below): [EMAIL PROTECTED] ~]$ rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 1000241 udp921 status 1000241 tcp928 status 172 udp 1000 ypbind 171 udp 1000 ypbind 172 tcp 1003 ypbind 171 tcp 1003 ypbind 1000111 udp647 rquotad 1000112 udp647 rquotad 1000111 tcp669 rquotad 1000112 tcp669 rquotad 132 udp 2049 nfs 133 udp 2049 nfs 134 udp 2049 nfs 132 tcp 2049 nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1000211 udp 32768 nlockmgr 1000213 udp 32768 nlockmgr 1000214 udp 32768 nlockmgr 1000211 tcp 32768 nlockmgr 1000213 tcp 32768 nlockmgr 1000214 tcp 32768 nlockmgr 151 udp165 mountd 151 tcp165 mountd 152 udp165 mountd 152 tcp165 mountd 153 udp165 mountd 153 tcp165 mountd [EMAIL PROTECTED] ~]$ Look at the nfs service. It has udp and tcp. I also have protocol 2, 3, and 4 available to clients. On Tue, 2 Aug 2005, Mark Knecht wrote: Matthew, Michael and Richard, Thanks for the responses. They seem to outline the options pretty clearly. One question - once I get it converted and I think I'm running NFS using tcp, how do I determine that I actually am? Thanks, Mark On 8/2/05, Richard Fish [EMAIL PROTECTED] wrote: Matthew Cline wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: From the MythTV-Users list I've seen people talking about using NFS devices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this. IIRC, there is also a kernel config option that enables NFS over TCP, which you need to enable on the server (maybe also client?). You should also add 'tcp' to your mount options in fstab. See 'man mount'. -Richard -- gentoo-user@gentoo.org mailing list -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
cat /proc/mounts | grep -E 'nfs.*tcp' On Tue, 2 Aug 2005, Mark Knecht wrote: Matthew, Michael and Richard, Thanks for the responses. They seem to outline the options pretty clearly. One question - once I get it converted and I think I'm running NFS using tcp, how do I determine that I actually am? Thanks, Mark On 8/2/05, Richard Fish [EMAIL PROTECTED] wrote: Matthew Cline wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: From the MythTV-Users list I've seen people talking about using NFS devices but recommending that they be set up with TCP instead of UDP. So far I haven't yet found any Gentoo docs on how to do this. IIRC, there is also a kernel config option that enables NFS over TCP, which you need to enable on the server (maybe also client?). You should also add 'tcp' to your mount options in fstab. See 'man mount'. -Richard -- gentoo-user@gentoo.org mailing list -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Mike, Thanks for the idea. I like the idea of being able to record locally for 15 hours safely and then just using the new NFS storage for playback only, but I think it won't work from a practical standpoint: 1) MythTV runs in conjunction with MySQL which is managing the data files. If I simply move the data files to some other location then MySQL won't know where they are for playback. 2) As far as I know MythTV expects all the data file to be in a single location for playback. I've never heard of anyone having multiple disks for playback, but if they could then your idea would possibly work. I like the idea though and will do some research to see if there's a practical solution. Possibly some sort of logical disk drive? That's a bit beyond my meager skill set. Thanks, Mark On 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: Mark, Here is my suggestion to get the best of both worlds (note my limited knowledge of mythtv). Setup a shell script to copy all your video files from the myth capture directory over to the nfs share and delete the files thus clearing your local space and also allowing you to capture 135 hours. You could even cron it so you don't have to think about it. Pardon me if this is a gross misunderstanding of mythtv but if its not it should work like a charm. -Mike On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show that I'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems to verify that both options I was looking for ar indeed working. Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. It happened again just a few minutes ago. This all started happening after I brought this NFS mount on-line as storage for the mythbackend server. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really this disk/PC/network connection. Thanks again for your help. Cheers, Mark -- gentoo-user@gentoo.org mailing list -- Michael E. Crute Software Developer SoftGroup Development Corporation In a world without walls and fences, who needs windows and gates? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the 4gb filesize limit. run nftstat -s (on the server) and nfsstat -c (on the client) to see what version of NFS you are using (note: what version of NFS you are using is not related to the transport - udp/tcp). I use bigger than 4GB files on Linux server/client all the time to move DVD iso's to machines with better burners... you are running the 2.6 kernel? On Tue, 2 Aug 2005, Bryan Whitehead wrote: What filesystem are you exporting over NFS? On Tue, 2 Aug 2005, Mark Knecht wrote: On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show that I'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems to verify that both options I was looking for ar indeed working. Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. It happened again just a few minutes ago. This all started happening after I brought this NFS mount on-line as storage for the mythbackend server. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really this disk/PC/network connection. Thanks again for your help. Cheers, Mark -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
Well if you are a perl or python kinda guy you could write a more sophisticated script to copy the files and update the database so that everything is transparent as far as myth is concerned. -MikeOn 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: Mike, Thanks for the idea. I like the idea of being able to recordlocally for 15 hours safely and then just using the new NFS storagefor playback only, but I think it won't work from a practicalstandpoint: 1) MythTV runs in conjunction with MySQL which is managing the datafiles. If I simply move the data files to some other location thenMySQL won't know where they are for playback.2) As far as I know MythTV expects all the data file to be in a single location for playback. I've never heard of anyone having multipledisks for playback, but if they could then your idea would possiblywork. I like the idea though and will do some research to see if there's a practical solution. Possibly some sort of logical disk drive? That'sa bit beyond my meager skill set.Thanks,MarkOn 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: Mark,Here is my suggestion to get the best of both worlds (note my limited knowledge of mythtv). Setup a shell script to copy all your video files from the myth capture directory over to the nfs share and delete the files thus clearing your local space and also allowing you to capture 135 hours. You could even cron it so you don't have to think about it. Pardon me if this is a gross misunderstanding of mythtv but if its not it should work like a charm.-Mike On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks,Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show that I'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems to verify that both options I was looking for ar indeed working. Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. It happened again just a few minutes ago. This all started happening after I brought this NFS mount on-line as storage for the mythbackend server. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really this disk/PC/network connection. Thanks again for your help. Cheers, Mark -- gentoo-user@gentoo.org mailing list -- Michael E. Crute Software Developer SoftGroup Development Corporation In a world without walls and fences, who needs windows and gates? --gentoo-user@gentoo.org mailing list-- Michael E. CruteSoftware Developer SoftGroup Development CorporationIn a world without walls and fences, who needs windows and gates?
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
I'm not any kind of programmer. Guitar player actually. I just need stuff to work or I'm helpless! Thanks, Mark On 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: Well if you are a perl or python kinda guy you could write a more sophisticated script to copy the files and update the database so that everything is transparent as far as myth is concerned. -Mike On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: Mike, Thanks for the idea. I like the idea of being able to record locally for 15 hours safely and then just using the new NFS storage for playback only, but I think it won't work from a practical standpoint: 1) MythTV runs in conjunction with MySQL which is managing the data files. If I simply move the data files to some other location then MySQL won't know where they are for playback. 2) As far as I know MythTV expects all the data file to be in a single location for playback. I've never heard of anyone having multiple disks for playback, but if they could then your idea would possibly work. I like the idea though and will do some research to see if there's a practical solution. Possibly some sort of logical disk drive? That's a bit beyond my meager skill set. Thanks, Mark On 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: Mark, Here is my suggestion to get the best of both worlds (note my limited knowledge of mythtv). Setup a shell script to copy all your video files from the myth capture directory over to the nfs share and delete the files thus clearing your local space and also allowing you to capture 135 hours. You could even cron it so you don't have to think about it. Pardon me if this is a gross misunderstanding of mythtv but if its not it should work like a charm. -Mike On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show that I'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems to verify that both options I was looking for ar indeed working. Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. It happened again just a few minutes ago. This all started happening after I brought this NFS mount on-line as storage for the mythbackend server. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really this disk/PC/network connection. Thanks again for your help. Cheers, Mark -- gentoo-user@gentoo.org mailing list -- Michael E. Crute Software Developer SoftGroup Development Corporation In a world without walls and fences, who needs windows and gates? -- gentoo-user@gentoo.org mailing list -- Michael E. Crute Software Developer SoftGroup Development Corporation In a world without walls and fences, who needs windows and gates? -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
I think it is much more easy to get NFS working right... ;) Just my 2 cents. On Tue, 2 Aug 2005, Michael Crute wrote: Well if you are a perl or python kinda guy you could write a more sophisticated script to copy the files and update the database so that everything is transparent as far as myth is concerned. -Mike On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: Mike, Thanks for the idea. I like the idea of being able to record locally for 15 hours safely and then just using the new NFS storage for playback only, but I think it won't work from a practical standpoint: 1) MythTV runs in conjunction with MySQL which is managing the data files. If I simply move the data files to some other location then MySQL won't know where they are for playback. 2) As far as I know MythTV expects all the data file to be in a single location for playback. I've never heard of anyone having multiple disks for playback, but if they could then your idea would possibly work. I like the idea though and will do some research to see if there's a practical solution. Possibly some sort of logical disk drive? That's a bit beyond my meager skill set. Thanks, Mark On 8/2/05, Michael Crute [EMAIL PROTECTED] wrote: Mark, Here is my suggestion to get the best of both worlds (note my limited knowledge of mythtv). Setup a shell script to copy all your video files from the myth capture directory over to the nfs share and delete the files thus clearing your local space and also allowing you to capture 135 hours. You could even cron it so you don't have to think about it. Pardon me if this is a gross misunderstanding of mythtv but if its not it should work like a charm. -Mike On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: On 8/2/05, Matthew Cline [EMAIL PROTECTED] wrote: On 8/2/05, Mark Knecht [EMAIL PROTECTED] wrote: but how do I know it's being used? And how do I know that the rsize option is being used? Thanks, Mark Could you watch the traffic between the two using something like ethereal? This should tell you which protocol is being used. Hi Matt, OK, ethereal was pretty easy to use, and it does indeed show that I'm using TCP for packat transfer. I see a proto=NFS packet followed by a number of TCP packets with sizes of 8K bytes so this seems to verify that both options I was looking for ar indeed working. Thanks! Unfortunately this means I'm no closer to the root cause of my real problem which is mythbackend shutting down without warning. It happened again just a few minutes ago. This all started happening after I brought this NFS mount on-line as storage for the mythbackend server. I suppose I'll have to go back to the reduced storage option (15 hours instead of 120 hours) and make sure that it's really this disk/PC/network connection. Thanks again for your help. Cheers, Mark -- gentoo-user@gentoo.org mailing list -- Michael E. Crute Software Developer SoftGroup Development Corporation In a world without walls and fences, who needs windows and gates? -- gentoo-user@gentoo.org mailing list -- Bryan Whitehead Email:[EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] NFS configuration (tcp/ip MythTV)
On 8/2/05, Bryan Whitehead [EMAIL PROTECTED] wrote: BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the 4gb filesize limit. OK, I've built the kernels on both machines and have support for both V3 and V3 clients and servers built in. Ethereal tells me now that I'm using V3. We'll see if that stays on line longer than the V2 protocol did. thanks! - Mark -- gentoo-user@gentoo.org mailing list
