From: "Lars Täuber" <taeuber@bbaw.de>
To: linux-raid@vger.kernel.org
Subject: Re: Reopen: 16 HDDs too much for RAID6?
Date: Fri, 28 Mar 2008 11:55:37 +0100 [thread overview]
Message-ID: <20080328115537.ad40f3dc.taeuber@bbaw.de> (raw)
In-Reply-To: <200803281135.20890.bs@q-leap.de>
Hi Bernd,
Bernd Schubert <bs@q-leap.de> schrieb:
> > Here the conf file:
> > monosan:~ # cat /etc/mdadm.conf
> > DEVICE /dev/sd[ab][0-9] /dev/dm-*
> > ARRAY /dev/md2 level=raid1 UUID=d9d31de2:e6dbd3c3:37c7ea09:882a64e5
> > ARRAY /dev/md3 level=raid1 num-devices=2
> > UUID=a8687183:a79e514c:ca492c4b:ffd4384f ARRAY /dev/md4 level=raid6
> > num-devices=15 spares=1 UUID=cfcbe071:f6766d8f:0f1ffefa:892d09c3 ARRAY
> > /dev/md9 level=raid1 num-devices=2 name=9
> > UUID=db687150:614e76fd:28feefc0:b1aae572
> >
> > All dm-* devices are really distinctive. I could post the
> > /etc/multipath.conf too if you want.
here is the file:
monosan:~ # cat /etc/multipath.conf
#
# This configuration file is generated by Yast, do not modify it
# manually please.
#
defaults {
polling_interval "0"
user_friendly_names "yes"
# path_grouping_policy "multibus"
}
blacklist {
# devnode "*"
wwid "SATA_WDC_WD1600YS-01_WD-WCAP02964085"
wwid "SATA_WDC_WD1600YS-01_WD-WCAP02965435"
}
blacklist_exceptions {
}
multipaths {
mutlipath {
wwid "SATA_ST31000340NS_5QJ02TBK"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ0185Y"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ02QRQ"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ0204G"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ02TVQ"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ012AL"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ00PHN"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ01BYF"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ026J1"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ01G09"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ02461"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ013GW"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ01835"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ01C49"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ02TBZ"
}
mutlipath {
wwid "SATA_ST31000340NS_5QJ01JSF"
}
}
> I only have very little experience with multipathing, but please send your
> config. The fact you really do use multipathing only confirms my initial
> guess it is a multipath and not a md problem.
But when I assemble the array after a clean shutdown after it has been initially synced there is no problem. Just if the array was degraded it has such duplicated superblocks.
How comes?
Lars
next prev parent reply other threads:[~2008-03-28 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 9:01 16 HDDs too much for RAID6? Lars Täuber
2008-03-06 9:45 ` Andre Noll
2008-03-06 10:55 ` Lars Täuber
2008-03-06 16:16 ` Andre Noll
2008-03-07 8:41 ` Luca Berra
2008-03-07 10:33 ` Andre Noll
2008-03-07 10:45 ` Lars Täuber
2008-03-28 9:20 ` Reopen: " Lars Täuber
2008-03-28 10:14 ` Bernd Schubert
2008-03-28 10:27 ` Lars Täuber
2008-03-28 10:35 ` Bernd Schubert
2008-03-28 10:55 ` Lars Täuber [this message]
2008-03-28 11:20 ` Bernd Schubert
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=20080328115537.ad40f3dc.taeuber@bbaw.de \
--to=taeuber@bbaw.de \
--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;
as well as URLs for NNTP newsgroup(s).