All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: David Reniau <david.reniau@gmail.com>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: My Thecus RAID-0 filesystem unmountable with mdadm. Please help.
Date: Thu, 27 May 2010 11:39:53 +0100	[thread overview]
Message-ID: <4BFE4BF9.9060708@anonymous.org.uk> (raw)
In-Reply-To: <AANLkTimDAbGPqen2dW7wtpxMjSup0IK8kcdNEnskibw-@mail.gmail.com>

On 27/05/2010 02:03, David Reniau wrote:
> Dear Linux-RAID gurus,

That's very kind of you but I'm no guru, just a user like yourself, 
though perhaps with a little more experience and I've hung around here a 
while because I like to know what goes on inside the black box.

[...]
> Similarly, IF the default chunk size (64K) i've been using so far with
> mdadm happens to be different from the Thecus', would the above
> tune2fs -l /dev/md0 command deliver results identical to the above
> ones with the corrected Thecus chunk size applied via mdadm
> --assemble? Could this parameter modification be sufficient to get my
> RAID filesystem back and mountable?

I don't know if the tune2fs info will be identical but it would be 
similar. You'll need to --create the array again with the corrected 
chunk size, not just --assemble it, but yes this on its own might very 
well be enough to get your filesystem back.

Cheers,

John.


  reply	other threads:[~2010-05-27 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  1:03 My Thecus RAID-0 filesystem unmountable with mdadm. Please help David Reniau
2010-05-27 10:39 ` John Robinson [this message]
2010-05-28  1:32 ` Michael Evans
  -- strict thread matches above, loose matches on Subject: below --
2010-05-24 12:40 David Reniau
2010-05-24 21:57 ` Michael Evans
2010-05-25  0:33 ` Neil Brown
2010-05-25  5:57   ` Mikael Abrahamsson
2010-05-25  5:09 ` Luca Berra
2010-05-25  7:59 ` John Robinson

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=4BFE4BF9.9060708@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=david.reniau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.