From: Andreas John <lists@aj.net-lab.net>
To: linux-raid@vger.kernel.org
Cc: neilb@cse.unsw.edu.au
Subject: mdadm question
Date: Fri, 20 Aug 2004 18:18:13 +0200 [thread overview]
Message-ID: <41262445.8010509@aj.net-lab.net> (raw)
Hello!
I have a question about mdadm usage. One of me customers killed a
raid5+1 by accidently removing an ide bus with two disk on it (dont't
ask, I know ;-))
Assuming that the data is on the disks I'm looking for a way to convince
linux to mark the superblocks (of the missing disk only?) as "not
failed" so that the raid comes up again. mdadm seems to have what I am
looking for, like "madm --assemble --update=? --force" can write the
superblocks freshly without destorying the data on it? Do I have to use
--update=super‐minor or --update=super‐minor on ia32?
Or is there an recovery tool for such a case (i.e. mddump?)?
If this does not work, can anyone point me out where I can find an
overview about the structure of a superblock, so that I may fix the
problem via hex-editor (my skills point back to C64 times ... :-))
I've seen the source but some kind of overview/scheme would be nice.
I'm scared. :)
Rgds,
Andreas
-
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 reply other threads:[~2004-08-20 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 16:18 Andreas John [this message]
2004-08-20 22:11 ` mdadm question Neil Brown
[not found] <1352887864.2731.1267578731820.JavaMail.root@mail1>
2010-03-03 1:15 ` Robert Minvielle
2010-03-03 1:42 ` Neil Brown
2010-03-03 1:45 ` Leslie Rhorer
2010-03-03 16:51 ` Bill Davidsen
[not found] <2127483366.2736.1267585385014.JavaMail.root@mail1>
2010-03-03 3:05 ` Robert Minvielle
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=41262445.8010509@aj.net-lab.net \
--to=lists@aj.net-lab.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).