[gentoo-user] NFS configuration (tcp/ip & MythTV)

[gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

Hi,
   I have set up a large NFS mount for use as remote storage for our
MythTV server. It works, but since setting it up the mythbackend
program has twice shut down in the middle of the night. Prior to
setting up this storage mythbackend had never, to the best of my
knowledge, ever shut down unexpectantly. Obviously I'm suspicious that
this change is the root cause.

   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.

   Any comments on whether this is likely to yield better results and
how I might look at going about it? Pointers to the right Gentoo docs
much appreciated.

Thanks,
Mark

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]

When you emerge nfs use the tcpd use flag to get TCP support.

-Mike

On 8/2/05, Mark Knecht <markknecht@gmail.com> wrote:
> 
> Hi,
> I have set up a large NFS mount for use as remote storage for our
> MythTV server. It works, but since setting it up the mythbackend
> program has twice shut down in the middle of the night. Prior to
> setting up this storage mythbackend had never, to the best of my
> knowledge, ever shut down unexpectantly. Obviously I'm suspicious that
> this change is the root cause.
> 
> 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.
> 
> Any comments on whether this is likely to yield better results and
> how I might look at going about it? Pointers to the right Gentoo docs
> much appreciated.
> 
> Thanks,
> 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?"

[-- Attachment #2: Type: text/html, Size: 1571 bytes --]

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Matthew Cline]

> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Richard Fish]

Matthew Cline wrote:

>>On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Mark Knecht]

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 <bigfish@asmallpond.org> wrote:
> Matthew Cline wrote:
> 
> >>On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Uwe Thiem]

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)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

I would use 'sudo netstat -lp | grep nfs' to see what nfs is listening on.

-Mike

On 8/2/05, Mark Knecht <markknecht@gmail.com> 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 <bigfish@asmallpond.org> wrote:
> > Matthew Cline wrote:
> >
> > >>On 8/2/05, Mark Knecht <markknecht@gmail.com> 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. Crute
Software Developer
SoftGroup Development Corporation

"In a world without walls and fences, who needs windows and gates?"

[-- Attachment #2: Type: text/html, Size: 2133 bytes --]

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

On 8/2/05, Michael Crute <mcrute@gmail.com> 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)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

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

On 8/2/05, Mark Knecht <markknecht@gmail.com> wrote:
> 
> On 8/2/05, Michael Crute <mcrute@gmail.com> 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
> 
> 


-- 
________________________________
Michael E. Crute
Software Developer
SoftGroup Development Corporation

"In a world without walls and fences, who needs windows and gates?"

[-- Attachment #2: Type: text/html, Size: 1442 bytes --]

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

On 8/2/05, Michael Crute <mcrute@gmail.com> 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
tcp        0      0 *:nfs                   *:*                     LISTEN -
udp        0      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)

[Matthew Cline]

On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Mark Knecht]

On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Mark Knecht]

On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

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 <markknecht@gmail.com> wrote:
> 
> On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
> > On 8/2/05, Mark Knecht <markknecht@gmail.com> 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?"

[-- Attachment #2: Type: text/html, Size: 2602 bytes --]

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Bryan Whitehead]

The best way is to ask the portmapper (example below):

[driver@mulan ~]$ rpcinfo -p
    program vers proto   port
     100000    2   tcp    111  portmapper
     100000    2   udp    111  portmapper
     100024    1   udp    921  status
     100024    1   tcp    928  status
     100007    2   udp   1000  ypbind
     100007    1   udp   1000  ypbind
     100007    2   tcp   1003  ypbind
     100007    1   tcp   1003  ypbind
     100011    1   udp    647  rquotad
     100011    2   udp    647  rquotad
     100011    1   tcp    669  rquotad
     100011    2   tcp    669  rquotad
     100003    2   udp   2049  nfs
     100003    3   udp   2049  nfs
     100003    4   udp   2049  nfs
     100003    2   tcp   2049  nfs
     100003    3   tcp   2049  nfs
     100003    4   tcp   2049  nfs
     100021    1   udp  32768  nlockmgr
     100021    3   udp  32768  nlockmgr
     100021    4   udp  32768  nlockmgr
     100021    1   tcp  32768  nlockmgr
     100021    3   tcp  32768  nlockmgr
     100021    4   tcp  32768  nlockmgr
     100005    1   udp    165  mountd
     100005    1   tcp    165  mountd
     100005    2   udp    165  mountd
     100005    2   tcp    165  mountd
     100005    3   udp    165  mountd
     100005    3   tcp    165  mountd
[driver@mulan ~]$

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 <bigfish@asmallpond.org> wrote:
>> Matthew Cline wrote:
>>
>>>> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Bryan Whitehead]

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 <bigfish@asmallpond.org> wrote:
>> Matthew Cline wrote:
>>
>>>> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

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 <mcrute@gmail.com> 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 <markknecht@gmail.com> wrote:
> > 
> > On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
> > > On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Bryan Whitehead]

What filesystem are you exporting over NFS?

On Tue, 2 Aug 2005, Mark Knecht wrote:

> On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
>> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Bryan Whitehead]

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 <matthew.cline@gmail.com> wrote:
>> >  On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 3698 bytes --]

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 <markknecht@gmail.com> 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 <mcrute@gmail.com> 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 <markknecht@gmail.com> wrote:
> > >
> > > On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
> > > > On 8/2/05, Mark Knecht <markknecht@gmail.com> 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?"

[-- Attachment #2: Type: text/html, Size: 4810 bytes --]

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Bryan Whitehead]

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 <markknecht@gmail.com> 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 <mcrute@gmail.com> 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 <markknecht@gmail.com> wrote:
>>>>
>>>> On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
>>>>> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

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 <mcrute@gmail.com> 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 <markknecht@gmail.com> 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 <mcrute@gmail.com > 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 <markknecht@gmail.com> wrote:
> > > >
> > > > On 8/2/05, Matthew Cline < matthew.cline@gmail.com> wrote:
> > > > > On 8/2/05, Mark Knecht <markknecht@gmail.com> 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)

[Mark Knecht]

Bryan,
   OK, according to ethereal I'm only getting NFS V2 across the bus.
Here's the way my two machines are set up:

The new 250GB storage machine - 2.6.12-gentoo-r6

<*> NFS file system support
 [ ]   Provide NFSv3 client support
 [ ]   Provide NFSv4 client support (EXPERIMENTAL)
 [ ]   Allow direct I/O on NFS files (EXPERIMENTAL)
 <*> NFS server support
 [*]   Provide NFSv3 server support
 [ ]     Provide NFSv4 server support (EXPERIMENTAL)
 [*]   Provide NFS server over TCP support 

The mythbackend machine which is the NFS client:

<*> NFS file system support
 [*]   Provide NFSv3 client support
 [ ]   Provide NFSv4 client support (EXPERIMENTAL)
 [ ]   Allow direct I/O on NFS files (EXPERIMENTAL)
 <M> NFS server support
 [*]   Provide NFSv3 server support
 [ ]     Provide NFSv4 server support (EXPERIMENTAL)
 [*]   Provide NFS server over TCP support 

I guess V2 support makes sense as that kernel only has V2 compiled in.
Shall I jump to V3 or V4?

thanks,
Mark

On 8/2/05, Bryan Whitehead <driver@megahappy.net> wrote:
> 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 <matthew.cline@gmail.com> wrote:
> >> >  On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
> --
> gentoo-user@gentoo.org mailing list
> 
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

Hope so! Thanks.

On 8/2/05, Bryan Whitehead <driver@megahappy.net> wrote:
> 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 <markknecht@gmail.com> 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 <mcrute@gmail.com> 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 <markknecht@gmail.com> wrote:
> >>>>
> >>>> On 8/2/05, Matthew Cline <matthew.cline@gmail.com> wrote:
> >>>>> On 8/2/05, Mark Knecht <markknecht@gmail.com> 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:driver@megahappy.net
> --
> gentoo-user@gentoo.org mailing list
> 
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

On 8/2/05, Bryan Whitehead <driver@megahappy.net> 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

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Bryan Whitehead]

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 <driver@megahappy.net> 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:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Mark Knecht]

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 <driver@megahappy.net> 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 <driver@megahappy.net> 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:driver@megahappy.net
> --
> gentoo-user@gentoo.org mailing list
> 
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

Quick... knock on wood!

On 8/8/05, Mark Knecht <markknecht@gmail.com> wrote:
> 
> 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 <driver@megahappy.net> 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 <driver@megahappy.net> 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:driver@megahappy.net
> > --
> > gentoo-user@gentoo.org mailing list
> >
> >
> 
> --
> 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?"

[-- Attachment #2: Type: text/html, Size: 2293 bytes --]

Re: [gentoo-user] NFS configuration (tcp/ip & MythTV)

[Michael Crute]

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

Oh oops... sorry... thats the way Windoze works (or rather doesn't work). 

Glad everything finally worked out for you.

-Mike

On 8/9/05, Michael Crute <mcrute@gmail.com> wrote:
> 
> Quick... knock on wood!
> 
> On 8/8/05, Mark Knecht <markknecht@gmail.com> wrote:
> > 
> > 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 <driver@megahappy.net> 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 <driver@megahappy.net> 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:driver@megahappy.net
> > > --
> > > gentoo-user@gentoo.org mailing list
> > >
> > >
> > 
> > --
> > 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?" 
> 



-- 
________________________________
Michael E. Crute
Software Developer
SoftGroup Development Corporation

"In a world without walls and fences, who needs windows and gates?"

[-- Attachment #2: Type: text/html, Size: 3548 bytes --]