From dbb95cec268a43784d5aebe553e9dfa6f915e75c Mon Sep 17 00:00:00 2001 From: Linda Bebernes Date: Wed, 28 Aug 2013 12:15:20 -0700 Subject: [PATCH] LUDOC-61 bugfix: Added note to lfs setstripe about inactive OSTs. Added a note describing what happens if lfs setstripe specifies a start OST that is inactive or degraded. Signed-off-by: Linda Bebernes Change-Id: I068f0636acdadd22a6984d33f2c61c8b5d418473 Reviewed-on: http://review.whamcloud.com/7471 Tested-by: Hudson Reviewed-by: Richard Henwood Reviewed-by: Andreas Dilger --- ManagingStripingFreeSpace.xml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/ManagingStripingFreeSpace.xml b/ManagingStripingFreeSpace.xml index 066a83e..64c5b88 100644 --- a/ManagingStripingFreeSpace.xml +++ b/ManagingStripingFreeSpace.xml @@ -190,7 +190,15 @@ start_ost - The start OST is the first OST to which files are written. The default value for start_ost is -1, which allows the MDS to choose the starting index. This setting is strongly recommended, as it allows space and load balancing to be done by the MDS as needed. Otherwise, the file starts on the specified OST index. The numbering of the OSTs starts at 0. + The start OST is the first OST to which files are written. The default value for + start_ost is -1, which allows the MDS to choose the starting index. This + setting is strongly recommended, as it allows space and load balancing to be done by the MDS + as needed. If the value of start_ost is set to a value other than -1, the + file starts on the specified OST index. OST index numbering starts at 0. + + If the specified OST is inactive or in a degraded mode, the MDS will silently choose + another target. + If you pass a start_ost value of 0 and a stripe_count value of 1, all files are written to -- 1.8.3.1