From: Thomas Backlund <tmb@mandriva.org>
To: linux-raid@vger.kernel.org
Subject: Re: Problem with mdadm 2.6.7
Date: Sun, 27 Jul 2008 17:26:33 +0300 [thread overview]
Message-ID: <488C8599.4090503@mandriva.org> (raw)
In-Reply-To: <488C531B.5060005@mandriva.org>
Hi,
(please cc me as I'm not subscribed)
I have hit a bug with mdadm 2.6.7
It rebuilds my raid5 array on every boot
(raid0 and raid1 arrays are not affected)
This didn't happend with 2.6.4
kernels tested are 2.6.24.7 and 2.6.25.12
Arch is x86_64
Distro Mandriva 2008.1, but I've tested wich kernel.org kernels and
upstream mdadm 2.6.7 and have the same problem
Now I could try to bisect it, but every raid5 rebuild takes 6-7 hours,
so I thought about asking for pointers before...
Any ideas where to start looking ?
here is the info on the array that gets rebuilt...
[root@tmb ~]# mdadm --detail /dev/md8
/dev/md8:
Version : 00.90
Creation Time : Fri Feb 1 17:44:23 2008
Raid Level : raid5
Array Size : 1465143808 (1397.27 GiB 1500.31 GB)
Used Dev Size : 732571904 (698.64 GiB 750.15 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 8
Persistence : Superblock is persistent
Update Time : Sun Jul 27 13:32:30 2008
State : clean, degraded, recovering
Active Devices : 2
Working Devices : 3
Failed Devices : 0
Spare Devices : 1
Layout : left-symmetric
Chunk Size : 128K
Rebuild Status : 1% complete
UUID : dc482f3f:ad67b9ef:bb6636b8:e9392071
Events : 0.16162
Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1
3 8 65 2 spare rebuilding /dev/sde1
next parent reply other threads:[~2008-07-27 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <488C531B.5060005@mandriva.org>
2008-07-27 14:26 ` Thomas Backlund [this message]
2008-07-27 15:06 ` Problem with mdadm 2.6.7 Doug Ledford
2008-07-27 15:24 ` Thomas Backlund
2008-07-27 19:31 ` Doug Ledford
2008-07-29 0:59 ` Neil Brown
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=488C8599.4090503@mandriva.org \
--to=tmb@mandriva.org \
--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.