Linux RAID Storage Date Index

• Thread Index

• Re: [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: Slackware and RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: USB and raid... Device names change
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• USB and raid... Device names change
  • From: Eduardo Jacob <edu@xxxxxxxxx>
• Re: USB disks for RAID storage (was Re: Please help me save my data)
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: scrub was Re: RAID5 Problem - $1000 reward for help
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• scrub was Re: RAID5 Problem - $1000 reward for help
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: Ask Bjørn Hansen <ask@xxxxxxxxxxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• RE: ATA cables and drives
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• USB disks for RAID storage (was Re: Please help me save my data)
  • From: Daniel Pittman <daniel@xxxxxxxxxxxx>
• Re: Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• Re: Slackware and RAID
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Slackware and RAID
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Slackware and RAID
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• RE: proactive-raid-disk-replacement
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• Re: Slackware and RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: ATA cables and drives
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: ATA cables and drives
  • From: Jeff Woods <Kazrak+kernel@xxxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 fill up?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• ATA cables and drives
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Please help me save my data
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Slackware and RAID
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: 2.6.18-rc5-mm1 - bd_claim_by_disk oops
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [PATCH] [v2] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: [PATCH 16/19] dmaengine: Driver for the Intel IOP 32x, 33x, and 13xx RAID engines
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: [PATCH 09/19] dmaengine: reduce backend address permutations
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: Ask Bjørn Hansen <ask@xxxxxxxxxxxxxx>
• RAID5 Problem - $1000 reward for help
  • From: Reza Naima <reza@xxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: [PATCH] missing close in mdassemble
  • From: Luca Berra <bluca@xxxxxxxxxx>
• I think there is a trick to improve performance of md.
  • From: liyiming <liyiming@xxxxxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Greg KH <gregkh@xxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raidhotadd works, mdadm --add doesn't
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: access *exisiting* array from knoppix
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: access array from knoppix
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: access *exisiting* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access *exisiting* array from knoppix
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Turbo Fredriksson <turbo@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jakob Oestergaard <jakob@xxxxxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• [PATCH] missing close in mdassemble
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access *existing* array from knoppix
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• raid 5 kernel error
  • From: Sterpu Victor <victor@xxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Ric Wheeler <ric@xxxxxxx>
• libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jakob Oestergaard <jakob@xxxxxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• RE: Correct way to create multiple RAID volumes with hot-spare?
  • From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@xxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Moving a raid5 array
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Moving a raid5 array
  • From: Neil Brown <neilb@xxxxxxx>
• Moving a raid5 array
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access *exisiting* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access array from knoppix
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• access array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 18/19] iop3xx: Give Linux control over PCI (ATU) initialization
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 17/19] iop3xx: define IOP3XX_REG_ADDR[32|16|8] and clean up DMA/AAU defs
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 15/19] dmaengine: raid5 dma client
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 14/19] dmaengine: add dma_sync_wait
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 12/19] dmaengine: dma_async_memcpy_err for DMA engines that do not support memcpy
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 11/19] dmaengine: add memset as an asynchronous dma operation
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 02/19] raid5: move write operations to a workqueue
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 01/19] raid5: raid5_do_soft_block_ops
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• [PATCH 07/19] raid5: remove compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 02/19] raid5: move write operations to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 03/19] raid5: move check parity operations to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 05/19] raid5: move read completion copies to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 10/19] dmaengine: expose per channel dma mapping characteristics to clients
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 19/19] iop3xx: IOP 32x and 33x support for the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 13/19] dmaengine: add support for dma xor zero sum operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 12/19] dmaengine: dma_async_memcpy_err for DMA engines that do not support memcpy
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 09/19] dmaengine: reduce backend address permutations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 17/19] iop3xx: define IOP3XX_REG_ADDR[32|16|8] and clean up DMA/AAU defs
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 15/19] dmaengine: raid5 dma client
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 16/19] dmaengine: Driver for the Intel IOP 32x, 33x, and 13xx RAID engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 18/19] iop3xx: Give Linux control over PCI (ATU) initialization
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 14/19] dmaengine: add dma_sync_wait
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 06/19] raid5: move the reconstruct write expansion operation to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 11/19] dmaengine: add memset as an asynchronous dma operation
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 04/19] raid5: move compute block operations to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 01/19] raid5: raid5_do_soft_block_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: raidhotadd works, mdadm --add doesn't
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Please help me save my data
  • From: "Patrick Hoover" <phoover.eml@xxxxxxxxx>
• Re: Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• raidhotadd works, mdadm --add doesn't
  • From: Leon Avery <leon@xxxxxxxxxxxxxxxxxx>
• raidhotadd works, mdadm --add doesn't
  • From: Leon Avery <leon@xxxxxxxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: UUID's
  • From: dean gaudet <dean@xxxxxxxxxx>
• RE: 2 Hard Drives & RAID
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• Re: 2 Hard Drives & RAID
  • From: Sandra McGrew <nurse1@xxxxxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Bodo Thiesen <bothie@xxxxxx>
• Re: 2 Hard Drives & RAID
  • From: berk walker <berk@xxxxxxxxx>
• Re: 2 Hard Drives & RAID
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Check/repair on composite RAID
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• 2 Hard Drives & RAID
  • From: "Sandra L. McGrew" <momo_1@xxxxxxxxxx>
• Re: Please help me save my data
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Check/repair on composite RAID
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: UUID's
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: UUID's
  • From: dean gaudet <dean@xxxxxxxxxx>
• UUID's
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Messed up creating new array...
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• 2.6.18-rc5-mm1 - bd_claim_by_disk oops
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Messed up creating new array...
  • From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: Interesting RAID checking observations - I'm getting it too
  • From: Mark Smith <nanog@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• proactive-raid-disk-replacement
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Ralf Herrmann <ralf.herrmann@xxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Raid5 reads and cpu
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Raid5 reads and cpu
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: checking state of RAID (for automated notifications)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: RAID-5 recovery
  • From: John McMonagle <johnm@xxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: checking state of RAID (for automated notifications)
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• checking state of RAID (for automated notifications)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Care and feeding of RAID?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: "Rev. Jeffrey Paul" <sneak@xxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Patrik Jonsson <patrik@xxxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: RAID over Firewire
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: large copy to mdadm array fails, marks readonly
  • From: Neil Brown <neilb@xxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Neil Brown <neilb@xxxxxxx>
• large copy to mdadm array fails, marks readonly
  • From: "Alan Gibson" <alan.gibson@xxxxxxxxx>
• checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: checkarray: E: no kernel support for parity checks.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Interesting RAID checking observations - I'm getting it too
  • From: Mark Smith <nanog@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: RAID over Firewire
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID over Firewire
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux: Why software RAID?
  • From: Joel Jaeggli <joelja@xxxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux: Why software RAID?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Interesting RAID checking observations
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid5 reads and cpu
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: 3ware glitches cause softraid rebuilds
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Interesting RAID checking observations - I'm getting it too
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID6 fallen apart
  • From: Ferenc Wagner <wferi@xxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• checkarray: E: no kernel support for parity checks.
  • From: Guillaume Filion <gfk@xxxxxxxxxxx>
• Re: Strange IO stats on RAID1?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Raid5 reads and cpu
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Bodo Thiesen <bothie@xxxxxx>
• Re: Newbie: Kernel panic during RAID1 test & reboot loses one disk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 001 of 4] md: Define backing_dev_info.congested_fn for raid0 and linear
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Strange IO stats on RAID1?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm dynamic multipathing
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Superblock checksum problems
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID-5 recovery
  • From: Neil Brown <neilb@xxxxxxx>
• RAID-0 on the Intel ICH7R chipset and swap configuration...
  • From: "Julio Meca Hansen" <julio28@xxxxxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: "Martin Schröder" <martin@xxxxxxxxxx>
• Re: RAID-5 recovery
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: serious trouble - raid5 won't assemble properly, vgscan sees no volumes - solved
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: RAID6 fallen apart
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: RAID6 fallen apart
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: RAID-5 recovery
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Kernel RAID support
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Kernel RAID support
  • From: David Greaves <david@xxxxxxxxxxxx>
• RAID-5 recovery
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: Kernel RAID support
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Kernel RAID support
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Kernel RAID support
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Bodo Thiesen <bothie@xxxxxx>
• Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• serious trouble - raid5 won't assemble properly, vgscan sees no volumes
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• mdadm dynamic multipathing
  • From: "D. Lane Ware" <dlware@xxxxxxxxxxxx>
• Re: SATA ontrollers and Linux MD
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re[2]: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Ralf Herrmann <Ralf.Herrmann@xxxxxxxxxxxxx>
• RE: SATA ontrollers and Linux MD
  • From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@xxxxxxxxxx>
• Re: SATA ontrollers and Linux MD
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Re: SATA ontrollers and Linux MD
  • From: Alex Davis <alex14641@xxxxxxxxx>
• SATA ontrollers and Linux MD
  • From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@xxxxxxxxxx>
• Strange IO stats on RAID1?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Interesting RAID checking observations - I'm getting it too
  • From: Mark Smith <nanog@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: dean gaudet <dean@xxxxxxxxxx>
• Feature Request/Suggestion - "Drive Linking"
  • From: Neil Bortnak <linux-raid@xxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: [PATCH 002 of 4] md: Define ->congested_fn for raid1, raid10, and multipath
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [PATCH 001 of 4] md: Define backing_dev_info.congested_fn for raid0 and linear
  • From: Andrew Morton <akpm@xxxxxxxx>
• [PATCH 003 of 4] md: Add a ->congested_fn function for raid5/6
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 4] md: Make messages about resync/recovery etc more specific.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 4] md: Define ->congested_fn for raid1, raid10, and multipath
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: Introduction
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Define backing_dev_info.congested_fn for raid0 and linear
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 fallen apart
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 3ware glitches cause softraid rebuilds
  • From: "adam radford" <aradford@xxxxxxxxx>
• Re: 3ware glitches cause softraid rebuilds
  • From: "adam radford" <aradford@xxxxxxxxx>
• 3ware glitches cause softraid rebuilds
  • From: Jim Klimov <klimov@xxxxxxxxxxx>
• Re: Newbie: Kernel panic during RAID1 test & reboot loses one disk
  • From: James Brown <jbrown@xxxxxxxxxx>
• PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Ralf Herrmann <Ralf.Herrmann@xxxxxxxxxxxxx>
• Re: Newbie: Kernel panic during RAID1 test & reboot loses one disk
  • From: James Brown <jbrown@xxxxxxxxxx>
• Raid5 reads and cpu
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Raid5 reads and cpu
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: RAID6 fallen apart
  • From: Ferenc Wagner <wferi@xxxxxxx>
• RE: md: only binds to one mirror after reboot
  • From: "Andreas Pelzner" <Andreas.Pelzner@xxxxxxxxxxxxx>
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: RAID6 fallen apart
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 fallen apart
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• [PATCH] mdadm -As --auto=yes fails if some of the md are already active
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Resize on dirty array?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Question regarding superblocks
  • From: "Norm Legit" <normlegit@xxxxxxxxx>
• RE: md: only binds to one mirror after reboot
  • From: Neil Brown <neilb@xxxxxxx>
• RE: md: only binds to one mirror after reboot
  • From: "Andreas Pelzner" <Andreas.Pelzner@xxxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 write performance
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Neil Brown <neilb@xxxxxxx>
• Re: invalid superblock - *again*
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 fallen apart
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Question regarding superblocks
  • From: Neil Brown <neilb@xxxxxxx>
• Question regarding superblocks
  • From: "Norm Legit" <normlegit@xxxxxxxxx>
• Re: Newbie: Kernel panic during RAID1 test & reboot loses one disk
  • From: Neil Brown <neilb@xxxxxxx>
• RE: md: only binds to one mirror after reboot
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Interesting RAID checking observations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Recommended kernel?
  • From: Neil Brown <neilb@xxxxxxx>
• Recommended kernel?
  • From: Jeff Breidenbach <jeff@xxxxxxx>
• [PATCH 002 of 4] md: Factor out part of raid1d into a separate function
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 4] md: Remove working_disks from raid1 state data
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 4] md: Improve locking around error handling
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Fix issues with referencing rdev in md/raid1
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: Introduction - some revised/reordered patches.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Interesting RAID checking observations
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: md: only binds to one mirror after reboot
  • From: "Andreas Pelzner" <Andreas.Pelzner@xxxxxxxxxxxxx>
• Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Newbie: Kernel panic during RAID1 test & reboot loses one disk
  • From: James Brown <jbrown@xxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH-stable16] Fix a potential NULL dereference in md/raid1
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: linux@xxxxxxxxxxx
• RAID6 fallen apart
  • From: Wagner Ferenc <wferi@xxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: [PATCH 000 of 4] md: Introduction
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 000 of 4] md: Introduction
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: md: only binds to one mirror after reboot
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• md: only binds to one mirror after reboot
  • From: "Andreas Pelzner" <Andreas.Pelzner@xxxxxxxxxxxxx>
• Re: strange raid6 assembly problem
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Mark Lord <lkml@xxxxxx>
• Re: Linux: Why software RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Adam Kropelin <akropel1@xxxxxxxxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Adam Kropelin <akropel1@xxxxxxxxxxxxxxxx>
• strange raid6 assembly problem
  • From: Mickael Marchand <mikmak@xxxxxxxxxxx>
• Re: RAID over Firewire
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• [PATCH 003 of 4] md: new sysfs interface for setting bits in the write-intent-bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 4] md: Remove unnecessary variable x in stripe_to_pdidx().
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 4] md: Fix issues with referencing rdev in md/raid1.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Fix recent breakage of md/raid1 array checking
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: Introduction
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 2] md: replace magic numbers in sb_dirty with well defined bit flags
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 2] md: Avoid backward event updates in md superblock when degraded.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 2] md: Fix a bug with backward event updates.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID over Firewire
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: "Chris Friesen" <cfriesen@xxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Linux: Why software RAID?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID over Firewire
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RAID over Firewire
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: RAID over Firewire
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RAID over Firewire
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID over Firewire
  • From: "Martin Schröder" <martin@xxxxxxxxxx>
• Re: RAID over Firewire
  • From: Gregory Seidman <gsslist+linuxraid@xxxxxxxxxxxxxxxxxx>
• RAID over Firewire
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: invalid superblock - *again*
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID-6 check slow..
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: RAID-6 check slow..
  • From: Neil Brown <neilb@xxxxxxx>
• RAID-6 check slow..
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: smal mdadm 1.5 bug
  • From: Neil Brown <neilb@xxxxxxx>
• Re: invalid superblock - *again*
  • From: Neil Brown <neilb@xxxxxxx>
• Re: invalid superblock - *again*
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• [patch 19/20] MD: Fix a potential NULL dereference in md/raid1
  • From: Greg KH <gregkh@xxxxxxx>
• Re: [stable] [PATCH] Fix a potential NULL dereference in md/raid1
  • From: Greg KH <greg@xxxxxxxxx>
• smal mdadm 1.5 bug
  • From: jwillem <jwillem@xxxxxxxxx>
• Re: invalid superblock - why?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Neil Brown <neilb@xxxxxxx>
• Re: invalid superblock - why?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: remark and RFC
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH-stable16] Fix a potential NULL dereference in md/raid1
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: [PATCH-stable16] Fix a potential NULL dereference in md/raid1
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] Fix a potential NULL dereference in md/raid1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH-stable16] Fix a potential NULL dereference in md/raid1
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• [PATCH-stable16] Fix a potential NULL dereference in md/raid1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 oops, 2.6.16
  • From: Neil Brown <neilb@xxxxxxx>
• invalid superblock - why?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: remark and RFC
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: raid1 oops, 2.6.16
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: raid@xxxxxxxxxxx
• Re: raid5 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx>
• Re: [patch] raid1: allow user to force reads from a specific disk
  • From: Pavel Machek <pavel@xxxxxxx>
• Re: raid5 grow problem
  • From: "舒星" <xshu2006@xxxxxxxxx>
• Re: remark and RFC
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: raid5 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: spurious dots in dmesg when reconstructing arrays
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: spurious dots in dmesg when reconstructing arrays
  • From: Neil Brown <neilb@xxxxxxx>
• spurious dots in dmesg when reconstructing arrays
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: raid5 grow problem
  • From: "舒星" <xshu2006@xxxxxxxxx>
• Re: raid5 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• raid5 grow problem
  • From: "舒星" <xshu2006@xxxxxxxxx>
• Re: remark and RFC
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Failed create or resync - incorrect checksums
  • From: Neil Brown <neilb@xxxxxxx>
• Failed create or resync - incorrect checksums
  • From: "Richard Taylor" <ryo.away@xxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: remark and RFC
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Imaging Mirrored OS Drives
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: remark and RFC
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Imaging Mirrored OS Drives
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Imaging Mirrored OS Drive
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• RE: Imaging Mirrored OS Drives
  • From: raid@xxxxxxxxxxx
• RE: Imaging Mirrored OS Drives
  • From: raid@xxxxxxxxxxx
• Re: Imaging Mirrored OS Drives
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: Is mdadm --create safe for existing arrays ?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: Is mdadm --create safe for existing arrays ?
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Is mdadm --create safe for existing arrays ?
  • From: Peter Greis <peter_greis@xxxxxxxxx>
• Re: remark and RFC
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: remark and RFC
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Mark Hahn <hahn@xxxxxxxxxxxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: remark and RFC
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• remark and RFC
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• RE: Can you IMAGE Mirrored OS Drives?
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• Can you IMAGE Mirrored OS Drives?
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: Kernel panic during resync
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Kernel panic during resync
  • From: Neil Brown <neilb@xxxxxxx>
• RE: RAID-10 and 4 HDDs - how many HDDs can break without loosing data?
  • From: "Andrew Rechenberg Lists" <flux-ml@xxxxxxxxxxxxx>
• Re: Getting 'sync' to flush disk cache?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Getting 'sync' to flush disk cache?
  • From: Jens Axboe <axboe@xxxxxxx>
• Re: Getting 'sync' to flush disk cache?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Getting 'sync' to flush disk cache?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Laurent Lesage <laurent@xxxxxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Laurent Lesage <laurent@xxxxxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Making bootable SATA RAID1 array in Mandriva 2006
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: Neil Brown <neilb@xxxxxxx>
• Making bootable SATA RAID1 array in Mandriva 2006
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: Resize on dirty array?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: raid5 write performance
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: Incative RAID5 (it should be active)
  • From: Jacob Madsen <jacob@xxxxxxxx>
• Incative RAID5 (it should be active)
  • From: Jacob Madsen <jacob@xxxxxxxx>
• Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• [bug?] raid1 integrity checking is broken on 2.6.18-rc4
  • From: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: Resize on dirty array?
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: Resize on dirty array?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: way too high reconstruction speed - bug?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: way too high reconstruction speed - bug?
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• drive is a spare, but I want to make it active - how?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: RAID-10 and 4 HDDs - how many HDDs can break without loosing data?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: drive is a spare, but I want to make it active - how?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Resize on dirty array?
  • From: dean gaudet <dean@xxxxxxxxxx>
• way too high reconstruction speed - bug?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• RAID-10 and 4 HDDs - how many HDDs can break without loosing data?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• RAID-10 and 4 HDDs - how many HDDs can break without loosing data?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• How does linux soft-raid resolve the inconsistency after a system crash?
  • From: liyiming <liyiming@xxxxxxxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Resize on dirty array?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Resize on dirty array?
  • From: James Peverill <jamespev@xxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: Mark Hahn <hahn@xxxxxxxxxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: "Martin Schröder" <martin@xxxxxxxxxx>
• Re: Resize on dirty array?
  • From: James Peverill <jamespev@xxxxxxxxxxxx>
• Re: resize new raid problem
  • From: Luca Berra <bluca@xxxxxxxxxx>
• resize new raid problem
  • From: Serge Torop <tsp@xxxxxxxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: Resize on dirty array?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Neil Brown <neilb@xxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Resize on dirty array?
  • From: James Peverill <jamespev@xxxxxxxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Krzysztof Halasa <khc@xxxxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: modifying degraded raid 1 then re-adding other members is bad
  • From: Neil Brown <neilb@xxxxxxx>
• modifying degraded raid 1 then re-adding other members is bad
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: Resize on dirty array?
  • From: Neil Brown <neilb@xxxxxxx>
• Resize on dirty array?
  • From: James Peverill <jamespev@xxxxxxxxxxxx>
• Re: raid5/lvm setup questions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5/lvm setup questions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: raid5/lvm setup questions
  • From: David Greaves <david@xxxxxxxxxxxx>
• slow resync during mdadm --create
  • From: Mahendra <kuk_m@xxxxxxxxx>
• Re: raid5/lvm setup questions
  • From: Chet McNeill <chet@xxxxxxxxxxx>
• Re: raid5/lvm setup questions
  • From: Shane <shane@xxxxx>
• Re: raid5/lvm setup questions
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [patch] raid1: allow user to force reads from a specific disk
  • From: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx>
• ANNOUNCE: mdadm 2.5.3 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [patch] raid1: allow user to force reads from a specific disk
  • From: Neil Brown <neilb@xxxxxxx>
• [patch] raid1: allow user to force reads from a specific disk
  • From: Chuck Ebbert <76306.1226@xxxxxxxxxxxxxx>
• issue with mdadm ver1 sb and bitmap on x86_64
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: [PATCH 010 of 10] md: Allow the write_mostly flag to be set via sysfs.
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid 5 read performance
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: raid5/lvm setup questions
  • From: "Martin Schröder" <martin@xxxxxxxxxx>
• Re: raid5/lvm setup questions
  • From: Shane <shane@xxxxx>
• Re: raid5/lvm setup questions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: raid 5 read performance
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• raid5/lvm setup questions
  • From: Shane <shane@xxxxx>
• raid1 oops, 2.6.16
  • From: Jason Lunz <lunz@xxxxxxxxxxxx>
• Re: [PATCH 010 of 10] md: Allow the write_mostly flag to be set via sysfs.
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Raid5 bitmap - Bug in bitmap_startwrite()
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• Re: Raid5 bitmap - Bug in bitmap_startwrite()
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Raid5 bitmap - Bug in bitmap_startwrite()
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• Re: [BUG] raid1: barrier retry does not work correctly with write-behind
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [BUG] raid1: barrier retry does not work correctly with write-behind
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [BUG] raid1: barrier retry does not work correctly with write-behind
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Raid5 hardware failure
  • From: Neil Brown <neilb@xxxxxxx>
• [BUG] raid1: barrier retry does not work correctly with write-behind
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Re: Converting Ext3 to Ext3 under RAID 1
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Mdadm problem?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 005 of 9] md: Replace magic numbers in sb_dirty with well defined bit flags
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Converting Ext3 to Ext3 under RAID 1
  • From: Robert Heinzmann <Robert.Heinzmann@xxxxxxx>
• Re: Converting Ext3 to Ext3 under RAID 1
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: Converting Ext3 to Ext3 under RAID 1
  • From: dean gaudet <dean@xxxxxxxxxx>
• Converting Ext3 to Ext3 under RAID 1
  • From: Dan Graham <graham@xxxxxxxxxxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Mdadm problem?
  • From: "A.J.Dawson" <A.J.Dawson@xxxxxxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: [PATCH 004 of 9] md: Factor out part of raid10d into a separate function.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 004 of 9] md: Factor out part of raid10d into a separate function.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 005 of 9] md: Replace magic numbers in sb_dirty with well defined bit flags
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• [PATCH] md: Fix a bug that recently crept into md/linear
  • From: NeilBrown <neilb@xxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Alexandre Oliva <aoliva@xxxxxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Helge Hafting <helgehaf@xxxxxxxxxxxxx>
• Re: [PATCH 005 of 9] md: Replace magic numbers in sb_dirty with well defined bit flags
  • From: Ingo Oeser <ioe-lkml@xxxxxxxxxx>
• Re: [PATCH 0/2] Fix RAID5 + IA64 compile
  • From: Jes Sorensen <jes@xxxxxxx>
• Re: [PATCH 0/2] Fix RAID5 + IA64 compile
  • From: Prarit Bhargava <prarit@xxxxxxxxxx>
• Re: [PATCH 006 of 9] md: Remove the working_disks and failed_disks from raid5 state data.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• [PATCH 003 of 9] md: Factor out part of raid1d into a separate function.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 9] md: Factor out part of raid10d into a separate function.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 9] md: Remove the working_disks and failed_disks from raid5 state data.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 007 of 9] md: Remove 'working_disks' from raid10 state
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 009 of 9] md: Improve locking around error handling.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 008 of 9] md: Remove working_disks from raid1 state data
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 9] md: Replace magic numbers in sb_dirty with well defined bit flags
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 9] md: Fix a comment that is wrong in raid5.h
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 9] md: The scheduled removal of the START_ARRAY ioctl for md
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 9] md: Introduction - assorted cleanup and minor fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: let md auto-detect 128+ raid members, fix potential race condition
  • From: Neil Brown <neilb@xxxxxxx>
• [RFC: 2.6 patch] the scheduled removal of the START_ARRAY ioctl for md
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• [PATCH 2/2] Fix IA64 components
  • From: Prarit Bhargava <prarit@xxxxxxx>
• [PATCH 1/2] Fix RAID5 components
  • From: Prarit Bhargava <prarit@xxxxxxx>
• [PATCH 0/2] Fix RAID5 + IA64 compile
  • From: Prarit Bhargava <prarit@xxxxxxx>
• Re: Weird blocks at fsync() calls using md
  • From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx>
• Linux software raid: Status and plan ?
  • From: Robert Haas <rha@xxxxxxxxxxxxxx>
• Re: Weird blocks at fsync() calls using md
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Weird blocks at fsync() calls using md
  • From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx>
• Re: Weird blocks at fsync() calls using md
  • From: Neil Brown <neilb@xxxxxxx>
• Weird blocks at fsync() calls using md
  • From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx>
• Re: [PATCH 001 of 006] raid5: Move write operations to a work queue
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [PATCH 001 of 006] raid5: Move write operations to a work queue
  • From: Yuri Tikhonov <yur_t@xxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: Grub vs Lilo
  • From: Simen Thoresen <simentt@xxxxxxxxxxxxx>
• Grub vs Lilo
  • From: Lewis Shobbrook <mylists@xxxxxxxxxxxxxxx>
• Re: ICH7R "strip" size
  • From: Mark Hahn <hahn@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• ICH7R "strip" size
  • From: Jeff Woods <Kazrak+kernel@xxxxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: host based mirror distance in a fc-based SAN environment
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Grub vs Lilo
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Grub vs Lilo
  • From: Bernd Rieke <bernd@xxxxxx>
• Re: Grub vs Lilo
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Grub vs Lilo
  • From: Jason Lunz <lunz@xxxxxxxxxxxx>
• Re: host based mirror distance in a fc-based SAN environment
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Grub vs Lilo
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Grub vs Lilo
  • From: Lewis Shobbrook <mylists@xxxxxxxxxxxxxxx>
• host based mirror distance in a fc-based SAN environment
  • From: "Stefan Majer" <stefan@xxxxxxxxxxxxx>
• FIXED : brute-force my RAID 5 - just some fsck errors..
  • From: Sevrin Robstad <quack@xxxxxxxxx>
• write back cache and barrier questions
  • From: marco <thedrop@xxxxxxxxxxx>
• Re: [PATCH] md: new bitmap sysfs interface
  • From: dave rientjes <rientjes@xxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Drives of same model in RAID 1/10 ?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• [PATCH] md: new bitmap sysfs interface
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Drives of same model in RAID 1/10 ?
  • From: hahn@xxxxxxxxxxxxxxxxxxx
• Re: Drives of same model in RAID 1/10 ?
  • From: "Jeff Breidenbach" <breidenbach@xxxxxxxxx>
• Re: Drives of same model in RAID 1/10 ?
  • From: Andy Smith <andy@xxxxxxxxxx>
• Re: Dell PowerEdge Expandable RAID Controller 4e/Di
  • From: "Pieter Steyn" <pieterste@xxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Drives of same model in RAID 1/10 ?
  • From: Mark Hellman <markhellman@xxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: I travelled twice in the past !!
  • From: hahn@xxxxxxxxxxxxxxxxxxx
• Dell PowerEdge Expandable RAID Controller 4e/Di
  • From: "Pieter Steyn" <pieterste@xxxxxxxxx>
• I travelled twice in the past !!
  • From: Edouard Gaulué <edouard.gaulue@xxxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Neil Brown <neilb@xxxxxxx>
• In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• raid from2.6 kernel not recognized under 2.4
  • From: "Daniel J. Priem" <daniel@xxxxxxxxxxx>
• Re: md reports: unknown partition table - fixed.
  • From: Nix <nix@xxxxxxxxxxxxx>
• Better Success, world-sobered
  • From: "Kimberley Mcclure" <KimberleyMcclure@xxxxxxxx>
• Re: Raid5 Reshape Status + xfs_growfs = Success! (2.6.17.3)
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• [RTLWS8-CFP] Eighth Real-Time Linux Workshop 2nd CFP
  • From: mcguire@xxxxxxxxxx
• Re: which disk the the one that data is on?
  • From: Shai <shaibn@xxxxxxxxx>
• Serious XFS bug in 2.6.17 kernels - FYI
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Megaraid, howto?
  • From: "Pieter Steyn" <pieterste@xxxxxxxxx>
• Re: Is it possible to recover data after resync?
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Megaraid, howto?
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• Slightly OT - Dell PERC 5 card...
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Megaraid, howto?
  • From: "Pieter Steyn" <pieterste@xxxxxxxxx>
• Re: Is it possible to recover data after resync?
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Is it possible to recover data after resync?
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Is it possible to recover data after resync?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Is it possible to recover data after resync?
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Is it possible to recover data after resync?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md reports: unknown partition table - fixed.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: which disk the the one that data is on?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5.h documentation
  • From: Neil Brown <neilb@xxxxxxx>
• Re: XFS and write barrier
  • From: Neil Brown <neilb@xxxxxxx>
• Is it possible to recover data after resync?
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: which disk the the one that data is on?
  • From: Janos Farkas <chexum+dev@xxxxxxxxx>
• raid5.h documentation
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: which disk the the one that data is on?
  • From: Shai <shaibn@xxxxxxxxx>
• Re: only 4 spares and no access to my data
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: issue with internal bitmaps
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: Sevrin Robstad <quack@xxxxxxxxx>
• Re: md reports: unknown partition table - fixed.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: XFS and write barrier
  • From: David Chinner <dgc@xxxxxxx>
• Re: mdadm -X bitmap status off by 2^16
  • From: Janos Farkas <chexum+dev@xxxxxxxxx>
• md reports: unknown partition table
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: mdadm -X bitmap status off by 2^16
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Raid and LVM and LILO
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: issue with internal bitmaps
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: which disk the the one that data is on?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid and LVM and LILO
  • From: Du <eduardo@xxxxxxxxxxxxxx>
• Re: Raid and LVM and LILO
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: [PATCH] enable auto=yes by default when using udev
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: which disk the the one that data is on?
  • From: Neil Brown <neilb@xxxxxxx>
• read-ahead cache on indiv. raid members and entire md device
  • From: Roy Waldspurger <rlists@xxxxxxxxxxxxxxxxx>
• Re: which disk the the one that data is on?
  • From: Shai <shaibn@xxxxxxxxx>
• Re: Still can't get md arrays that were started from an initrd to shutdown
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: Still can't get md arrays that were started from an initrd to shutdown
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: which disk the the one that data is on?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: XFS and write barrier
  • From: Neil Brown <neilb@xxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• which disk the the one that data is on?
  • From: Shai <shaibn@xxxxxxxxx>
• Re: XFS and write barrier
  • From: Nathan Scott <nathans@xxxxxxx>
• mdadm -X bitmap status off by 2^16
  • From: Janos Farkas <chexum+dev@xxxxxxxxx>
• Re: Problem with --manage
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Problem with --manage
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Where is MD Device Layer
  • From: linuxmania.lizhi@xxxxxxxxx
• Re: Problem with --manage
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Can't add disk to failed raid array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] enable auto=yes by default when using udev
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Still can't get md arrays that were started from an initrd to shutdown
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Where is MD Device Layer
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Booting issue - rebooting also
  • From: Neil Brown <neilb@xxxxxxx>
• Re: PLEASE HELP ... raid5 array degraded ...
  • From: Neil Brown <neilb@xxxxxxx>
• Re: only 4 spares and no access to my data
  • From: Neil Brown <neilb@xxxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Test feedback 2.6.17.4+libata-tj-stable (EH, hotplug)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Problem with 3xRAID1 to RAID 0
  • From: Neil Brown <neilb@xxxxxxx>
• Re: SWRaid Wiki
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Raid5 Reshape Status + xfs_growfs = Success! (2.6.17.3)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Kernel 2.6.17 and RAID5 Grow Problem (critical section backup)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Mounting array was read write for about 3 minutes, then Read-only file system error
  • From: "David Rientjes" <rientjes@xxxxxxxxxx>
• Re: zeroing old superblocks & upgrading...
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Mounting array was read write for about 3 minutes, then Read-only file system error
  • From: Neil Brown <neilb@xxxxxxx>
• Raid and LVM and LILO
  • From: Du <eduardo@xxxxxxxxxxxxxx>
• Re: Still can't get md arrays that were started from an initrd to shutdown
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: second controller: what will my discs be called, and does it matter?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: trying to "brute-force" my RAID 5...
  • From: Sevrin Robstad <quack@xxxxxxxxx>
• Still can't get md arrays that were started from an initrd to shutdown
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• troubleshooting PNY S-cure
  • From: "whc86 (sent by Nabble.com)" <lists@xxxxxxxxxx>