linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-raid@vger.kernel.org
Subject: Re: Error mounting a reiserfs on renamed raid1
Date: Fri, 25 Jan 2008 20:56:50 +0100	[thread overview]
Message-ID: <479A3F02.3010403@anagramm.de> (raw)
In-Reply-To: <20080125085741.GA581@cthulhu.home.robinhill.me.uk>

Robin Hill schrieb:
> On Fri Jan 25, 2008 at 01:48:32AM +0100, Clemens Koller wrote:
> 
>> Hi there.
>>
>> I am new to this list, however didn't find this effect nor a
>> solution to my problem in the archives or with google:
>>
>> short story:
>> ------------
>> A single raid1 as /dev/md0 containing a reiserfs (with important data)
>> assembled during boot works just fine:
>> $ cat /proc/mdstat
>> Personalities : [linear] [raid0] [raid1]
>> md0 : active raid1 hdg1[1] hde1[0]
>>       293049600 blocks [2/2] [UU]
>>
>> The same raid1 moved to another machine as a fourth raid can be
>> assembled manually as /dev/md3 (to work around naming conflicts),
>> but it cannot be mounted anymore:
>> $ mdadm --assemble /dev/md3 --update=super-minor -m0 /dev/hde /dev/hdg
>> does not complain. /dev/md3 is created. But
>>
> It looks like you should be assembling the partitions, not the disks.
> Certainly the mdstat entry above shows the array being formed from the
> disks.  Try:
>   mdadm --assemble /dev/md3 --update=super-minor -m0 /dev/hde1 /dev/hdg1

Argh, that was too simple. I thought I've tried to assemble the
partitions (/dev/hdx1) too instead of the whole disks but I guess
I was wrong.

A simple
mdadm --assemble /dev/md3 /dev/hde1 /dev/hdg1
did the job

Thank you!

Regards,

Clemens


      reply	other threads:[~2008-01-25 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25  0:48 Error mounting a reiserfs on renamed raid1 Clemens Koller
2008-01-25  8:57 ` Robin Hill
2008-01-25 19:56   ` Clemens Koller [this message]

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=479A3F02.3010403@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --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).