Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 5 Feb 2015 10:44:45 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12772184.1423004853000.265134.1423133085262@Atlassian.JIRA>
In-Reply-To: <JIRA.12772184.1423004853000@Atlassian.JIRA>
References: <JIRA.12772184.1423004853000@Atlassian.JIRA>
 <JIRA.12772184.1423004853519@arcas>
Subject: [jira] [Commented] (HDFS-7733) NFS: readdir/readdirplus return null
 directory attribute on failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307026#comment-14307026 ] 

Hudson commented on HDFS-7733:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk #829 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/829/])
HDFS-7733. NFS: readdir/readdirplus return null directory attribute on failure. (Contributed by Arpit Agarwal) (arp: rev c6f20007ebda509b39a7e4098b99e9b43d73d5b2)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs-nfs/src/main/java/org/apache/hadoop/hdfs/nfs/nfs3/RpcProgramNfs3.java


> NFS: readdir/readdirplus return null directory attribute on failure
> -------------------------------------------------------------------
>
>                 Key: HDFS-7733
>                 URL: https://issues.apache.org/jira/browse/HDFS-7733
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: nfs
>    Affects Versions: 2.6.0
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>             Fix For: 2.6.1
>
>         Attachments: HDFS-7733.01.patch
>
>
> NFS readdir and readdirplus operations return a null directory attribute on some failure paths. This causes clients to get a 'Stale file handle' error which can only be fixed by unmounting and remounting the share.
> The issue can be reproduced by running 'ls' against a large directory which is being actively modified, triggering the 'cookie mismatch' failure path.
> {code}
>         } else {
>           LOG.error("cookieverf mismatch. request cookieverf: " + cookieVerf
>               + " dir cookieverf: " + dirStatus.getModificationTime());
>           return new READDIRPLUS3Response(Nfs3Status.NFS3ERR_BAD_COOKIE);
>         }
> {code}
> Thanks to [~brandonli] for catching the issue.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)