From: "Peter Lojkin" <ia6432@inbox.ru>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: "Bernhard Kaindl" <bk@suse.de>,
nfs@lists.sourceforge.net, "Chris Mason" <mason@suse.com>
Subject: Re: NFS oopses on smp servers
Date: Thu, 26 Dec 2002 17:31:36 +0300 [thread overview]
Message-ID: <E18RZ2u-000GF6-00@f17.mail.ru> (raw)
In-Reply-To: <shs8yypaojt.fsf@charged.uio.no>
Hello,
we were unable to trigger the oops with this patch so we start installing it on failing servers. none of the updated servers
failed with such oops (first server updated 8 days ago), so i
guess this patch solves the problem. big thanks to all involved
for quick help!
now we have another nfs related oopses. these oopses happend on
both updated and not updated servers, so this patch wasn't the
cause. see my next message to the list for full info...
-----Original Message-----
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Date: 16 Dec 2002 17:58:30 +0100
Subject: Re: [NFS] NFS oopses on smp servers
> >>>>> " " == Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>
> > Try the appended patch instead:
>
> Duh: typo...
>
> Cheers,
> Trond
[patch skipped]
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-12-26 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 14:58 NFS oopses on smp servers Peter Lojkin
2002-12-16 14:38 ` Bernhard Kaindl
2002-12-16 15:34 ` Trond Myklebust
2002-12-16 16:58 ` Trond Myklebust
2002-12-26 14:31 ` Peter Lojkin [this message]
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=E18RZ2u-000GF6-00@f17.mail.ru \
--to=ia6432@inbox.ru \
--cc=bk@suse.de \
--cc=mason@suse.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.