linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: <tigran.mkrtchyan@desy.de>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: blacklisted DS with pnfs
Date: Wed, 25 Jan 2012 14:46:24 +0200	[thread overview]
Message-ID: <4F1FF9A0.2000505@panasas.com> (raw)
In-Reply-To: <4F1FF91B.3010708@panasas.com>

On 01/25/2012 02:44 PM, Boaz Harrosh wrote:
> On 01/25/2012 11:56 AM, Tigran Mkrtchyan wrote:
>> Hi,
>>
>> we have observed that in some situations ( probably network glitches )
>> the pnfs client blacklisted one of the data servers:
>>
>> NFS: data server 83a95099 connection error -12. Deviceid [22000000000]
>> marked out of use.
>>
>> As a result, data server can't be used by this client anymore.
>>
>> Is there a way to let client to forget about data server?
>> Some magic in /proc ?
>>
>> This is SL6.2 (RHEL 6.2):
>> # uname -a
>> Linux p3-wgs13 2.6.32-220.2.1.el6.x86_64 #1 SMP Thu Dec 22 11:15:52
>> CST 2011 x86_64 x86_64 x86_64 GNU/Linux
>> #
>>
> 
> Look in the source code, I think there is a RECALL that the server
> can do to trash the all device cache. or one of the devices.
> 
> What happens is that the device is marked with error but is in 
> cache so is not re-fetched.
> 
> wait let me look ....
> 
> I found it! The server sends a NOTIFY_DEVICEID4_CHANGE. The
> client will remove the deviceid from cache and unmount if needed.
> Next layout with that deviceid will re-establish the connection and
> will put a new clean entry in the dev cache.
> 

If you want to see for your self look at:
 callback_proc.c::nfs4_callback_devicenotify()

Boaz
> [If you decide to enhance pynfs to send a NOTIFY_DEVICEID4_CHANGE as an admin
>  tool. That would be interesting]
> 
>> Regards,
>>    Tigran.
> 
> Cheers
> 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


  reply	other threads:[~2012-01-25 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25  9:56 blacklisted DS with pnfs Tigran Mkrtchyan
2012-01-25 12:44 ` Boaz Harrosh
2012-01-25 12:46   ` Boaz Harrosh [this message]
2012-01-25 13:17     ` Tigran Mkrtchyan
2012-01-25 13:29       ` Boaz Harrosh

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=4F1FF9A0.2000505@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.de \
    /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;
as well as URLs for NNTP newsgroup(s).