All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: "William A. (Andy) Adamson" <androsadamson@gmail.com>
Cc: Benny Halevy <bhalevy@panasas.com>, NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Am I still the one to fix the NFS_FILE_SYNC problem
Date: Mon, 24 May 2010 18:39:09 +0300	[thread overview]
Message-ID: <4BFA9D9D.2030908@panasas.com> (raw)
In-Reply-To: <AANLkTilR7cJu1uCv60GrpFimqDWb0ogyvKVh1q0iW_6a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 05/24/2010 04:14 PM, William A. (Andy) Adamson wrote:
> Hi Boaz
> 
> The last patch I sent in [PATCH 1/1] SQUASHME pnfs-submit: replace
> layoutcommit_ctx with rpc_cred fixes the NFS_FILE_SYNC problem for
> files. It replaces taking a reference on the open context with taking
> a reference on the rpc_cred.
> 

Hi Andy.

I hope you are online could you chat with me a bit about this, 
on boazharrosh-Re5JQEeQqe9fmgfxC/sS/w@public.gmane.org

I have seen your patch and i like it a lot. I have not yet test with
it, so I own you.

I'm talking about the other problem I had where the write-out returns
NFS_FILE_SYNC and commit is not called and pnfs_client_ops->nfs_commit_complete()
is not eventually called, then inode never gets written/updated and we get all
these straining .nfs000000000000XXX files and IO never finishes. You said
you had them too and I had a work around for objects. (This problem is new
in 2.6.34)

Do you have this problem or it's only me?

Boaz

> -->Andy
> 				
> 
> On Sun, May 23, 2010 at 2:36 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
>>
>> Andy, Benny are you waiting on me to fix the NFS_FILE_SYNC problem?
>>
>> I've been on a long holiday, but I can attempt a fix tomorrow if still
>> needed?
>>
>> I was hoping someone else need that more urgently then me, since I already
>> have a work around, for my testing ;-)
>>
>> Boaz
>>
>> --
>> 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
>>


  parent reply	other threads:[~2010-05-24 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-23 18:36 Am I still the one to fix the NFS_FILE_SYNC problem Boaz Harrosh
2010-05-24 13:14 ` William A. (Andy) Adamson
     [not found]   ` <AANLkTilR7cJu1uCv60GrpFimqDWb0ogyvKVh1q0iW_6a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-24 15:39     ` Boaz Harrosh [this message]
2010-05-24 16:10       ` Tao Guo
2010-05-24 16:47       ` William A. (Andy) Adamson

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=4BFA9D9D.2030908@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=androsadamson@gmail.com \
    --cc=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.