From: Yusuf Goolamabbas <yusufg-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org>
To: nfs@lists.sourceforge.net
Subject: [NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19
Date: Sun, 19 Oct 2008 11:28:11 +0800 [thread overview]
Message-ID: <20081019032811.GA30801@outblaze.com> (raw)
Anybody know if this is bug is fixed and if so in which kernel revision.
Any ideas about its impact on vendor kernels (RHEL/SUSE Enterprise)
http://opensrs.com/blog/2008/10/technical-debrief-on-october-cluster-a-email-service-issue/
Regards, Yusuf
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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 reply other threads:[~2008-10-19 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 3:28 Yusuf Goolamabbas [this message]
[not found] ` <20081019032811.GA30801-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org>
2008-10-19 10:44 ` [NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19 Jeff Layton
[not found] ` <20081019064405.0db1e004-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-10-19 16:45 ` Trond Myklebust
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=20081019032811.GA30801@outblaze.com \
--to=yusufg-la0cmj9g6+fwk0htik3j/w@public.gmane.org \
--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