Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Janos Haar" <djani22@netcenter.hu>
To: linux-raid@vger.kernel.org
Subject: questions about softraid limitations
Date: Wed, 14 May 2008 02:34:19 +0200	[thread overview]
Message-ID: <002801c8b55a$60e4a360$0404a8c0@dcccs> (raw)

Hello list, Neil,

I have worked on a faulty hw raid card data recovery some days before.
The project is already successfully done, but i run into some limitations.

For the best safe way first i have jumperd the drives to readonly mode.

Than try to build an "old fashion" linear arrays from each disks + 64k 
another blockdevice. (for store the superblock)
But the mdadm refused to _build_ the array, because the source scsi drive is 
jumpered to readonly. Why? :-)

I try to build the array with --readonly option, but the mdadm still dont 
understand what i want. (yes, i know, rtfm...)

The next step is:

mdadm --create --assume-clean -l 5 /dev/mdX --raid-disks 5 /dev/....

(And this step is refused too if the drives or some part of the sources are 
readonly.)

Its OK, but what about building a readonly raid 5 array for recovery usage 
only? :-)
And _build_ a degraded-readonly raid 4-5-6 is even better if this will ever 
available....

And i need to set the readonly flag _after_ the --create, but the --create 
+ --assume-clean is logical, and working combination with --readonly.

More additionally, i think the only write the superblocks to the disks, when 
the --readonly flag is cleared.
And more, if the readonly raid 4-5-6 array can handle, and recover the bad 
sectors from the parity infos.... hmmmm... :-)

These little options can be great help for data recovery, and all is safe.

Thanks and regards,

Janos Haar




             reply	other threads:[~2008-05-14  0:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  0:34 Janos Haar [this message]
2008-05-14 10:45 ` questions about softraid limitations David Greaves
2008-05-14 23:29   ` Janos Haar
2008-05-16  1:39     ` Neil Brown
2008-05-16  6:05       ` [OT] " Peter Rabbitson
2008-05-18 23:52         ` Neil Brown
2008-05-16 10:00       ` Janos Haar
2008-05-16  8:36     ` David Greaves
2008-05-16  9:18       ` David Greaves
2008-05-16  9:28       ` Janos Haar
2008-05-18  9:11         ` David Greaves
2008-05-18 11:11           ` Janos Haar
2008-05-18 13:00             ` David Greaves
2008-05-18 21:51               ` Janos Haar
2008-05-18 19:36           ` David Lethe
2008-05-18 22:23             ` David Greaves
2008-05-18 22:38               ` Janos Haar
  -- strict thread matches above, loose matches on Subject: below --
2008-05-18 23:18 David Lethe

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='002801c8b55a$60e4a360$0404a8c0@dcccs' \
    --to=djani22@netcenter.hu \
    --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