From 85df40f40d556bc54b4d0af0de07ba862c3fa6e7 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Wed, 31 Aug 2016 22:26:17 +0200 Subject: [PATCH] Clarify about the space holder for Windows In Windows we keep 256 MB to avoid warnings. --- HISTORY | 2 ++ cmdline/parity.c | 1 + snapraid.1 | 13 +++++-------- snapraid.d | 13 +++++-------- snapraid.txt | 13 +++++-------- 5 files changed, 18 insertions(+), 24 deletions(-) diff --git a/HISTORY b/HISTORY index b793e90e..42f985b4 100644 --- a/HISTORY +++ b/HISTORY @@ -10,6 +10,8 @@ SnapRAID HISTORY line, separated by , (comma). Note that if this feature is used, the saved content file won't be read by older SnapRAID versions. + In Windows, 256 MB are left free in each disk to avoid the warning + about full disks. * Added a new 'hashsize' configuration option. It could be useful in systems with low memory, to reduce the memory usage. Note that if this feature is used, the saved content file won't be diff --git a/cmdline/parity.c b/cmdline/parity.c index b3717e20..30d66dbc 100644 --- a/cmdline/parity.c +++ b/cmdline/parity.c @@ -369,6 +369,7 @@ static int parity_handle_fill(struct snapraid_split_handle* split, data_off_t si return -1; } + /* note that in Windows ftruncate is really allocating space */ if (ftruncate(spaceholder_f, spaceholder_size) != 0) { log_fatal("WARNING Failed to resize the space holder file '%s' to %llu bytes.\n", spaceholder_path, spaceholder_size); log_fatal("Assuming that no more space is available.\n"); diff --git a/snapraid.1 b/snapraid.1 index b778ac8d..0bf34f3f 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -1228,13 +1228,16 @@ The parity enables the protection from a single disk failure, like RAID5. .PP You can specify multiples files that should be in different disks. -When the first file cannot grow anymore, the next one is used. +When a file cannot grow anymore, the next one is used. The total space available must be as big as the biggest data disk in the array. .PP Leaving the parity disks reserved for parity ensures that it doesn\'t get fragmented, improving the performance. .PP +In Windows 256 MB are left unused in each disk to avoid the +warning about full disks. +.PP This option is mandatory and it can be used only one time. .SS (2,3,4,5,6)\-parity FILE [,FILE] ... Defines the files to use to store extra parity information. @@ -1257,13 +1260,7 @@ is enabled: Each parity level requires the precence of all the previous parity levels. .PP -You can specify multiples files that should be in different disks. -When the first file cannot grow anymore, the next one is used. -The total space available must be as big as the biggest data disk in -the array. -.PP -Leaving the parity disks reserved for parity ensures that -it doesn\'t get fragmented, improving the performance. +The same considerations of the \'parity\' option apply. .PP These options are optional and they can be used only one time. .SS z\-parity FILE [,FILE] ... diff --git a/snapraid.d b/snapraid.d index 2d30defe..5c16fe8f 100644 --- a/snapraid.d +++ b/snapraid.d @@ -931,13 +931,16 @@ Configuration failure, like RAID5. You can specify multiples files that should be in different disks. - When the first file cannot grow anymore, the next one is used. + When a file cannot grow anymore, the next one is used. The total space available must be as big as the biggest data disk in the array. Leaving the parity disks reserved for parity ensures that it doesn't get fragmented, improving the performance. + In Windows 256 MB are left unused in each disk to avoid the + warning about full disks. + This option is mandatory and it can be used only one time. (2,3,4,5,6)-parity FILE [,FILE] ... @@ -955,13 +958,7 @@ Configuration Each parity level requires the precence of all the previous parity levels. - You can specify multiples files that should be in different disks. - When the first file cannot grow anymore, the next one is used. - The total space available must be as big as the biggest data disk in - the array. - - Leaving the parity disks reserved for parity ensures that - it doesn't get fragmented, improving the performance. + The same considerations of the 'parity' option apply. These options are optional and they can be used only one time. diff --git a/snapraid.txt b/snapraid.txt index eaf12a31..fe29b41c 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -997,13 +997,16 @@ The parity enables the protection from a single disk failure, like RAID5. You can specify multiples files that should be in different disks. -When the first file cannot grow anymore, the next one is used. +When a file cannot grow anymore, the next one is used. The total space available must be as big as the biggest data disk in the array. Leaving the parity disks reserved for parity ensures that it doesn't get fragmented, improving the performance. +In Windows 256 MB are left unused in each disk to avoid the +warning about full disks. + This option is mandatory and it can be used only one time. 7.2 (2,3,4,5,6)-parity FILE [,FILE] ... @@ -1023,13 +1026,7 @@ is enabled: Each parity level requires the precence of all the previous parity levels. -You can specify multiples files that should be in different disks. -When the first file cannot grow anymore, the next one is used. -The total space available must be as big as the biggest data disk in -the array. - -Leaving the parity disks reserved for parity ensures that -it doesn't get fragmented, improving the performance. +The same considerations of the 'parity' option apply. These options are optional and they can be used only one time.