lkml.org 
[lkml]   [2005]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: NFS oops on 2.6.14.2
From
On Tue, Nov 29, 2005 at 04:26:37PM -0500, Trond Myklebust wrote:
> Both presumably following a server reboot?
>
> Do you have any sure-fire way to reproduce it?

Correct. The server crashed and rebooted this morning but I didn't see
anything like this (these happened a few days ago after another
mysterious server reboot). I'll be rebooting the server again tonight,
so we'll see. So no, I don't yet have a sure-fire way to reproduce.

> > These machines have an NFS-mounted root, but this is mounted nolock so I'm
> > assuming that's unrelated. The other NFS mounts have options like:
> >
> > rw,nosuid,nodev,v3,rsize=8192,wsize=8192,hard,intr,udp,lock
> >
> > I've also been seeing lots of the "do_vfs_lock: VFS is out of sync with lock
> > manager!", but that has been happening at least since 2.6.13.
>
> That is usually the result of doing kill -9/kill -TERM/kill -INT on a
> process that was in the act of grabbing a lock.

OK, well it doesn't seem to cause any problems so I guess I'll ignore
it. Just wanted to mention it since it sounds kind of ominous.

Thanks,
-ryan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-11-29 22:57    [W:0.033 / U:0.644 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site