Linux NFS development
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: NeilBrown <neilb@suse.de>,
	nfs@lists.sourceforge.net, Greg Banks <gnb@sgi.com>
Subject: Re: [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch
Date: Sat, 13 Oct 2007 07:35:21 -0500	[thread overview]
Message-ID: <C33625B9.3C913%tom@opengridcomputing.com> (raw)
In-Reply-To: <20071013034842.GA13453@fieldses.org>


On 10/12/07 10:48 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:

> On Fri, Oct 12, 2007 at 06:30:00PM -0400, bfields wrote:
>> On Fri, Oct 12, 2007 at 06:03:00PM -0400, bfields wrote:
>>> Sorry, yes, it's currently in "master" in my git tree:
>>> 
>>> git://linux-nfs.org/~bfields/linux.git master
>>> 
>>> I believe it's got everything you've sent me so far except the three
>>> patches from today.  I haven't looked at it again since yesterday.
>> 
>> Bah, don't spend any time on this.  I took another look, and it seems
>> the problem is in the exported filesystem itself, not in the server.
> 
> Yeah, there were some filesystem errors in the logs, and after
> reformatting that partition I can't reproduce the problem.  I think that
> one machine may just have an unreliable drive.
>

No worries, I found three other bugs in the process :-)

Tom 
> --b.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-10-13 12:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  2:23 [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch Tom Tucker
2007-10-11  2:28 ` [RFC, PATCH 1/3] svc: Change sockaddr to sockaddr_storage in svc_create_xprt Tom Tucker
2007-10-11  2:28 ` [RFC,PATCH 2/3] svc: Fix bugs in svc_find_xprt Tom Tucker
2007-10-11  2:29 ` [RFC, PATCH 3/3] knfsd: Modify write_ports to use svc_find_xprt service Tom Tucker
2007-10-11  3:00   ` Neil Brown
2007-10-11  3:46     ` J. Bruce Fields
2007-10-11  5:09       ` Neil Brown
2007-10-11  5:26         ` Greg Banks
2007-10-11  5:37           ` Neil Brown
2007-10-11 14:56         ` J. Bruce Fields
2007-10-11  5:11       ` Tom Tucker
2007-10-11 15:25         ` J. Bruce Fields
2007-10-11 15:27           ` Tom Tucker
2007-10-11 17:04             ` J. Bruce Fields
2007-10-11  5:25 ` [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch Greg Banks
2007-10-11 17:09   ` J. Bruce Fields
2007-10-11 20:30 ` J. Bruce Fields
2007-10-11 20:53   ` Tom Tucker
2007-10-11 21:14   ` Tom Tucker
2007-10-11 22:04   ` Tom Tucker
2007-10-11 22:08     ` J. Bruce Fields
2007-10-12 15:17       ` Tom Tucker
2007-10-12 15:41         ` J. Bruce Fields
2007-10-12 16:27           ` Tom Tucker
2007-10-12 21:40   ` Tom Tucker
2007-10-12 22:03     ` J. Bruce Fields
2007-10-12 22:30       ` J. Bruce Fields
2007-10-13  3:48         ` J. Bruce Fields
2007-10-13 12:35           ` Tom Tucker [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=C33625B9.3C913%tom@opengridcomputing.com \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=gnb@sgi.com \
    --cc=neilb@suse.de \
    --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