From: "J. Bruce Fields" <bfields@fieldses.org>
To: mike <mike503@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] Help! NFS broken
Date: Mon, 8 Dec 2008 18:38:11 -0500 [thread overview]
Message-ID: <20081208233811.GD24083@fieldses.org> (raw)
In-Reply-To: <bd9320b30812070648x652c8430uf567b9c80cda07a6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Sun, Dec 07, 2008 at 06:48:52AM -0800, mike wrote:
> I upgraded my Ubuntu Hardy server to Intrepid the night before last.
> When I woke up yesterday morning, my main server I use as my ssh
> gateway into the others was totally messed up.
>
> My server is FreeBSD. I haven't had to touch it since I set it up.
>
> My clients are 6 Ubuntu servers. All are identical in packages,
> configs (I diff'ed /etc), kernel versions, network setup, etc.
So the "server" in the first paragraph is an NFS client, and its NFS
server is the FreeBSD machine?
And what are the first symptoms? Any threads accessing the NFS
filesystem just hang? A sysrq-T trace on the client showing where
they're hanging might be helpful.
--b.
>
> Only *one* of the machines is suffering (and of course, one of the
> most important ones) - and it isn't even one of the busiest.
>
> I've tried downgrading the kernel on the box suffering the issue from
> 2.6.27-10 to 2.6.27-7, my next attempt will be picking a kernel .deb
> that was from the previous Ubuntu release...
>
> What is odd is that it works great after reboot and lasts for a couple
> hours, then stops working. I can umount -l /home and then try to
> remount it (see below) but it never gets anywhere and eventually dies
> with a generic message. I tried to strace -f it, and it gave me
> nothing to work with. The FreeBSD server doesn't give me anything in
> logs to go off of either. I can ping and ssh between the two no
> problem at this point still. It's just NFS that is odd. Also I did
> notice trying to restart services manually and try to debug them that
> portmap seemed to throw a kernel error in my logs once in a while. But
> I don't get a connection to portmap when I run the mount command, and
> I would assume if portmap is required for mounting NFS shares that it
> would need to contact it. That could totally be irrelevant though.
>
> Any help or insight or request for additional information is
> appreciated. On-list or off-list is fine. I will pay someone via
> Paypal who can help me resolve this quickly...
>
> [root@lvs01 ~]# mount -vvvv /home
> mount: fstab path: "/etc/fstab"
> mount: mtab path: "/etc/mtab"
> mount: lock path: "/etc/mtab~"
> mount: temp path: "/etc/mtab.tmp"
> mount: spec: "raid01:/home"
> mount: node: "/home"
> mount: types: "nfs"
> mount: opts: "rsize=8192,rsize=8192,tcp,rw,acregmin=30"
> mount: external mount: argv[0] = "/sbin/mount.nfs"
> mount: external mount: argv[1] = "raid01:/home"
> mount: external mount: argv[2] = "/home"
> mount: external mount: argv[3] = "-v"
> mount: external mount: argv[4] = "-o"
> mount: external mount: argv[5] = "rw,rsize=8192,rsize=8192,tcp,acregmin=30"
> mount.nfs: timeout set for Sun Dec 7 06:36:39 2008
> mount.nfs: text-based options:
> 'rsize=8192,rsize=8192,tcp,acregmin=30,addr=10.13.220.94'
> (just stalls here, normally a connection is near instant. eventually
> it will die with a generic error message. i can control-C to quit it
> too, so it's not frozen completely)
>
>
>
> thanks...
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you. Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
> _______________________________________________
> Please note that nfs@lists.sourceforge.net is being discontinued.
> Please subscribe to linux-nfs@vger.kernel.org instead.
> http://vger.kernel.org/vger-lists.html#linux-nfs
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-12-08 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 14:48 [NFS] Help! NFS broken mike
[not found] ` <bd9320b30812070648x652c8430uf567b9c80cda07a6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-08 23:38 ` J. Bruce Fields [this message]
2008-12-09 0:12 ` mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081208233811.GD24083@fieldses.org \
--to=bfields@fieldses.org \
--cc=mike503@gmail.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox