From: Pierre Beck <mail@pierre-beck.de>
To: freeone3000 <freeone3000@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Data Offset
Date: Wed, 20 Jun 2012 16:09:41 +0200 [thread overview]
Message-ID: <4FE1D9A4.5010003@pierre-beck.de> (raw)
In-Reply-To: <CAFhY2ChB03GWOSWjX=YAEkZSLiqQp6LZUhqcnPVfpbpeL3iJ0w@mail.gmail.com>
Through the re-creation of the array, metadata has been fixed and the
array is now as good as it was before the little accident. You can
configure auto-assembly of the array as usual in mdadm.conf (updating
the UUID is probably all you need to do). Also, you can now add the
spare disk with your standard mdadm.
Am 20.06.2012 15:54, schrieb freeone3000:
> Thanks a lot for your help. I have my data back! Played a few movie
> files off of the mounted drive, and they all worked perfect. Sorry for
> being such a dunce with the block sizes.
>
> `/dev/sdc3:2048s /dev/sdb3:2048s /dev/sde:2048s /dev/sdd3:1024s
> missing` mounted the drive successfully. Now, is there a way to
> "normalize" my drives so I can mount it without running through this
> guesswork again? Or that I can re-create my array using a standard
> mdadm?
>
> On Wed, Jun 13, 2012 at 1:49 PM, Piergiorgio Sartor
> <piergiorgio.sartor@nexgo.de> wrote:
>> Hi all,
>>
>> On Wed, Jun 13, 2012 at 08:22:02PM +0200, Pierre Beck wrote:
>>> I wonder if LVM activation can be done without writing to the array?
>>> IIRC it updates at least some timestamp ...
>> we tried setting the array itself read only,
>> which prevent (or it should) anybody above,
>> filesystem or LVM, to perform writes...
>>
>> Neveretheless, the result was a bit "strange",
>> namely a kernel BUG() or similar, we had to
>> reset the PC.
>>
>> I'm not sure if this was caused by other issue,
>> since the PC was in a not really healty state,
>> or a direct consequence of md device in r/o.
>>
>> bye,
>>
>> --
>>
>> piergiorgio
>> --
>> 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
>
>
>
> --
> James Moore
> --
> 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
>
next prev parent reply other threads:[~2012-06-20 14:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 23:22 Data Offset freeone3000
2012-06-01 23:52 ` NeilBrown
2012-06-02 0:48 ` freeone3000
2012-06-04 3:35 ` NeilBrown
2012-06-04 18:26 ` Pierre Beck
2012-06-04 22:57 ` NeilBrown
2012-06-05 5:26 ` freeone3000
2012-06-05 5:44 ` NeilBrown
[not found] ` <CAFhY2CiDTMRSV2wFCMhT9ZstUkHkJS7E0p7SP-ssfqwaquo+0w@mail.gmail.com>
[not found] ` <20120610074531.65eaed81@notabene.brown>
[not found] ` <CAFhY2CgxkjH6JvJzvQt9XT0oawntK7YoTFqnXQJGzvqthD8XpQ@mail.gmail.com>
2012-06-13 9:46 ` Pierre Beck
2012-06-13 12:49 ` Phil Turmel
2012-06-13 17:56 ` Pierre Beck
2012-06-13 18:11 ` Phil Turmel
2012-06-13 18:22 ` Pierre Beck
2012-06-13 18:49 ` Piergiorgio Sartor
2012-06-20 3:56 ` freeone3000
2012-06-20 14:09 ` Pierre Beck [this message]
2012-06-25 6:25 ` NeilBrown
2014-02-24 11:22 ` wiebittewas
2014-02-24 21:38 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 14:11 Data offset Patrik Horník
2014-05-15 22:07 ` NeilBrown
2014-05-16 0:41 ` Patrik Horník
2012-05-10 17:42 Data Offset Piergiorgio Sartor
2012-05-24 5:20 ` NeilBrown
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=4FE1D9A4.5010003@pierre-beck.de \
--to=mail@pierre-beck.de \
--cc=freeone3000@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).