Linux RAID Storage Date Index

• Thread Index

• Re: [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [-mm PATCH 2/2] raid5: use stripe_queues to prioritize the "most deserving" requests (take3)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [-mm PATCH 1/2] raid5: add the stripe_queue object for tracking raid io requests (take2)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Raid array is not automatically detected.
  • From: Bryan Christ <bryan.christ@xxxxxx>
• Re: Re-building an array
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3ware 9650 tips
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3ware 9650 tips
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• Re-building an array
  • From: mail <lists@xxxxxxxxx>
• Re: 3ware 9650 tips
  • From: Jon Collette <jon@xxxxxxxxxx>
• Re: 3ware 9650 tips
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm create to existing raid5
  • From: Jon Collette <jon@xxxxxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• [GIT PULL] ioat fixes, raid5 acceleration, and the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: mdadm create to existing raid5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: mdadm create to existing raid5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Man page patch (manage mode options clarification)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Man page patch (bold font for option names in MISC MODE section)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RE: mdadm create to existing raid5
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• mdadm create to existing raid5
  • From: Jon Collette <jon@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Valdis.Kletnieks@xxxxxx
• Re: Linux Software RAID is really RAID?
  • From: "Johny Mail list" <maillist.johny@xxxxxxxxx>
• adding drives / growing RAID-10?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Resizing RAID1 on top of LVM2 LVs
  • From: "Grzegorz Nosek" <grzegorz.nosek@xxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Valdis.Kletnieks@xxxxxx
• Re: Software based SATA RAID-5 expandable arrays?
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Ric Wheeler <ric@xxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Fwd: Re: RAID performance is not too well....
  • From: Rogier Wolff <R.E.Wolff@xxxxxxxxxxxx>
• Re: Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: nested raid possible?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 recover after a 2 disk failure
  • From: Frank Jenkins <fjenkins873@xxxxxxxxx>
• md looping on recovery of raid1 array
  • From: Ryan_MichaelS@xxxxxxx
• Re: nested raid possible?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: nested raid possible?
  • From: Simon Valiquette <v.simon@xxxxxxxx>
• nested raid possible?
  • From: turbo@xxxxxxxxxx
• Re: [RFC PATCH 0/2] raid5: 65% sequential-write performance improvement, stripe-queue take2
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Dirty flag during resync
  • From: "Vincze, Tamas" <vincze@xxxxxxx>
• Re: Expanding a RAID-5 in use from 3 disks to 6 disks
  • From: "David Rees" <drees76@xxxxxxxxx>
• Expanding a RAID-5 in use from 3 disks to 6 disks
  • From: acostoya <adrian@xxxxxxxxxxx>
• Dead RAID5!
  • From: John Rowe <rowe@xxxxxxxxxxxxx>
• Re: AW: The array is functioning normally (?)
  • From: Simon <simon.xhz@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• AW: The array is functioning normally (?)
  • From: "Heinzmann, Robert" <Heinzmann@xxxxxxxxxxxxx>
• The array is functioning normally (?)
  • From: Simon <simon.xhz@xxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: Mark Lord <liml@xxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• I/O is retried forever if last disk in a md device fails
  • From: "Heinzmann, Robert" <Heinzmann@xxxxxxxxxxxxx>
• Re: Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFC PATCH 0/2] raid5: 65% sequential-write performance improvement, stripe-queue take2
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode.
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: Tejun Heo <htejun@xxxxxxxxx>
• [RFC PATCH 2/2] raid5: use stripe_queues to prioritize the "most deserving" requests, take2
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 1/2] raid5: add the stripe_queue object for tracking raid io requests
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 0/2] raid5: 65% sequential-write performance improvement, stripe-queue take2
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: Mark Lord <liml@xxxxxx>
• Re: spare not becoming active
  • From: Simon <simon.xhz@xxxxxxxxx>
• Re: spare not becoming active
  • From: Simon <simon.xhz@xxxxxxxxx>
• Re: spare not becoming active
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: spare not becoming active
  • From: Simon <simon.xhz@xxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Patrik Jonsson <patrik@xxxxxxxxxxx>
• Re: Behavior of mdadm depending on user
  • From: Michael <michael@xxxxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• Re: Behavior of mdadm depending on user
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Proposed enhancement to mdadm: Allow "--write-behind=" to be done in grow mode.
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: Behavior of mdadm depending on user
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: "Johny Mail list" <maillist.johny@xxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Behavior of mdadm depending on user
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• RAID5 Expansion
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: RAID5 not being reassembled correctly after device swap
  • From: Neil Brown <neilb@xxxxxxx>
• RAID5 not being reassembled correctly after device swap
  • From: Michael Frotscher <infomails@xxxxxxxxxxxxxxxxxxxxx>
• best way to create RAID10 on an CentOS5 install
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Does "--write-behind=" have to be done at create time?
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Chinner <dgc@xxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Chinner <dgc@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Chinner <dgc@xxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: David Chinner <dgc@xxxxxxx>
• Re: [linux-pm] Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: Pavel Machek <pavel@xxxxxx>
• XFS mount option performance on Linux Software RAID 5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: spare not becoming active
  • From: Simon <simon.xhz@xxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: Pavel Machek <pavel@xxxxxx>
• Does "--write-behind=" have to be done at create time?
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm usage: creating arrays with helpful names?
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• Re: raid=noautodetect is apparently ignored?
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Matti Aarnio <matti.aarnio@xxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: mdadm usage: creating arrays with helpful names?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: David Chinner <dgc@xxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Fastest Chunk Size w/XFS For MD Software RAID = 1024k
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: deliberately degrading RAID1 to a single disk, then back again
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• spare not becoming active
  • From: Simon <simon.xhz@xxxxxxxxx>
• [RFC PATCH 2/2] raid5: use stripe_queues to prioritize the "most deserving" requests
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 1/2] raid5: add the stripe_queue object for tracking raid io requests
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 0/2] An evolutionary change to the raid456 queuing model
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: raid=noautodetect is apparently ignored?
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: "Johny Mail list" <maillist.johny@xxxxxxxxx>
• Re: mdadm usage: creating arrays with helpful names?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx
  • From: "Satyam Sharma" <satyam.sharma@xxxxxxxxx>
• Re: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [md-accel PATCH 00/19] md raid acceleration and the async_tx api
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• [md-accel PATCH 19/19] ARM: Add drivers/dma to arch/arm/Kconfig
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 18/19] iop3xx: surface the iop3xx DMA and AAU units to the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 17/19] iop13xx: surface the iop13xx adma units to the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 16/19] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 15/19] md: remove raid5 compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 14/19] md: handle_stripe5 - request io processing in raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 13/19] md: handle_stripe5 - add request/completion logic for async expand ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 12/19] md: handle_stripe5 - add request/completion logic for async read ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 11/19] md: handle_stripe5 - add request/completion logic for async check ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 10/19] md: handle_stripe5 - add request/completion logic for async compute ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 09/19] md: handle_stripe5 - add request/completion logic for async write ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 08/19] md: common infrastructure for running operations with raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 07/19] md: raid5_run_ops - run stripe operations outside sh->lock
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 05/19] raid5: refactor handle_stripe5 and handle_stripe6 (v2)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 06/19] raid5: replace custom debug PRINTKs with standard pr_debug
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 04/19] async_tx: add the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 02/19] dmaengine: make clients responsible for managing channels
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 01/19] dmaengine: refactor dmaengine around dma_async_tx_descriptor
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [md-accel PATCH 00/19] md raid acceleration and the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• mdadm usage: creating arrays with helpful names?
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• Re: raid=noautodetect is apparently ignored?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux Software RAID is really RAID?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: deliberately degrading RAID1 to a single disk, then back again
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• deliberately degrading RAID1 to a single disk, then back again
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Linux Software RAID is really RAID?
  • From: "Johny Mail list" <maillist.johny@xxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: raid=noautodetect is apparently ignored?
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: if (stripe_cache_size =< chunk_size) { BUG() }
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• if (stripe_cache_size =< chunk_size) { BUG() }
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid=noautodetect is apparently ignored?
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: raid=noautodetect is apparently ignored?
  • From: Neil Brown <neilb@xxxxxxx>
• raid=noautodetect is apparently ignored?
  • From: Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: stripe_cache_size and performance [BUG with =64kb]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance [BUG with =64kb]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance [BUG with =64kb]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance [BUG with =64kb]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: "Thorsten Wolf" <T_Wolf@xxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID 5 Grow
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• RAID 5 Grow
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Degraded array on every reboot
  • From: Neil Brown <neilb@xxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Raz <raziebe@xxxxxxxxx>
• Re: Degraded array on every reboot
  • From: David Greaves <david@xxxxxxxxxxxx>
• Degraded array on every reboot
  • From: "John Hendrikx" <hjohn@xxxxxxxxx>
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: limits on raid
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: limits on raid
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: stripe_cache_size and performance
  • From: Raz <raziebe@xxxxxxxxx>
• Re: limits on raid
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• stripe_cache_size and performance
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: Mark Lord <lkml@xxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: limits on raid
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: limits on raid
  • From: David Chinner <dgc@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: David Chinner <dgc@xxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Chinner <dgc@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: lsorense@xxxxxxxxxxxxxxxxxxx (Lennart Sorensen)
• Auto rebuild of Firewire/USB drive in 3-way RAID1
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• Re: suggestions for inexpensive linux jbod?
  • From: Sven Rudolph <Sven_Rudolph@xxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Michael <big_green_jelly_bean@xxxxxxxxx>
• Re: raid5 recover after a 2 disk failure
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc5 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: raid5 recover after a 2 disk failure
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: raid5 recover after a 2 disk failure
  • From: Frank Jenkins <fjenkins873@xxxxxxxxx>
• Re: suggestions for inexpensive linux jbod?
  • From: linux@xxxxxxxxxxx
• Re: suggestions for inexpensive linux jbod?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: suggestions for inexpensive linux jbod?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: [PATCH git-md-accel 1/2] raid5: refactor handle_stripe5 and handle_stripe6
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: limits on raid
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• [PATCH git-md-accel 2/2] raid5: replace custom debug print with standard pr_debug
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH git-md-accel 1/2] raid5: refactor handle_stripe5 and handle_stripe6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH git-md-accel 0/2] raid5 refactor, and pr_debug cleanup
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: lsorense@xxxxxxxxxxxxxxxxxxx (Lennart Sorensen)
• Re: limits on raid
  • From: lsorense@xxxxxxxxxxxxxxxxxxx (Lennart Sorensen)
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• stop sync?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: limits on raid
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: resync to last 27h - usually 3. what's this?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: suggestions for inexpensive linux jbod?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: resync to last 27h - usually 3. what's this?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• suggestions for inexpensive linux jbod?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: resync to last 27h - usually 3. what's this?
  • From: David Greaves <david@xxxxxxxxxxxx>
• resync to last 27h - usually 3. what's this?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Chinner <dgc@xxxxxxx>
• RE: Software based SATA RAID-5 expandable arrays?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: XFS Tunables for High Speed Linux SW RAID5 Systems?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
  • From: Mikael Pettersson <mikpe@xxxxxxxx>
• Re: XFS Tunables for High Speed Linux SW RAID5 Systems?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: limits on raid
  • From: David Chinner <dgc@xxxxxxx>
• Re: XFS Tunables for High Speed Linux SW RAID5 Systems?
  • From: David Chinner <dgc@xxxxxxx>
• Re: Software based SATA RAID-5 expandable arrays?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Software based SATA RAID-5 expandable arrays?
  • From: greenjelly <big_green_jelly_Bean@xxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: limits on raid
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: limits on raid
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: limits on raid
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: limits on raid
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: limits on raid
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: limits on raid
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• 2.6.22-rc4 BUG
  • From: linux@xxxxxxxxxxx
• Re: [linux-lvm] 2.6.22-rc4 XFS fails after hibernate/resume
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: raid5 recover after a 2 disk failure
  • From: "frank jenkins" <fjenkins873@xxxxxxxxxxx>
• raid5 recover after a 2 disk failure
  • From: "frank jenkins" <fjenkins873@xxxxxxxxxxx>
• Re: limits on raid
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: limits on raid
  • From: dean gaudet <dean@xxxxxxxxxx>
• raid synchronization too aggressive in 2.6.21?
  • From: Frank van Maarseveen <frankvm@xxxxxxxxxxx>
• Re: Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
  • From: Mikael Pettersson <mikpe@xxxxxxxx>
• Re: limits on raid
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: limits on raid
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: limits on raid
  • From: David Greaves <david@xxxxxxxxxxxx>
• Machine hanging on synchronize cache on shutdown 2.6.22-rc4-git[45678]
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: "Dan Merillat" <dan.merillat@xxxxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: limits on raid
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: Neil Brown <neilb@xxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: XFS Tunables for High Speed Linux SW RAID5 Systems?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• XFS Tunables for High Speed Linux SW RAID5 Systems?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: limits on raid
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: limits on raid
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: limits on raid
  • From: Avi Kivity <avi@xxxxxxxxxx>
• Re: limits on raid
  • From: David Chinner <dgc@xxxxxxx>
• need help in recovering a RAID
  • From: "Thorsten Wolf" <T_Wolf@xxxxxxx>
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: limits on raid
  • From: david@xxxxxxx
• Re: limits on raid
  • From: Neil Brown <neilb@xxxxxxx>
• limits on raid
  • From: david@xxxxxxx
• Re: raid5: coding style cleanup / refactor
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Removing devices from RAID-5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Removing devices from RAID-5
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Removing devices from RAID-5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Removing devices from RAID-5
  • From: Rich Walker <rw@xxxxxxxxxxxxxxx>
• Re: Removing devices from RAID-5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Removing devices from RAID-5
  • From: Rich Walker <rw@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Cluster Aware MD Driver
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Cluster Aware MD Driver
  • From: Xinwei Hu <hxinwei@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: "Thorsten Wolf" <T_Wolf@xxxxxxx>
• Re: spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• RFC: dealing with bad blocks: another view
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Neil Brown <neilb@xxxxxxx>
• raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• RE: raid5: coding style cleanup / refactor
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Mdadm recovery in infinite loop
  • From: "Kyle Harris" <kyle@xxxxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 000 of 2] md: Introduction - bugfixes for md/raid{1,10}
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Some RAID levels do not support bitmap
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: spare group
  • From: Neil Brown <neilb@xxxxxxx>
• Re: spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Neil Brown <neilb@xxxxxxx>
• SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: "Thorsten Wolf" <T_Wolf@xxxxxxx>
• Re: spare group
  • From: Neil Brown <neilb@xxxxxxx>
• Re: spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• [PATCH]is_power_of_2-dm
  • From: vignesh babu <vignesh.babu@xxxxxxxxx>
• Re: conflicting superblocks - Re: what is the best approach for fixing a degraded RAID5 (one drive failed) using mdadm?
  • From: Neil Brown <neilb@xxxxxxx>
• conflicting superblocks - Re: what is the best approach for fixing a degraded RAID5 (one drive failed) using mdadm?
  • From: simon redfern <simon@xxxxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• [PATCH 002 of 2] md: Fix bug in error handling during raid1 repair.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 2] md: Introduction - bugfixes for md/raid{1,10}
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 2] md: Fix two raid10 bugs.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: spare group
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Some RAID levels do not support bitmap
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Some RAID levels do not support bitmap
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Paranoid read mode for raid5/6
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Paranoid read mode for raid5/6
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• what is the best approach for fixing a degraded RAID5 (one drive failed) using mdadm?
  • From: simon redfern <simon@xxxxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Some RAID levels do not support bitmap
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: LVM on raid10 - severe performance drop
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• below 10MB/s write on raid5
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM on raid10 - severe performance drop
  • From: Bernd Schubert <bs@xxxxxxxxx>
• LVM on raid10 - severe performance drop
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: question about --assume-clean
  • From: Neil Brown <neilb@xxxxxxx>
• question about --assume-clean
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Help on Recovering a Corrupted raid5 Partition
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Help on Recovering a Corrupted raid5 Partition
  • From: Neil Brown <neilb@xxxxxxx>
• Help on Recovering a Corrupted raid5 Partition
  • From: phyros <dlopuch@xxxxxxx>
• [patch 06/54] md: Dont write more than is required of the last page of a bitmap
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• [patch 05/54] md: Avoid overflow in raid0 calculation with large components.
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Regarding odd RAID5 I/O patterns
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Regarding odd RAID5 I/O patterns
  • From: Neil Brown <neilb@xxxxxxx>
• Regarding odd RAID5 I/O patterns
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• RE: RAID 6 grow problem
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Iustin Pop <iusty@xxxxxxxxx>
• bug report on mdadm --export
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• [PATCH] md: comment add_stripe_bio
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• RE: RAID 6 grow problem
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID 6 grow problem
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RE: multiple xor_block() functions
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: problems with faulty disks and superblocks 1.0, 1.1 and 1.2
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• minimum speed for raid5 check
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: RAID6 clean?
  • From: Neil Brown <neilb@xxxxxxx>
• RAID6 clean?
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: 5 HDD RAID5 not starting after controller failure
  • From: Karsten Desler <kdesler@xxxxxxxxxx>
• Re: 5 HDD RAID5 not starting after controller failure
  • From: Neil Brown <neilb@xxxxxxx>
• 5 HDD RAID5 not starting after controller failure
  • From: Karsten Desler <kdesler@xxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: tj <lists@xxxxxxxx>
• RE: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: multiple xor_block() functions
  • From: Jouni Malinen <j@xxxxx>
• multiple xor_block() functions
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Valdis.Kletnieks@xxxxxx
• Re: RAID SB 1.x autodetection
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• possible logic bug in raid5.c
  • From: Jens Laas <jens.laas@xxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: raid1 check/repair read error recovery in 2.6.20
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• MD device flag from spare to active
  • From: Philip Bergen <philip.bergen@xxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• problems with faulty disks and superblocks 1.0, 1.1 and 1.2
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• very strange (maybe) raid1 testing results
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Bill Davidsen <davidsen@xxxxxxx>
• dm-crypt issue
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: mismatch_cnt = 128 for root (/) md raid1 device
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Creating RAID1 with bitmap fails
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• RAID SB 1.x autodetection
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <sbader3@xxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <sbader3@xxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jeremy Higdon <jeremy@xxxxxxx>
• Re: Reshaping raid0/10
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid state diagram
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Nikita Danilov <nikita@xxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Timothy Shimmin <tes@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• assemble array without rebuild - readonly mode?
  • From: Tim Harvey <tim_harvey@xxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: tj <lists@xxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• raid state diagram
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• mismatch_cnt = 128 for root (/) md raid1 device
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Andreas Dilger <adilger@xxxxxxxxxxxxx>
• Re: [dm-devel] [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• When does a disk get flagged as bad?
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• raid1 check/repair read error recovery in 2.6.20
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Thomas Jager <lists@xxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Colin McCabe <Colin.P.McCabe@xxxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Colin McCabe <Colin.P.McCabe@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Fwd: Identify SATA Disks
  • From: "lewis shobbrook" <lewis@xxxxxxxxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• I/O errors, server unresponsive, array NOT-degraded
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: mdadm on huge raid sets
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Bill Davidsen <davidsen@xxxxxxx>
• mdadm on huge raid sets
  • From: Erich Weiler <weiler@xxxxxxxxxxxx>
• Raid-5 long write wait while reading
  • From: Thomas Jager <lists@xxxxxxxx>
• Re: Adding larger disks to RAID5
  • From: "Bill Rugolsky Jr." <brugolsky@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: not resyncing after power cut.
  • From: "Chris Fanning" <christopher.fanning@xxxxxxxxx>
• Re: not resyncing after power cut.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm, raid10, and problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Adding larger disks to RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Adding larger disks to RAID5
  • From: "Bill Rugolsky Jr." <brugolsky@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Adding larger disks to RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Adding larger disks to RAID5
  • From: Christian <cjs@xxxxxxx>
• Re: not resyncing after power cut.
  • From: thunder7@xxxxxxxxx
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• [patch 39/69] md: Avoid a possibility that a read error can wrongly propagate through md/raid1 to a filesystem.
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• not resyncing after power cut.
  • From: "Chris Fanning" <christopher.fanning@xxxxxxxxx>
• ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 007 of 7] md: Change bitmap_unplug and others to void functions.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 7] md: Check that internal bitmap does not overlap other data.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 7] md: Improve the is_mddev_idle test fix
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 7] md: Improve message about invalid superblock during autodetect.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 7] md: Fix bug with linear hot-add and elsewhere.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 7] md: Don't write more than is required of the last page of a bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 7] md: Avoid overflow in raid0 calculation with large components.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 7] md: Introduction EXPLAIN PATCH SET HERE
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm, raid10, and problem
  • From: "Maciej 'Agaran' Pijanka" <agaran@xxxxxxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Colin McCabe <Colin.P.McCabe@xxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: david@xxxxxxx
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: david@xxxxxxx
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Recovery of software RAID5 using FC6 rescue?
  • From: "Mark A. O'Neil" <mark.a.oneil@xxxxxxxxxxxxx>
• unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Michal Piotrowski" <michal.k.k.piotrowski@xxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Gregory Seidman <gsslist+linuxraid@xxxxxxxxxxxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Neil Brown <neilb@xxxxxxx>