test : removing quota-anon-fd-nfs.t for time being.

I am removing quota-anon-fd-nfs.t for time being as it is causing
lots of regression failure. Meanwhile I will be working in parallel
to find out the root cause for this spurious failure in another patch
(http://review.gluster.org/#/c/9381/). I'll revert this patch once a proper fix is found.

Change-Id: I0ef205241219ed3210d58d2b487f1b00292115f0
BUG: 1163543
Signed-off-by: Sachin Pandit <spandit@redhat.com>
Reviewed-on: http://review.gluster.org/9390
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
Tested-by: Raghavendra G <rgowdapp@redhat.com>

1 files changed, 0 insertions, 86 deletions

diff --git a/tests/basic/quota-anon-fd-nfs.t b/tests/basic/quota-anon-fd-nfs.t
deleted file mode 100755
index 5841580f9a8..00000000000
--- a/tests/basic/quota-anon-fd-nfs.t
+++ /dev/null
@@ -1,86 +0,0 @@
-#!/bin/bash
-
-. $(dirname $0)/../include.rc
-. $(dirname $0)/../fileio.rc
-
-cleanup;
-
-TESTS_EXPECTED_IN_LOOP=16
-TEST glusterd
-TEST pidof glusterd
-TEST $CLI volume info;
-
-TEST $CLI volume create $V0 $H0:$B0/brick1;
-EXPECT 'Created' volinfo_field $V0 'Status';
-
-
-# The test makes use of inode-lru-limit to hit a scenario, where we
-# find an inode whose ancestry is not there. Following is the
-# hypothesis (which is confirmed by seeing logs indicating that
-# codepath has been executed, but not through a good understanding of
-# NFS internals).
-
-#     At the end of an fop, the reference count of an inode would be
-#     zero. The inode (and its ancestry) persists in memory only
-#     because of non-zero lookup count. These looked up inodes are put
-#     in an lru queue of size 1 (here). So, there can be at most one
-#     such inode in memory.
-
-#     NFS Server makes use of anonymous fds. So, if it cannot find
-#     valid fd, it does a nameless lookup. This gives us an inode
-#     whose ancestry is NULL. When a write happens on this inode,
-#     quota-enforcer/marker finds a NULL ancestry and asks
-#     storage/posix to build it.
-
-TEST $CLI volume set $V0 network.inode-lru-limit 1
-TEST $CLI volume set $V0 performance.nfs.write-behind off
-
-TEST $CLI volume start $V0;
-EXPECT 'Started' volinfo_field $V0 'Status';
-
-TEST $CLI volume quota $V0 enable
-TEST $CLI volume quota $V0 limit-usage / 1
-TEST $CLI volume quota $V0 soft-timeout 0
-TEST $CLI volume quota $V0 hard-timeout 0
-
-TEST mount -t nfs -o noac,soft,nolock,vers=3 $H0:/$V0 $N0
-deep=/0/1/2/3/4/5/6/7/8/9
-TEST mkdir -p $N0/$deep
-
-TEST touch $N0/$deep/file1 $N0/$deep/file2 $N0/$deep/file3 $N0/$deep/file4
-
-TEST fd_open 3 'w' "$N0/$deep/file1"
-TEST fd_open 4 'w' "$N0/$deep/file2"
-TEST fd_open 5 'w' "$N0/$deep/file3"
-TEST fd_open 6 'w' "$N0/$deep/file4"
-
-# consume all quota
-TEST ! dd if=/dev/zero of="$N0/$deep/file" bs=1MB count=1
-
-# At the end of each fop in server, reference count of the
-# inode associated with each of the file above drops to zero and hence
-# put into lru queue. Since lru-limit is set to 1, an fop next file
-# will displace the current inode from itable. This will ensure that
-# when writes happens on same fd, fd resolution results in
-# nameless lookup from server and quota_writev encounters an fd
-# associated with an inode whose parent is not present in itable.
-
-for j in $(seq 1 2); do
-    for i in $(seq 3 6); do
-        # failing writes indicate that we are enforcing quota set on /
-        # even with anonymous fds.
-        TEST_IN_LOOP ! fd_write $i "content"
-        TEST_IN_LOOP sync
-    done
-done
-
-exec 3>&-
-exec 4>&-
-exec 5>&-
-exec 6>&-
-
-$CLI volume statedump $V0 all
-
-TEST umount -l $N0
-
-cleanup;