Hi Phil,
On 17/05/2020 22:56, Phil Turmel wrote:
Your math is wrong. Or rather, you are using the bogus power-of-ten
definition of "MB" that disk manufacturers use to deliver less space.
Use 128MB. Or better, specify "262144s".
Thanks very much, that was the final thing, and now I have a working
array again and don't have to worry about pulling 6TB of data down from S3.
I had no idea that you could use sectors as a suffix to data-offset as
it's not in the manpage. So you should find attached a patch file which
adds that suffix to the manpage. If this isn't the correct place to
provide patches, or if there's an issue with the formatting of my patch,
please let me know and I'll happily update it and send it to the correct
place.
Best Regards,
Sam
>From 116bc0ddeb29e848077480853a41c509518eb8ff Mon Sep 17 00:00:00 2001
From: Sam Hurst <sam@xxxxxxxxxxxxxxx>
Date: Mon, 18 May 2020 19:48:13 +0100
Subject: [PATCH] Add sector suffix to mdadm --data-offset manpage
---
mdadm.8.in | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/mdadm.8.in b/mdadm.8.in
index 9e7cb96..c997be4 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -857,8 +857,9 @@ an array which was originally created using a different version of
which computed a different offset.
Setting the offset explicitly over-rides the default. The value given
-is in Kilobytes unless a suffix of 'K', 'M', 'G' or 'T' is used to explicitly
-indicate Kilobytes, Megabytes, Gigabytes or Terabytes respectively.
+is in Kilobytes unless a suffix of 'K', 'M', 'G', 'T' or 's' is used to
+explicitly indicate Kilobytes, Megabytes, Gigabytes, Terabytes or sectors
+respectively.
Since Linux 3.4,
.B \-\-data\-offset
--
2.17.1
