From c66509ca9d8a0aeba47ac5a892b269ccb280f4f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pavel=20Jir=C3=A1sek?= <pavel.jirasek@vsb.cz>
Date: Mon, 23 Jan 2017 12:38:45 +0100
Subject: [PATCH] Link managingstripingfreespace

---
 docs.it4i/anselm-cluster-documentation/storage.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs.it4i/anselm-cluster-documentation/storage.md b/docs.it4i/anselm-cluster-documentation/storage.md
index 92b31ff2a..d67279a8a 100644
--- a/docs.it4i/anselm-cluster-documentation/storage.md
+++ b/docs.it4i/anselm-cluster-documentation/storage.md
@@ -75,7 +75,7 @@ Another good practice is to make the stripe count be an integral factor of the n
 
 Large stripe size allows each client to have exclusive access to its own part of a file. However, it can be counterproductive in some cases if it does not match your I/O pattern. The choice of stripe size has no effect on a single-stripe file.
 
-Read more on <http://wiki.lustre.org/manual/LustreManual20_HTML/ManagingStripingFreeSpace.html>
+Read more on <http://doc.lustre.org/lustre_manual.xhtml#managingstripingfreespace>
 
 ### Lustre on Anselm
 
-- 
GitLab