From: Dragos <dragos@mpigani.org>
To: David Greaves <david@dgreaves.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: assemble vs create an array.......
Date: Thu, 06 Dec 2007 10:17:49 -0500 [thread overview]
Message-ID: <4758129D.40600@mpigani.org> (raw)
In-Reply-To: <47568DE1.1050108@dgreaves.com>
Thank you.
I want to make sure I understand.
1- Does it matter which permutation of drives I use for xfs_repair (as
long as it tells me that the Structure needs cleaning)? When it comes to
linux I consider myself at intermediate level, but I am a beginner when
it comes to raid and filesystem issues.
2- After I do it, assuming that it worked, how do I reintegrate the
'missing' drive while keeping my data?
Thank you for you time.
Dragos
David Greaves wrote:
> Dragos wrote:
>
>> Thank you for your very fast answers.
>>
>> First I tried 'fsck -n' on the existing array. The answer was that If I
>> wanted to check a XFS partition I should use 'xfs_check'. That seems to
>> say that my array was partitioned with xfs, not reiserfs. Am I correct?
>>
>> Then I tried the different permutations:
>> mdadm --create /dev/md0 --raid-devices=3 --level=5 missing /dev/sda1
>> /dev/sdb1
>> mount /dev/md0 temp
>> mdadm --stop --scan
>>
>> mdadm --create /dev/md0 --raid-devices=3 --level=5 /dev/sda1 missing
>> /dev/sdb1
>> mount /dev/md0 temp
>> mdadm --stop --scan
>>
>>
> [etc]
>
>
>> With some arrays mount reported:
>> mount: you must specify the filesystem type
>> and with others:
>> mount: Structure needs cleaning
>>
>> No choice seems to have been successful.
>>
>
> OK, not as good as you could have hoped for.
>
> Make sure you have the latest xfs tools.
>
> you may want to try xfs_repair and you can use the -n (I think - check man page)
> option.
>
> You may need to force it to ignore the log
>
> David
>
>
>
>
next prev parent reply other threads:[~2007-12-06 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 3:42 assemble vs create an array Dragos
2007-11-30 5:32 ` Neil Brown
2007-11-30 14:26 ` David Greaves
2007-12-01 6:48 ` Dragos
2007-12-01 7:23 ` Dragos
2007-12-04 13:14 ` Dragos
2007-12-05 11:39 ` David Greaves
2007-12-06 15:17 ` Dragos [this message]
2007-12-06 16:39 ` Michael Tokarev
2007-12-06 17:12 ` Eric Sandeen
2007-12-06 21:22 ` David Chinner
2008-02-03 7:42 ` Dragos
2007-11-30 14:53 ` Bryce
2007-11-30 17:40 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2008-01-28 7:21 Dragos
2008-01-28 7:25 Dragos
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=4758129D.40600@mpigani.org \
--to=dragos@mpigani.org \
--cc=david@dgreaves.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).