[mythtv-users] Incomming WAF Problem: NFS "Crashing" on Jaunty
douglasw0 at gmail.com
Fri Jun 5 18:55:22 UTC 2009
On Fri, Jun 5, 2009 at 1:48 PM, Brian Wood <beww at beww.org> wrote:
> On Friday 05 June 2009 12:29:25 Douglas Wagner wrote:
> > Ok, so I've got 3 days to figure this one out before my WAF goes to the
> > tubes.
> > Been using Myth for a few years now. A year or two ago I came across
> > mythbuntu and was pretty impressed so I installed 8.04. Last week, due
> > wanting some better tools, and a successful upgrade of my ubuntu desktop
> > work, I decided to upgrade to mythbuntu 9.04 Jaunty.
> > Did a double network upgrade (8.04 -> 8.10 -> 9.04). The upgrade got
> > up in the 8.10 ->9.04 side with some symbolic links to NFS shares and
> > didn't install correctly. Removing and adding a few packages (basically
> > readd of the mythbuntu consolidated package) fixed the issue and has the
> > machine up and running.
> > Now, however, i'm facing a rather large issue. I have all of my video
> > shares (other than a small 250GB drive in the Myth Box that gets the
> > initial recording) on NFS Shares shared from my NAS Box. At this
> > seems that periodically (at MOST every 24 hours but I'm guessing it's
> > taking a few hours) my Myth box looses NFS connectivity, to the point
> > it cannot see any of my NFS shares anymore. At this point the
> > goes into a "hung up" state when attempting to access the recording or
> > video section (the stuff on the nas is symbolic linked through NFS to
> > like files on the local system. Yes, I know this is so Myth 0.19 and
> > there's other ways to do this now).
> > The root cause seems to be myth being unable to read from NFS. I can
> > unmount but not remount the NFS shares. Restarting NFS-COMMON doesn't
> > to help.
> > I CANNOT have this box having to be rebooted every few hours to make it
> > useful. Anyone have any ideas what the heck is going on? Rebooting the
> > myth box brings the NFS shares back with no problems at all. Last night
> > restarted the NAS box and did a remount of everything and all was in good
> > shape...so it seems I can "fix" it from either end.
> > I can tell it's not the NAS system, because I have some of the same
> > mounted on other boxes and no other box other than the Myth box has
> > with the shares (i.e. When the myth box can't access them the rest of the
> > boxes can.)
> > All of the exports on the NAS use the same export type (pretty basic):
> > /mnt/video3 192.168.100.0/24(rw,async)<http://192.168.100.0/24%28rw,async%29>
> > And are being mounted as follows:
> > nas:/mnt/video3 /mnt/video3 nfs
> > intr,rsize=8192,wsize=8192,async,nfsvers=3,bg,actimeo=0,tcp
> > HELP? Any ideas? Would dropping a mythbuntu 9.04 DVD in the drive and
> > doing an "upgrade" (is this possible without blowing away settings?) to
> > replace all the system packages with what they should be help? Can I do
> > non-destructive "something's broken, fix it" installation? Any
> > packages I can remove-reinstall to see about fixing this?
> > Is there a better way to mount these shares or is there a known bug with
> > NFS?
> A quick google shows a lot of folks having similar problems (not
> with Myth). Some seem to think it's a problem with the 2.6.28 kernel Ubuntu
> 9.04 is using.
> You might try an SMB/CIFS mount, or even upgrading to 2.6.29.
> Gossamer shows a lot of NFS problems, but I didn't read enough of them to
> determine if they are all with 9.04.
> I'm curious what "better tools" would have motivated you to upgrade a
> beww at beww.org
> mythtv-users mailing list
> mythtv-users at mythtv.org
Mythexport 2.0 mostly. That and the fact that I was seeing some writing on
the wall that many of the new tools weren't being "backported" to 8.04, only
to 8.10. I chose the LTS exactly for the reason you're mentioning, once it
works it works for a long while, but with some of the transcoding issues
I've had along with the fact that there was some talk about mythexport
supporting more than one export feed (I have 4 people with 4 ipods in the
house that want 4 different things on their systems) along with the fact
that I am a NOTORIOUS ITABFI (If it ain't broke, fix it), along with the
fact I get two weeks a year to do any upgrades on the myth system (when my
wife and kids are out of town), it all sort of combined to make this my week
Actually, I'm kinda glad to hear it's being blamed on the kernel, that means
when the kernel upgrades I can give it a try again and see if it works or
not. Till then, looks like I'll try to switch over to a CIFS mount and see
if that is more stable.
Thanks for the fast answer...and the virtual smack upside the back of the
head for upgrading a working system, I really SHOULD know better.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users