From 81850f806a2a61470806c8a8a1a03de65cabc06c Mon Sep 17 00:00:00 2001
From: Kshithij Iyer <kshithij.ki@gmail.com>
Date: Tue, 17 Sep 2019 10:34:22 +0530
Subject: [PATCH] Fixing 404 links in gfid-to-path.md

---
 docs/Troubleshooting/gfid-to-path.md | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/docs/Troubleshooting/gfid-to-path.md b/docs/Troubleshooting/gfid-to-path.md
index 5167353..de2bdba 100644
--- a/docs/Troubleshooting/gfid-to-path.md
+++ b/docs/Troubleshooting/gfid-to-path.md
@@ -5,7 +5,7 @@ file across the entire cluster. This is analogous to inode number in a
 normal filesystem. The GFID of a file is stored in its xattr named
 `trusted.gfid`.
 
-#### Special mount using [gfid-access translator][1]:
+#### Special mount using gfid-access translator:
 ~~~
 mount -t glusterfs -o aux-gfid-mount vm1:test /mnt/testvol
 ~~~
@@ -21,7 +21,7 @@ getfattr -n glusterfs.gfid.string /mnt/testvol/dir/file
 ### Get file path from GFID (Method 1):
 **(Lists hardlinks delimited by `:`, returns path as seen from mountpoint)**
 
-####Turn on build-pgfid option
+#### Turn on build-pgfid option
 ~~~
 gluster volume set test build-pgfid on
 ~~~
@@ -64,10 +64,6 @@ trusted.glusterfs.pathinfo="(<DISTRIBUTE:test-dht> <POSIX(/mnt/brick-test/b):vm1
 ~~~
 
 ---
-### Get file path from GFID (Method 3):
-https://gist.github.com/semiosis/4392640
-
 ---
 #### References and links:
 [posix: placeholders for GFID to path conversion](http://review.gluster.org/5951)
-[1]: https://github.com/gluster/glusterfs/blob/master/doc/features/gfid-access.md