From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Re: Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm?
Date: Thu, 28 Jun 2012 10:59:19 +0200 [thread overview]
Message-ID: <4FEC1CE7.5010709@xunil.at> (raw)
In-Reply-To: <20120628163205.2c6a1122@notabene.brown>
Am 28.06.2012 08:32, schrieb NeilBrown:
> On Tue, 26 Jun 2012 15:57:21 +0200 "Stefan G. Weichinger"
> <lists@xunil.at> wrote:
>> Could that relate to this issue:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500309
>
> Nope. It was an earlier bug fixed in 2.6.5 by
>
> http://neil.brown.name/git?p=mdadm;a=commitdiff;h=7a3be72fc621b4a7589e923cf065
Ah,
>
I see. So this *could* be solved by using a more recent mdadm,
correct?
>> The NAS seems to run some ubuntu:
>>
>> # cat /proc/version Linux version 2.6.33.2 (root@NasX86-5) (gcc
>> version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1
>> SMP Mon Sep 13 04:28:32 CST 2010
>
> Does the "X86" in there suggest and x86 processor? What does
> "uname -a" show?
# uname -a
Linux NASCA0A00 2.6.33.2 #1 SMP Mon Sep 13 04:28:32 CST 2010 i686 unknown
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 28
model name : Intel(R) Atom(TM) CPU D525 @ 1.80GHz
stepping : 10
cpu MHz : 1795.730
cache size : 512 KB
[...]
> You mean the NAS didn't come with a complete build environment and
> sources for all programs? Outrageous.
*sigh*
> If you have a machine with the same arch at the NAS, you could
>
> git clone git://neil.brown.name/mdadm -b mdadm-2.6.5 cd mdadm make
> mdadm.static CWFLAGS=-Wall
>
> and then use the "mdadm.static" on the NAS.
Ok, thanks. I could boot some ubuntu on my Atom-netbook .. or what?
Would it be enough to match the 64bit-environment, or would I have to
use something with the same kernel ... ?
Thanks! Stefan
next prev parent reply other threads:[~2012-06-28 8:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 13:57 Re-adding disks to RAID6 in a Fujitsu NAS: old mdadm? Stefan G. Weichinger
2012-06-27 10:17 ` Stefan G. Weichinger
2012-06-27 11:34 ` Stefan G. Weichinger
2012-06-27 11:38 ` Stefan G. Weichinger
2012-06-28 6:32 ` NeilBrown
2012-06-28 8:59 ` Stefan G. Weichinger [this message]
2012-06-28 9:14 ` Stefan G. Weichinger
2012-06-28 9:23 ` Stefan G. Weichinger
2012-06-28 11:22 ` NeilBrown
2012-06-28 15:56 ` Stefan G. Weichinger
2012-06-28 18:25 ` Stefan G. Weichinger
2012-06-28 21:36 ` NeilBrown
2012-06-29 8:18 ` Stefan G. Weichinger
2012-07-02 8:30 ` Stefan G. Weichinger
2012-06-28 21:39 ` NeilBrown
2012-06-28 9:39 ` NeilBrown
2012-06-28 9:42 ` Stefan G. Weichinger
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=4FEC1CE7.5010709@xunil.at \
--to=lists@xunil.at \
--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.