Linux RAID Storage Date Index

• Thread Index

• [PATCH 2/8] md_getgeo(): Move comment to proper position.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 1/8] md_ioctl(): Fix misleading indentation.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 3/8] do_md_run(): Fix misleading error message.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 4/8] sync_speed_show(): Trivial cleanups.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 5/8] Fix typo in array_state comment.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 8/8] Kill unused parameter mddev in md_new_event_inintr().
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 6/8] Fix a typo in the comment to cmd_match().
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 7/8] sb_equal(): Fix misleading printk.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [Patch 0/8] simple md.c cleanups
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [Fwd: Re: mdadm: spare rebuilding]
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.26-rc8 deadlock: RAID code?
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: md devices disappearing on system reboot
  • From: thomas62186218@xxxxxxx
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Robert Hancock <hancockr@xxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Robert Hancock <hancockr@xxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Robert Hancock <hancockr@xxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: "Jon Nelson" <jnelson@xxxxxxxxxxx>
• Lots of con-current I/O = resets SATA link? (2.6.25.10)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.26-rc8 deadlock: RAID code?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• 2.6.26-rc8 deadlock: RAID code?
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
  • From: Robert Hancock <hancockr@xxxxxxx>
• Re: Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Grow a RAID-10
  • From: "Daniel L. Miller" <dmiller@xxxxxxxxx>
• Re: Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: "raid" versions of hard drives for software raid?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: "raid" versions of hard drives for software raid?
  • From: Dan Christensen <jdc@xxxxxx>
• Re: new bottleneck section in wiki
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Grow a RAID-10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Grow a RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [Fwd: Re: mdadm: spare rebuilding]
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Grow a RAID-10
  • From: "Daniel L. Miller" <dmiller@xxxxxxxxx>
• Re: Grow a RAID-10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• [PULL-REQUEST] md bugfixes for 2.6.26
  • From: Neil Brown <neilb@xxxxxxx>
• RE: new bottleneck section in wiki
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Grow a RAID-10
  • From: "Daniel L. Miller" <dmiller@xxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: "raid" versions of hard drives for software raid?
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: "raid" versions of hard drives for software raid?
  • From: Dan Christensen <jdc@xxxxxx>
• Re: "raid" versions of hard drives for software raid?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: "raid" versions of hard drives for software raid?
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: Metadata upgradable?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• "raid" versions of hard drives for software raid?
  • From: Dan Christensen <jdc@xxxxxx>
• Re: Metadata upgradable?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld J?rn Simonsen <keld@xxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld J?rn Simonsen <keld@xxxxxxxx>
• Re: new bottleneck section in wiki
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld J?rn Simonsen <keld@xxxxxxxx>
• Metadata upgradable?
  • From: Oliver <oliver@xxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• RE: new bottleneck section in wiki
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• RE: new bottleneck section in wiki
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: new bottleneck section in wiki
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: md devices disappearing on system reboot
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• new bottleneck section in wiki
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: md man page
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: md man page
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: md man page
  • From: "Randy.Dunlap" <rdunlap@xxxxxxxxxxxx>
• md man page
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Michael Bussmann <bus@xxxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Mike McCarthy <mike@xxxxxxxx>
• md devices disappearing on system reboot
  • From: thomas62186218@xxxxxxx
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 001 of 29] md: Ensure interrupted recovery completed properly (v1 metadata plus bitmap)
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: Whole drives or Only partitions for mdadm software RAIDs?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: Whole drives or Only partitions for mdadm software RAIDs?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Whole drives or Only partitions for mdadm software RAIDs?
  • From: thomas62186218@xxxxxxx
• Re: Whole drives or Only partitions for mdadm software RAIDs?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Whole drives or Only partitions for mdadm software RAIDs?
  • From: thomas62186218@xxxxxxx
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Mike McCarthy <mike@xxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Michael Bussmann <bus@xxxxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Mike McCarthy <mike@xxxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: [PATCH 008 of 29] md: Close race in md_probe
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: raid5 recovery dramas.
  • From: Mark Davies <mark@xxxxxxxxxxxxxxxxxxx>
• Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: mdadm: spare rebuilding
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Suspected corruption on ACID databases due to no barrier support in ext3 on software raid-5 and hard resets
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: [PATCH 018 of 29] md: Support changing rdev size on running arrays.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 008 of 29] md: Close race in md_probe
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software RAID1 deadlock in 2.6.25 kernels
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 recovery dramas.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 018 of 29] md: Support changing rdev size on running arrays.
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 008 of 29] md: Close race in md_probe
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: raid5 recovery dramas.
  • From: Mark Davies <mark@xxxxxxxxxxxxxxxxxxx>
• Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 recovery dramas.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm: spare rebuilding
  • From: Neil Brown <neilb@xxxxxxx>
• Storing array run-time options in mdadm.conf
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• [PATCH 029 of 29] md: md: rationalize raid5 function names
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 028 of 29] md: md: handle operation chaining in raid5_run_ops
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 027 of 29] md: md: replace R5_WantPrexor with R5_WantDrain, add 'prexor' reconstruct_states
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 026 of 29] md: md: replace STRIPE_OP_{BIODRAIN,PREXOR,POSTXOR} with 'reconstruct_states'
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 025 of 29] md: md: replace STRIPE_OP_COMPUTE_BLK with STRIPE_COMPUTE_RUN
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 024 of 29] md: md: replace STRIPE_OP_BIOFILL with STRIPE_BIOFILL_RUN
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 023 of 29] md: md: replace STRIPE_OP_CHECK with 'check_states'
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 022 of 29] md: md: unify raid5/6 i/o submission
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 021 of 29] md: md: use stripe_head_state in ops_run_io()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 020 of 29] md: md: kill STRIPE_OP_IO flag
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 019 of 29] md: md: kill STRIPE_OP_MOD_DMA in raid5 offload
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 018 of 29] md: Support changing rdev size on running arrays.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 017 of 29] md: Make sure all changes to md/dev-XX/state are notified
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 016 of 29] md: Make sure all changes to md/degraded are notified.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 015 of 29] md: Make sure all changes to md/sync_action are notified.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 014 of 29] md: Make sure all changes to md/array_state are notified.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 013 of 29] md: Don't reject HOT_REMOVE_DISK request for an array that is not yet started.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 012 of 29] md: rationalise return value for ->hot_add_disk method.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 011 of 29] md: Support adding a spare to a live md array with external metadata.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 010 of 29] md: Enable setting of 'offset' and 'size' of a hot-added spare.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 009 of 29] md: Don't try to make md arrays dirty if that is not meaningful.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 008 of 29] md: Close race in md_probe
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 007 of 29] md: Allow setting start point for requested check/repair
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 29] md: Improve setting of "events_cleared" for write-intent bitmaps.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 29] md: use bio_endio instead of a call to bi_end_io
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 29] md: linear: correct disk numbering error check
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 29] md: Fix error paths if md_probe fails.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 29] md: Don't acknowlege that stripe-expand is complete until it really is.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 29] md: Ensure interrupted recovery completed properly (v1 metadata plus bitmap)
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 29] md: Introduction : patchbomb for 2.6.27 merge window
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] disable queue flag test in barrier check
  • From: Timothy Shimmin <tes@xxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: [PATCH] disable queue flag test in barrier check
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: [PATCH] disable queue flag test in barrier check
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• RE: [PATCH] disable queue flag test in barrier check
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: raid5 recovery dramas.
  • From: Mark Davies <mark@xxxxxxxxxxxxxxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Slowww raid check (raid10, f2)
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: raid5 recovery dramas.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: [PATCH] disable queue flag test in barrier check
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Slowww raid check (raid10, f2)
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: [PATCH] disable queue flag test in barrier check
  • From: Timothy Shimmin <tes@xxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• [PATCH] disable queue flag test in barrier check
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: raid5 recovery dramas.
  • From: Mark Davies <mark@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] sysfs superblock read oops
  • From: Neil Brown <neilb@xxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• RE: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: "Jon Nelson" <jnelson@xxxxxxxxxxx>
• Re: raid10,f2 degraded read speed
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• In reply to the scheduler performance across md/software RAID.
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• How to avoid complete rebuild of RAID 6 array (6/8 active devices)
  • From: Dave Moon <p.b.w.tortilla@xxxxxxxxx>
• Re: md raid1 passes barriers, but xfs doesn't use them?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• [PATCH] sysfs superblock read oops
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: md raid1 passes barriers, but xfs doesn't use them?
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• mdadm: spare rebuilding
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: md/Software RAID ATA/RAID (software RAID)
  • From: Jin Suh <jinssuh@xxxxxxxxx>
• md/Software RAID ATA/RAID (software RAID)
  • From: Jin Suh <jinssuh@xxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: End to end SMART to RAID repair
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: [PATCH 2/2] use bio_endio instead of a call to bi_end_io
  • From: Neil Brown <neilb@xxxxxxx>
• raid5 recovery dramas.
  • From: Mark Davies <mark@xxxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] use bio_endio instead of a call to bi_end_io
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Neil Brown <neilb@xxxxxxx>
• md raid1 passes barriers, but xfs doesn't use them?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: End to end SMART to RAID repair
  • From: Arthur Britto <ahbritto@xxxxxxx>
• Re: Trouble increasing md component size
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Why can't I stop these arrays? PATCH
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Why can't I stop these arrays? PATCH
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• Re: Why can't I stop these arrays?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Why can't I stop these arrays?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Why can't I stop these arrays?
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: Bill Davidsen <davidsen@xxxxxxx>
• INFO messages during resync
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: External bitmap disappears
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: mdadm: making a spare actie
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: External bitmap disappears
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: External bitmap disappears
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• External bitmap disappears
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: mdadm: making a spare actie
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: mdadm: making a spare actie
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: mdadm: making a spare actie
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: mdadm: making a spare actie
  • From: Neil Brown <neilb@xxxxxxx>
• mdadm: making a spare actie
  • From: Jon Buckingham <jbuckingham@xxxxxxxxxxxxxxxx>
• Re: Wierd critical node problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid10: no raid0 support?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: resync=PENDING, interrupted RAID5 grow will not automatically reconstruct
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] Segfault with --assemble --force
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Trouble increasing md component size
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• [PATCH] Segfault with --assemble --force
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Trouble increasing md component size
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Trouble increasing md component size
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• resync=PENDING, interrupted RAID5 grow will not automatically reconstruct
  • From: Jesse Molina <jmolina@xxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Confused about UUID mounting and mirrors
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• raid10,f2 degraded read speed
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RE: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: <jmolina@xxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: Jesse Molina <jmolina@xxxxxxxx>
• Re: [PATCH] linear: correct disk numbering error check
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: Confused about UUID mounting and mirrors
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Confused about UUID mounting and mirrors
  • From: "michael@xxxxxxxxxxx" <michael@xxxxxxxxxxx>
• Re: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: Jesse Molina <jmolina@xxxxxxxx>
• Re: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: "Ken Drummond" <ken.drummond@xxxxxxxxxxxxxxx>
• RE: Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: <jmolina@xxxxxxxx>
• Failed RAID5 array grow after reboot interruption; mdadm: Failed to restore critical section for reshape, sorry.
  • From: <jmolina@xxxxxxxx>
• Re: What do these SATA errors mean / kernel 2.6.25.6 (DRDY ERR/ICRC ABRT)
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: need some help very strange behavior mdadm writes data to non raid disk?
  • From: Jelle de Jong <jelledejong@xxxxxxxxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: "Sean Hildebrand" <silverwraithii@xxxxxxxxx>
• need some help very strange behavior mdadm writes data to non raid disk?
  • From: Jelle de Jong <jelledejong@xxxxxxxxxxxxx>
• Re: Weird corruptions read error.
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Weird corruptions read error.
  • From: Karl Dubois <karl-2.dubois@xxxxxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: "Sean Hildebrand" <silverwraithii@xxxxxxxxx>
• Re: Rebuilding an array with a corrupt disk.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Rebuilding an array with a corrupt disk.
  • From: "Sean Hildebrand" <silverwraithii@xxxxxxxxx>
• [PATCH] linear: correct disk numbering error check
  • From: "Nikanth Karthikesan" <knikanth@xxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Neil Brown <neilb@xxxxxxx>
• Re: What do these SATA errors mean / kernel 2.6.25.6 (DRDY ERR/ICRC ABRT)
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Nat Makarevitch <nat@xxxxxxxxxxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: What do these SATA errors mean / kernel 2.6.25.6 (DRDY ERR/ICRC ABRT)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Proper partition type for components with V1.x superblocks?
  • From: David Greaves <david@xxxxxxxxxxxx>
• What do these SATA errors mean / kernel 2.6.25.6 (DRDY ERR/ICRC ABRT)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Proper partition type for components with V1.x superblocks?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: Wierd critical node problem
  • From: Wayne Gemmell <wayne@xxxxxxxxxxxxxxxx>
• Re: Wierd critical node problem
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Wierd critical node problem
  • From: Wayne Gemmell <wayne@xxxxxxxxxxxxxxxx>
• Re: Wierd critical node problem
  • From: "NeilBrown" <neilb@xxxxxxx>
• Wierd critical node problem
  • From: Wayne Gemmell <wayne@xxxxxxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• raid10: no raid0 support?
  • From: "Alan D. Brunelle" <Alan.Brunelle@xxxxxx>
• [SOLVED] Re: Rebuild after a drive replacement
  • From: Gavin Hamill <gdh@xxxxxxxxxxxxxx>
• Re: RAID1 over aoe devices freezes cp-procs on failure of one aoe device
  • From: "Ed L. Cashin" <ecashin@xxxxxxxxxx>
• RE: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• RE: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• [ANNOUNCE] Einarc - universal RAID management/monitoring tool - v1.2 released
  • From: Mikhail Yakshin <greycat@xxxxxxxxxxxx>
• Re: Rebuild after a drive replacement
  • From: Gavin Hamill <gdh@xxxxxxxxxxxxxx>
• Re: Rebuild after a drive replacement
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Rebuild after a drive replacement
  • From: Gavin Hamill <gdh@xxxxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: thomas62186218@xxxxxxx
• Reallocating sd device
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Question on hotplug SATA controllers
  • From: "John Bridges" <john.bridges@xxxxxxxxx>
• Re: Rebuild after a drive replacement
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Rebuild after a drive replacement
  • From: David Greaves <david@xxxxxxxxxxxx>
• Rebuild after a drive replacement
  • From: Gavin Hamill <gdh@xxxxxxxxxxxxxx>
• Re: Change disk problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Change disk problem
  • From: "Jon Lurås" <jon@xxxxxxxxxxxx>
• Re: Change disk problem
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Change disk problem
  • From: David Greaves <david@xxxxxxxxxxxx>
• Change disk problem
  • From: "Jon Lurås" <jon@xxxxxxxxxxxx>
• Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• how can I access a disk marked as failed
  • From: robert.koeppl@xxxxxxxxx
• RAID-5 and the mysterious disappearing drive
  • From: Ben Martin <monkeyiq@xxxxxxxxxxxxxxxxxxxxx>
• RE: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Question on hotplug SATA controllers
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Question on hotplug SATA controllers
  • From: "John Bridges" <john.bridges@xxxxxxxxx>
• Question on hotplug SATA controllers
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RE: Problem Growing Raid 5 Array - Help Needed!
  • From: "Jeremy Leigh" <jeremy.leigh@xxxxxxxxx>
• Re: RAID1 over aoe devices freezes cp-procs on failure of one aoe device
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: RAID1 over aoe devices freezes cp-procs on failure of one aoe device
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• ANNOUNCE: mdadm 2.6.7 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• RAID1 over aoe devices freezes cp-procs on failure of one aoe device
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: boot time autoassembly: how come it works?
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: boot time autoassembly: how come it works?
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: boot time autoassembly: how come it works?
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• boot time autoassembly: how come it works?
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: David Greaves <david@xxxxxxxxxxxx>
• RAID5 losing initial synchronization on restart when one disk is spare
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: After partition resize, RAID5 array does not assemble on boot
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: Software RAID 6 initial sync very slow
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• Re: Problem Growing Raid 5 Array - Help Needed!
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: Problem Growing Raid 5 Array - Help Needed!
  • From: "Jeremy Leigh" <jeremy.leigh@xxxxxxxxx>
• After partition resize, RAID5 array does not assemble on boot
  • From: Jules Bean <jules@xxxxxxxxxxxxxxx>
• Re: Software RAID 6 initial sync very slow
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software RAID 6 initial sync very slow
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• md_thread and kjournald race w/ raid1 on 2-way x86
  • From: "Srinivas Murthy" <codevana@xxxxxxxxx>
• Re: Software RAID 6 initial sync very slow
  • From: thomas62186218@xxxxxxx
• Re: Awful Raid10,f2 performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Problem Growing Raid 5 Array - Help Needed!
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Awful Raid10,f2 performance
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Awful Raid10,f2 performance
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Problem Growing Raid 5 Array - Help Needed!
  • From: "Jeremy Leigh" <jeremy.leigh@xxxxxxxxx>
• Awful Raid10,f2 performance
  • From: "Jon Nelson" <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Software RAID 6 initial sync very slow
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mdadm raid10 performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: mdadm raid10 performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• mdadm raid10 performance
  • From: "Марк Коренберг" <socketpair@xxxxxxxxx>
• Re: Software RAID 6 initial sync very slow
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
  • From: Willy Tarreau <w@xxxxxx>
• Software RAID 6 initial sync very slow
  • From: thomas62186218@xxxxxxx
• Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: 2.6.25.x: Wrong CPU frequency (cpufreq table) with p4-clockmod
  • From: Guntsche Michael <mike@xxxxxxxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: Tony Germano <tony_germano@xxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Known good eSATA CardBus controllers
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: How to force stopping an array`
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Known good eSATA CardBus controllers
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: Known good eSATA CardBus controllers
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• Known good eSATA CardBus controllers
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Chris Snook <csnook@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Chris Snook <csnook@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: "Jens Bäckman" <jens.backman@xxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Chris Snook <csnook@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: How to force stopping an array`
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: aoe disk not recognized as part of raid - solution!
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 003 of 3] md: Do not compute parity unless it is on a failed drive
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 3] md: fix uninitialized use of mddev->recovery_wait
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 3] md: md: fix prexor vs sync_request race
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 3] md: raid5 patches suitable for 2.6.26 and -stable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• split off + mount a partitionless RAID1 device?
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: "Grant Grundler" <grundler@xxxxxxxxxx>
• Re: How to force stopping an array`
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: How to force stopping an array`
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: How to force stopping an array`
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• RE: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: Keeping debian from auto-assembling
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: Andre Tomt <andre@xxxxxxxx>
• Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: Mark Lord <liml@xxxxxx>
• Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RFI for 2.6.25.5 : Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: "Chris Green" <cgreen@xxxxxxxxxxxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RFI for 2.6.25.5 : Re: Regression- XFS won't mount on partitioned md array
  • From: Willy Tarreau <w@xxxxxx>
• RFI for 2.6.25.5 : Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: "Chris Green" <cgreen@xxxxxxxxxxxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• ESATA discs spindown. Can mdadm handle this?
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: Recreating undamaged RAID5
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: Tony Germano <tony_germano@xxxxxxxxxxx>
• Recreating undamaged RAID5
  • From: Anders Johansson <ajh@xxxxxx>
• RE: Proposal: non-striping RAID4
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Tony Germano <tony_germano@xxxxxxxxxxx>
• RE: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• RAID-6, dmcrypt, lvm, ext3
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: Wipe failed RAID-5 disk before RMA
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Wipe failed RAID-5 disk before RMA
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: INFO: task md2_resync:7950 blocked for more than 120 seconds
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Re: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Re: Re: Two Drive Failure on RAID-5
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• RE: Re: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Re: Two Drive Failure on RAID-5
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: Wipe failed RAID-5 disk before RMA
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: Wipe failed RAID-5 disk before RMA
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Wipe failed RAID-5 disk before RMA
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• RE: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Neil Brown <neilb@xxxxxxx>
• ANNOUNCE: mdadm 2.6.6 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: howto and faq
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm 2.6.5 compile issue
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 010 of 10] md: Restart recovery cleanly after device failure.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 009 of 10] md: Allow parallel resync of md-devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 008 of 10] md: Improve setting of "events_cleared" for write-intent bitmaps.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 007 of 10] md: notify userspace on 'stop' events
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 10] md: Notify userspace on 'write-pending' changes to array_state
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 10] md: raid1: Fix restoration of bio between failed read and write.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 10] md: md: raid5 rate limit error printk
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 10] md: kill file_path wrapper
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 10] md: proper extern for mdp_major
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 10] md: Fix possible oops when removing a bitmap from an active array
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 10] md: Various bug fixes and small improvements for md in 2.6.26-rc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [OT] Re: questions about softraid limitations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: questions about softraid limitations
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• RE: questions about softraid limitations
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• RE: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• mdadm 2.6.5 compile issue
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: "Oliver Pinter" <oliver.pntr@xxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• [OT] Re: questions about softraid limitations
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: questions about softraid limitations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: Twigathy <twigathy@xxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: David Greaves <david@xxxxxxxxxxxx>
• ANNOUNCE: mdadm 2.6.5 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Linux Software RAID /sysfs repair issue
  • From: Neil Brown <neilb@xxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <djani22@xxxxxxxxxxxx>
• Re:
  • From: David Greaves <david@xxxxxxxxxxxx>
• [no subject]
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• questions about softraid limitations
  • From: "Janos Haar" <djani22@xxxxxxxxxxxx>
• Linux Software RAID /sysfs repair issue
  • From: "Fairbanks, David" <David.Fairbanks@xxxxxxxxxxx>
• Re: Help recovering from failed disk on RAID 6
  • From: "Pascal Charest" <pascal.charest@xxxxxxxxx>
• RE: Help recovering from failed disk on RAID 6
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Help recovering from failed disk on RAID 6
  • From: "Steve Fairbairn" <steve@xxxxxxxxxxxxxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] Remove blkdev warning triggered by using md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Bas van Schaik <bas@xxxxxxxx>
• [no subject]
  • From: "me at tmr.com" <tmrbill@xxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [PATCH] md: kill file_path wrapper
  • From: Neil Brown <neilb@xxxxxxx>
• Re: howto and faq
  • From: Neil Brown <neilb@xxxxxxx>
• Re: howto and faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: howto and faq
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: linux raid faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: linux raid faq
  • From: Janek Kozicki <janek_listy@xxxxx>
• Re: What to do when repair does not fix mismatch_cnt to 0 (2.6.25.1)?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• What to do when repair does not fix mismatch_cnt to 0 (2.6.25.1)?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: howto and faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: linux raid faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Q. Recovering concatenated array from disk images?
  • From: Graham King <linuxraid@xxxxxxxxxxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [PATCH] md: kill file_path wrapper
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: partitioned mirror vs. mirrors of partitions?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: mdadm feature suggestion
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: michael@xxxxxxxxx
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• partitioned mirror vs. mirrors of partitions?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: "Greg Cormier" <gcormier@xxxxxxxxx>
• Re: Autostarting arrays with V1 metadata
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Andrew Farley <andrew@xxxxxxxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Booting off of RAID10 versus RAID1
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: Autostarting arrays with V1 metadata
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Multipath behavior
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Autostarting arrays with V1 metadata
  • From: Neil Brown <neilb@xxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Autostarting arrays with V1 metadata
  • From: Ben Winslow <rain@xxxxxxxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: "Hardy Garten" <mailingliste@xxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: Marc MERLIN <marc_news@xxxxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: [RFC PATCH] md: towards a replacement for the raid5 STRIPE_OP_* flags
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: Marc MERLIN <marc_news@xxxxxxxxxxx>
• Re: Resize / file system and create /home in existing raid 1
  • From: "Tiago Pinheiro" <tpinheiro@xxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Russ Hammer <russ@xxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Resize / file system and create /home in existing raid 1
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• Re: how to recreate a raid5 array with n-1 drives?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• how to recreate a raid5 array with n-1 drives?
  • From: Marc MERLIN <marc_news@xxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: Federico <undicizeri@xxxxxxxxx>
• Re: [RFC PATCH] md: towards a replacement for the raid5 STRIPE_OP_* flags
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm feature suggestion
  • From: Neil Brown <neilb@xxxxxxx>
• [RFC PATCH] md: towards a replacement for the raid5 STRIPE_OP_* flags
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Resize / file system and create /home in existing raid 1
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Resize / file system and create /home in existing raid 1
  • From: "Tiago Pinheiro" <tpinheiro@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Joao Luis Meloni Assirati <assirati@xxxxxxxxxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: non-fresh from initrd, all fine when assembling manually
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• Re: Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: Federico <undicizeri@xxxxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Lars Täuber <taeuber@xxxxxxx>
• mdadm raid1 stops to work after kernel panic
  • From: Federico <undicizeri@xxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: "Greg Cormier" <gcormier@xxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Joao Luis Meloni Assirati <assirati@xxxxxxxxxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• RE: Sleeping hard drives in an array?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• RE: Sleeping hard drives in an array?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: berk walker <berk@xxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• [PATCH] md: fix raid5 'repair' operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Russ Hammer <russ@xxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• non-fresh from initrd, all fine when assembling manually
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: Michael Tokarev <mjt@xxxxxxxxxx>