From: Arild Langseid <arild@langseid.no>
To: Michael Evans <mjevans1983@gmail.com>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: need help: corrupt files on one of my raids
Date: Wed, 11 Nov 2009 09:15:52 +0100 [thread overview]
Message-ID: <4AFA72B8.8010802@langseid.no> (raw)
In-Reply-To: <4877c76c0911102016k63f3e8ccled2b7f2a5cc3dffd@mail.gmail.com>
Hi Michael:
I still ran your advice and got this result:
creator:~# mdadm -D /dev/md1
/dev/md1:
Version : 00.90
Is it a big problem running version 0.9? I use the version of the tools
that comes with Debian - and as they are "some" conservative their
versions lags some behind.
I have now upgraded my Debian Etch to Debian Lenny and have this mdadm:
creator:~# mdadm --version
mdadm - v2.6.7.2 - 14th November 2008
When I fix the firmware issues on my motherboard or buys a sepparate
sata controller.... will the superblock be one of the version you
suggests when I create the raid again? If not is it that large problem
and I should upgrade my tools beyond what Debian provides?
Best Regards,
Arild
Michael Evans wrote:
> One other thing besides what's already been mentioned. You are seeing
> issues with Raid1 and -not- your Raid5 volume. If you run mdadm -D
> /dev/md(whatever the number is) what version (for the superblock) is
> reported? Preferably you will be using either superblock 1.1 or 1.2
> (preferably 1.1). The only reason to use mdadm 1.0 or 0.9 are special
> cases, such as for /boot style volumes.
> --
> 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 prev parent reply other threads:[~2009-11-11 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 14:07 need help: corrupt files on one of my raids Arild Langseid
2009-11-10 15:34 ` Majed B.
[not found] ` <4AF99159.4000800@langseid.no>
2009-11-10 18:26 ` Majed B.
[not found] ` <4AF9CB19.7000803@langseid.no>
2009-11-10 20:31 ` Majed B.
[not found] ` <4AF9D194.6000306@langseid.no>
2009-11-11 2:29 ` Majed B.
2009-11-11 4:16 ` Michael Evans
2009-11-11 8:06 ` Arild Langseid
2009-11-11 8:15 ` Arild Langseid [this message]
2009-11-11 8:25 ` Leslie Rhorer
2009-11-11 8:31 ` Michael Evans
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=4AFA72B8.8010802@langseid.no \
--to=arild@langseid.no \
--cc=linux-raid@vger.kernel.org \
--cc=mjevans1983@gmail.com \
/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.