From: NeilBrown <neilb@suse.com>
To: Veljko <veljko3@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Linear device of two arrays
Date: Fri, 21 Jul 2017 08:00:44 +1000 [thread overview]
Message-ID: <87d18uydir.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <38e015fa-a07c-8f1a-3a04-384d973966be@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Mon, Jul 17 2017, Veljko wrote:
> On 07/15/2017 02:12 AM, NeilBrown wrote:
>
>> So command should be
>>
>>>> dd if=/dev/md2 of=SOMEWHERE/SAFE bs=1M skip=5626590
>>
>> and expect it to create a 3M file.
>>
>> Use this 'skip' number of the 'seek' number later.
>>
>> NeilBrown
>
> Thanks, Neil, now it makes more sense.
>
> I tried to create new linear device, but mdadm is complaining about
> data-offset:
>
> # mdadm -C /dev/md4 -l linear -n 2 --rounding=1M -e 1.0 --data-offset=0
> /dev/md2 /dev/md3
> mdadm: invalid data-offset: 0
Bother.
mdadm uses "parse_size()" to parse the offset, and this rejects
"0", which makes sense for a size, but not for an offset.
Just leave the "--data-offset=0" out. I checked and that is defintely
the default for 1.0.
> I noticed that md2 and md3 use 1.2 metadata. Can that be the issue?
No the metadata on md4 is quite independent of the metadata on md2 and md3.
NeilBrown
>
> I'm using Debian 8.8 if it makes any difference.
>
> # mdadm -V
> mdadm - v3.3.2 - 21st August 2014
>
> What could be the problem?
>
> Regards,
> Veljko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-07-20 22:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 15:34 Linear device of two arrays Veljko
2017-07-05 16:42 ` Roman Mamedov
2017-07-05 18:07 ` Wols Lists
2017-07-07 11:07 ` Nix
2017-07-07 20:26 ` Veljko
2017-07-07 21:20 ` Andreas Klauer
2017-07-07 21:53 ` Roman Mamedov
2017-07-07 22:20 ` Andreas Klauer
2017-07-07 22:33 ` Andreas Klauer
2017-07-07 22:52 ` Stan Hoeppner
2017-07-08 10:26 ` Veljko
2017-07-08 21:24 ` Stan Hoeppner
2017-07-09 22:37 ` NeilBrown
2017-07-10 11:03 ` Veljko
2017-07-12 10:21 ` Veljko
2017-07-14 2:03 ` NeilBrown
2017-07-14 1:57 ` NeilBrown
2017-07-14 2:05 ` NeilBrown
2017-07-14 13:40 ` Veljko
2017-07-15 0:12 ` NeilBrown
2017-07-17 10:16 ` Veljko
2017-07-18 8:58 ` Veljko
2017-07-20 21:40 ` Veljko
2017-07-20 22:00 ` NeilBrown [this message]
2017-07-21 9:15 ` Veljko
2017-07-21 11:37 ` Veljko
2017-07-22 23:03 ` NeilBrown
2017-07-23 10:05 ` Veljko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d18uydir.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=veljko3@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).