diff options
| author | kshithijiyer <kshithij.ki@gmail.com> | 2019-09-02 18:43:36 +0530 |
|---|---|---|
| committer | Amar Tumballi <amarts@gmail.com> | 2019-09-05 04:55:30 +0000 |
| commit | b0dbe11556c17ba6ea0b7d85b741bd4807c81c9c (patch) | |
| tree | 35b58d0fc52d28bb24f1215509a7a8fa485546c2 /doc/debugging | |
| parent | 724c657995a2e148243eeb78c68b620c6d7714a5 (diff) | |
[Doc] Fixing 404 links in markdown files.
Problem:
While running markdown-link-checker it was
observed that there were a large number of
404 links present in the documentation present
in the form of markdown files in the project.
This was casued due to the following reasons:
1. Repos being removed.
2. Typo in markdown links.
3. Restructring of directoires.
Solution:
Fixing all the 404 links present in the project.
fixes: bz#1746810
Change-Id: I30de745f848fca2e9c92eb7493f74738f0890ed9
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
Diffstat (limited to 'doc/debugging')
| -rw-r--r-- | doc/debugging/gfid-to-path.md | 4 | ||||
| -rw-r--r-- | doc/debugging/statedump.md | 2 |
2 files changed, 1 insertions, 5 deletions
diff --git a/doc/debugging/gfid-to-path.md b/doc/debugging/gfid-to-path.md index 49e9aa09a3f..1917bf2cca1 100644 --- a/doc/debugging/gfid-to-path.md +++ b/doc/debugging/gfid-to-path.md @@ -64,9 +64,5 @@ 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) diff --git a/doc/debugging/statedump.md b/doc/debugging/statedump.md index 9d594320ddc..9dfdce15fad 100644 --- a/doc/debugging/statedump.md +++ b/doc/debugging/statedump.md @@ -328,7 +328,7 @@ cur-stdalloc=214 max-stdalloc=220 ``` -Here, with cold count being 0 by default, `cur-stdalloc` indicated the number of `dict_t` objects that were allocated in heap using `mem_get()`, and yet to be freed using `mem_put()` (refer to this [page](https://github.com/gluster/glusterfs/blob/master/doc/data-structures/mem-pool.md) for more details on how mempool works). After the test case (name selfheal of 100 files), there was a rise in the cur-stdalloc value (from 14 to 214) for `dict_t`. +Here, with cold count being 0 by default, `cur-stdalloc` indicated the number of `dict_t` objects that were allocated in heap using `mem_get()`, and yet to be freed using `mem_put()` (refer to this [page](../developer-guide/datastructure-mem-pool.md) for more details on how mempool works). After the test case (name selfheal of 100 files), there was a rise in the cur-stdalloc value (from 14 to 214) for `dict_t`. After these leaks were fixed, glusterfs was again compiled with -DDEBUG flags, and the same steps were performed again and statedump was taken before and after executing the test case, of the mount. This was done to ascertain the validity of the fix. And the following are the results: |