From: Tim Small <tim@seoss.co.uk>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: a general question re. linux-raid stability
Date: Tue, 21 Sep 2010 10:27:19 +0100 [thread overview]
Message-ID: <4C987A77.7050903@seoss.co.uk> (raw)
In-Reply-To: <4C97DFB4.1010705@meetinghouse.net>
On 20/09/10 23:27, Miles Fidelman wrote:
> Folks,
>
> I've been watching patch after patch go by on this list, which leads
> me to wonder - how stable are the basic raid kernel modules, and
> mdadm, as included in major linux distributions (in my case, Debian
> Lenny)?
Pretty good - we use it on a few tens of servers. Overall we find it
easier to manage, and more reliable than hardware RAID...
Debian definitely gets updates - although the Debian team could probably
do with more help keeping tabs on them. Two good cross-reference
sources are probably this list, and the RHEL kernel update changelogs.....
tim@zebedee:~$ cat /etc/debian_version
5.0.6
tim@zebedee:~$ zgrep -i raid
/usr/share/doc/linux-image-2.6.26-2-amd64/changelog.Debian.gz | egrep -v
'(aacraid|megaraid|cpq|5c1|dm|DM|cciss|LVM|sym)'
* raid456: Fix two bugs in handling of degraded states (Closes: #581392)
- Prevent reshaping of doubly-degraded RAID4
- Enable error-correction on singly-degraded RAID6
- md: fix raid5 'repair' operations
- Fix sparc64 niagara optimized RAID xor asm
- md: raid5: fix clearing of biofill operations
- raid5: fix unending write sequence
- md: handle writes to broken raid10 arrays gracefully
- md: raid10: fix use-after-free of bio
- md: Avoid overflow in raid0 calculation with large components.
- md/raid1 to a filesystem.
- md: Fix raid10 recovery problem.
- Fix various bugs with aligned reads in RAID5.
* Fix raid1 recovery (closes: #406181)
- Set a default raid level on a volume that either does not support
* Enable raid456 for mips/mipsel qemu kernel.
- md: Fix calculation of ->degraded for multipath and raid10
- MD: Fix a potential NULL dereference in md/raid1
- md: Avoid oops when attempting to fix read errors on raid10
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
next prev parent reply other threads:[~2010-09-21 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 1:42 [PATCH 1/2] PPC4xx: Generelizing drivers/dma/ppc4xx/adma.c tmarri
2010-09-18 21:09 ` Wolfgang Denk
2010-09-20 18:00 ` Tirumala Marri
2010-09-20 21:31 ` Wolfgang Denk
2010-09-20 22:27 ` a general question re. linux-raid stability Miles Fidelman
2010-09-21 2:19 ` Daniel Reurich
2010-09-21 9:27 ` Tim Small [this message]
2010-09-21 15:35 ` Miles Fidelman
2010-09-21 17:00 ` Andre Tomt
2010-09-23 20:22 ` [PATCH 1/2] PPC4xx: Generelizing drivers/dma/ppc4xx/adma.c Dan Williams
2010-09-23 22:39 ` Tirumala Marri
2010-09-24 6:58 ` Stefan Roese
2010-09-24 18:52 ` Tirumala Marri
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=4C987A77.7050903@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mfidelman@meetinghouse.net \
/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).