Linux RAID Storage Date Index

• Thread Index

• mdadm: RUN_ARRAY failed: Cannot allocate memory
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• RE: Grow a RAID-6 ?
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: Swap initialised as an md?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Swap initialised as an md?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: linux@xxxxxxxxxxx
• Re: Grow a RAID-6 ?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Grow a RAID-6 ?
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Grow a RAID-6 ?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: [PATCH 2.6.21-rc4 01/15] dmaengine: add base support for the async_tx api
  • From: Yuri Tikhonov <yur@xxxxxxxxxxx>
• Re: XFS sunit/swidth for raid10
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• [PATCH 2.6.21-rc4 05/15] md: use raid5_run_ops for stripe cache operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 08/15] md: move raid5 parity checks to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 04/15] md: add raid5_run_ops and support routines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 09/15] md: satisfy raid5 read requests via raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 03/15] dmaengine: add the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 14/15] iop13xx: Surface the iop13xx adma units to the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 10/15] md: use async_tx and raid5_run_ops for raid5 expansion operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 13/15] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 11/15] md: move raid5 io requests to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 06/15] md: move write operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 15/15] iop3xx: Surface the iop3xx DMA and AAU units to the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 12/15] md: remove raid5 compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 07/15] md: move raid5 compute block operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 02/15] ARM: Add drivers/dma to arch/arm/Kconfig
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 01/15] dmaengine: add base support for the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.21-rc4 00/15] md raid5 acceleration and async_tx
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: XFS sunit/swidth for raid10
  • From: dean gaudet <dean@xxxxxxxxxx>
• [PATCH 003 of 3] md: Convert compile time warnings into runtime warnings.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 3] md: Clear the congested_fn when stopping a raid5
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 3] md: Allow raid4 arrays to be reshaped.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 3] md: bug fixes for md for 2.6.21
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: linux@xxxxxxxxxxx
• Re: Another report of a raid6 array being maintaind by _raid5 in ps .
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: XFS sunit/swidth for raid10
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: BLK_DEV_MD with CONFIG_NET
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: XFS sunit/swidth for raid10
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Another report of a raid6 array being maintaind by _raid5 in ps .
  • From: Neil Brown <neilb@xxxxxxx>
• Another report of a raid6 array being maintaind by _raid5 in ps .
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• XFS sunit/swidth for raid10
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: BLK_DEV_MD with CONFIG_NET
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: BLK_DEV_MD with CONFIG_NET
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: BLK_DEV_MD with CONFIG_NET
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: mdadm: raid1 with ext3 - filesystem size differs?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: BLK_DEV_MD with CONFIG_NET
  • From: David Miller <davem@xxxxxxxxxxxxx>
• BLK_DEV_MD with CONFIG_NET
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: strange test results
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Stefan Roese <sr@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Michael Ellerman <michael@xxxxxxxxxxxxxx>
• Raid1 replaced with raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• strange test results
  • From: Tomka Gergely <gergely@xxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• raid10 far layout outperforms offset at writing? (was: Help with chunksize on raid10 -p o3 array)
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: raid6 array , part id 'fd' not assembling at boot .
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: Data corruption on software raid.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Data corruption on software raid.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Data corruption on software raid.
  • From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: raid6 array , part id 'fd' not assembling at boot .
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Failed reads from RAID-0 array; still no joy in Mudville.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: Failed reads from RAID-0 array; still no joy in Mudville.
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: Data corruption on software raid.
  • From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx>
• Re: Failed reads from RAID-0 array; still no joy in Mudville.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Data corruption on software raid.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: Data corruption on software raid.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Data corruption on software raid.
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: Data corruption on software raid.
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Data corruption on software raid.
  • From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: mdadm file system type check
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [Linux-usb-users] Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: Failed reads from RAID-0 array; still no joy in Mudville.
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: Failed reads from RAID-0 array; still no joy in Mudville.
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: mdadm file system type check
  • From: "William L. Thomson Jr." <wltjr@xxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Stefan Roese <sr@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: mdadm file system type check
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Yuri Tikhonov <yur@xxxxxxxxxxx>
• Re: mdadm file system type check
  • From: Chris Lindley <ferg@xxxxxxxxxxxx>
• Re: mdadm file system type check
  • From: "William L. Thomson Jr." <wltjr@xxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Stefan Roese <sr@xxxxxxx>
• Re: mdadm file system type check
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid6 array , part id 'fd' not assembling at boot .
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: Neil Brown <neilb@xxxxxxx>
• Failed reads from RAID-0 array (from newbie who has read the FAQ)
  • From: "Michael Schwarz" <mschwarz@xxxxxxxxxxxxx>
• Re: mdadm file system type check
  • From: "William L. Thomson Jr." <wltjr@xxxxxxxxxx>
• raid6 array , part id 'fd' not assembling at boot .
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Re: mdadm file system type check
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm file system type check
  • From: berk walker <berk@xxxxxxxxx>
• mdadm file system type check
  • From: "William L. Thomson Jr." <wltjr@xxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Stefan Roese <sr@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Paul Mackerras <paulus@xxxxxxxxx>
• mdadm: raid1 with ext3 - filesystem size differs?
  • From: Hanno Meyer-Thurow <h.mth@xxxxxx>
• [PATCH] [PPC32] ADMA support for PPC 440SPe processors.
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mismatch_cnt questions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Tomka Gergely <gergely@xxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Neil Brown <neilb@xxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Tomka Gergely <gergely@xxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Tomka Gergely <gergely@xxxxxxxx>
• Re: sw raid0 read bottleneck
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• sw raid0 read bottleneck
  • From: Tomka Gergely <gergely@xxxxxxxx>
• Issue with Adaptec AIC-7899P using MD on Dell PE 2650
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Help with chunksize on raid10 -p o3 array
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Help with chunksize on raid10 -p o3 array
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Help with chunksize on raid10 -p o3 array
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: mismatch_cnt questions - how about raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: mismatch_cnt questions - how about raid10?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Help with chunksize on raid10 -p o3 array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Reshaping raid0/10
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Reshaping raid0/10
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: Reshaping raid0/10
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• RAID5 failure due to changing, by mistake, of a good disk
  • From: "Claudiu Cismaru" <claudiu.cismaru@xxxxxxxxx>
• Re: Changing partition types safe? raidtools to mdadm migration
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Changing partition types safe? raidtools to mdadm migration
  • From: "Simon Matthews" <simon.d.matthews@xxxxxxxxx>
• Re: Changing partition types safe? raidtools to mdadm migration
  • From: "Simon Matthews" <simon.d.matthews@xxxxxxxxx>
• Re: Changing partition types safe? raidtools to mdadm migration
  • From: Neil Brown <neilb@xxxxxxx>
• Changing partition types safe? raidtools to mdadm migration
  • From: "Simon Matthews" <simon.d.matthews@xxxxxxxxx>
• Re: [PATCH] fix read past end of array in md/linear.c
  • From: Andy Isaacson <adi@xxxxxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mismatch_cnt questions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH] fix read past end of array in md/linear.c
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mismatch_cnt questions
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid 10 Problems?
  • From: Marc Perkel <mperkel@xxxxxxxxx>
• Re: Raid 10 Problems?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• [PATCH] fix read past end of array in md/linear.c
  • From: Andy Isaacson <adi@xxxxxxxxxxxxx>
• Re: Replace drive in RAID5 without losing redundancy?
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: mismatch_cnt questions
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Raid 10 Problems?
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• [patch 021/101] md: Avoid possible BUG_ON in md bitmap handling.
  • From: Greg KH <gregkh@xxxxxxx>
• [patch 045/101] md: Fix raid10 recovery problem.
  • From: Greg KH <gregkh@xxxxxxx>
• Re: no journaling and loops on softraid?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Replace drive in RAID5 without losing redundancy?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: berk walker <berk@xxxxxxxxx>
• Re: high mismatch count after scrub
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Help with chunksize on raid10 -p o3 array
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: Michael Stumpf <mjstumpf@xxxxxxxxx>
• Re: Help with chunksize on raid10 -p o3 array
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mismatch_cnt questions
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: high mismatch count after scrub
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: high mismatch count after scrub
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Replace drive in RAID5 without losing redundancy?
  • From: Ralf Müller <ralf@xxxxxxxx>
• Help with chunksize on raid10 -p o3 array
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: mismatch_cnt questions - how about raid10?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mismatch_cnt questions - how about raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: mismatch_cnt questions - how about raid10?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mismatch_cnt questions - how about raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Replace drive in RAID5 without losing redundancy?
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Replace drive in RAID5 without losing redundancy?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Paul Davidson <Paul.Davidson@xxxxxxxxxx>
• Re: high mismatch count after scrub
  • From: Neil Brown <neilb@xxxxxxx>
• high mismatch count after scrub
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: [PATCH] md: Fix for raid6 reshape.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: no journaling and loops on softraid?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• no journaling and loops on softraid?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Replace drive in RAID5 without losing redundancy?
  • From: Neil Brown <neilb@xxxxxxx>
• How to copy a page to another page completely?
  • From: "Yu-Chen Wu" <g944370@xxxxxxxxxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Raid on USB flash disk
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: Michael Stumpf <mjstumpf@xxxxxxxxx>
• Re: detecting/correcting _slightly_ flaky disks
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• detecting/correcting _slightly_ flaky disks
  • From: Michael Stumpf <mjstumpf@xxxxxxxxx>
• Replace drive in RAID5 without losing redundancy?
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: mismatch_cnt questions
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Tejun Heo <teheo@xxxxxxx>
• RAID & ext dire straits
  • From: "Gunny Smith" <gunny74@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mismatch_cnt questions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mismatch_cnt questions
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Unexpectedly slow raid1 benchmark results.
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Unexpectedly slow raid1 benchmark results.
  • From: "Dan" <kasper37@xxxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Neil Brown <neilb@xxxxxxx>
• mismatch_cnt questions
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH] md: Fix for raid6 reshape.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID0 to RAID5 upgrade
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Does anyone on this list have a Raptor74/150 sw raid with > 8 drives?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: RAID1, hot-swap and boot integrity
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RAID1, hot-swap and boot integrity
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: Growing a raid 6 array
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] md: Fix for raid6 reshape.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: Fix for raid6 reshape.
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] md: Fix for raid6 reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: swap on raid
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: Growing a raid 6 array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID0 to RAID5 upgrade
  • From: rabbit@xxxxxxxxx (Peter Rabbitson)
• Re: swap on raid
  • From: rabbit@xxxxxxxxx (Peter Rabbitson)
• Re: swap on raid
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Growing a raid 6 array
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RAID0 to RAID5 upgrade
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Growing a raid 6 array
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: swap on raid
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: swap on raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Growing a raid 6 array
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• swap on raid
  • From: rabbit@xxxxxxxxx (Peter Rabbitson)
• Growing a raid 6 array
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: end to end error recovery musings
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxx>
• RAID5 4 disk recovery advice
  • From: "Rich Deeming" <rdeeming@xxxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• RE: DMRAID feature direction?
  • From: Neil Brown <neilb@xxxxxxx>
• RE: DMRAID feature direction?
  • From: "Gaston, Jason D" <jason.d.gaston@xxxxxxxxx>
• Re: trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: Linux Software RAID Bitmap Question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID Bitmap Question
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: end to end error recovery musings
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: end to end error recovery musings
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: "Martin K. Petersen" <mkp@xxxxxxx>
• RE: end to end error recovery musings
  • From: "Moore, Eric" <Eric.Moore@xxxxxxx>
• Re: end to end error recovery musings
  • From: Douglas Gilbert <dougg@xxxxxxxxxx>
• Re: Linux Software RAID Bitmap Question
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [RFC, PATCH] raid456: replace the handle_list with a multi-threaded workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: DMRAID feature direction?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: end to end error recovery musings
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• DMRAID feature direction?
  • From: "Gaston, Jason D" <jason.d.gaston@xxxxxxxxx>
• Re: end to end error recovery musings
  • From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
• Re: trouble creating array
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Linux Software RAID Bitmap Question
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: end to end error recovery musings
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: end to end error recovery musings
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: end to end error recovery musings
  • From: Andreas Dilger <adilger@xxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Linux Software RAID Bitmap Question
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: end to end error recovery musings
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Problems with software raid - all mine I am sure
  • From: Michael <michael@xxxxxxxxxxx>
• Re: Problems with software raid - all mine I am sure
  • From: Tru Huynh <tru@xxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: berk walker <berk@xxxxxxxxx>
• RE: end to end error recovery musings
  • From: "Moore, Eric" <Eric.Moore@xxxxxxx>
• Re: end to end error recovery musings
  • From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: end to end error recovery musings
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• Re: end to end error recovery musings
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Problems with software raid - all mine I am sure
  • From: Michael <michael@xxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: "Colin Simpson" <csimpson@xxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: end to end error recovery musings
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: end to end error recovery musings
  • From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: end to end error recovery musings
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxx>
• Re: beginner error detection
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Douglas Gilbert <dougg@xxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: end to end error recovery musings
  • From: Neil Brown <neilb@xxxxxxx>
• Re: trouble creating array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Linux Software RAID Bitmap Question
  • From: Neil Brown <neilb@xxxxxxx>
• Re: trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: trouble creating array
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Benjamin Davenport <ben@xxxxxxxxxxxxxxx>
• Re: trouble creating array
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• trouble creating array
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Frank van Maarseveen <frankvm@xxxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Linux Software RAID Bitmap Question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: "Colin Simpson" <csimpson@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Chris Wedgwood <cw@xxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Jason Rainforest <l3mming@xxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Jason Rainforest <l3mming@xxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: end to end error recovery musings
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: Andreas Dilger <adilger@xxxxxxxxxxxxx>
• Re: nonzero mismatch_cnt with no earlier error
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• nonzero mismatch_cnt with no earlier error
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: end to end error recovery musings
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Reshaping raid0/10
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID a bit of a weakness?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Linux Software RAID a bit of a weakness?
  • From: "Colin Simpson" <csimpson@xxxxxxxxx>
• Re: 2.6.20: stripe_cache_size goes boom with 32mb
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Bill Davidsen <davidsen@xxxxxxx>
• end to end error recovery musings
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: 2.6.20: stripe_cache_size goes boom with 32mb
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: Reshaping raid0/10
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: 2.6.20: stripe_cache_size goes boom with 32mb
  • From: Jason Rainforest <l3mming@xxxxxxxxxxxx>
• Re: 2.6.20: stripe_cache_size goes boom with 32mb
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• beginner error detection
  • From: Tomka Gergely <gergely@xxxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
• 2.6.20: stripe_cache_size goes boom with 32mb
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Stephen C Woods <scw@xxxxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Reshaping raid0/10
  • From: dean gaudet <dean@xxxxxxxxxx>
• ANNOUNCE: mdadm 2.6.1 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Oleg Verych <olecom@xxxxxxxxxxxxxx>
• Re: [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: Reshaping raid0/10
  • From: Neil Brown <neilb@xxxxxxx>
• Reshaping raid0/10
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• 5th USENIX Conference on File and Storage Technologies - Paper
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [PATCH 000 of 6] md: Assorted fixes and features for md for 2.6.21
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mdadm 2.6, linux 2.6.17, failed grow/reshape
  • From: "Thomas Langås" <thomas.langaas@xxxxxxxxx>
• Re: mdadm 2.6, linux 2.6.17, failed grow/reshape
  • From: "Thomas Langås" <thomas.langaas@xxxxxxxxx>
• Re: mdadm 2.6, linux 2.6.17, failed grow/reshape
  • From: Neil Brown <neilb@xxxxxxx>
• mdadm 2.6, linux 2.6.17, failed grow/reshape
  • From: "Thomas Langås" <thomas.langaas@xxxxxxxxx>
• mdadm 2.6, linux 2.6.17, failed grow/reshape
  • From: "Thomas Langås" <thomas.langaas@xxxxxxxxx>
• Re: RAID10 Resync fails with specific chunk size and drive sizes (reproducible)
  • From: rabbit@xxxxxxxxx (Peter Rabbitson)
• Re: PATA/SATA Disk Reliability paper
  • From: Al Boldi <a1426z@xxxxxxxxx>
• RAID10 Resync fails with specific chunk size and drive sizes (reproducible)
  • From: rabbit@xxxxxxxxx (Peter Rabbitson)
• [PATCH 006 of 6] md: Add support for reshape of a raid6
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 6] md: Restart a (raid5) reshape that has been aborted due to a read/write error.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 6] md: RAID6: clean up CPUID and FPU enter/exit code
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 6] md: Clean out unplug and other queue function on md shutdown
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 6] md: Move warning about creating a raid array on partitions of the one device.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 6] md: Fix raid10 recovery problem.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 6] md: Assorted fixes and features for md for 2.6.21
  • From: NeilBrown <neilb@xxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: RAID 10 resync leading to attempt to access beyond end of device
  • From: "John Stilson" <john9601@xxxxxxxxx>
• Re: mdadm --grow failed
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: PATA/SATA Disk Reliability paper
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: mdadm --grow failed
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: mdadm --grow failed
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: Changing chunk size
  • From: Bill Davidsen <davidsen@xxxxxxx>
• PATA/SATA Disk Reliability paper
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: mdadm --grow failed
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: Fw: Re: mdadm --grow failed
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm --grow failed
  • From: David Greaves <david@xxxxxxxxxxxx>
• Fw: Re: mdadm --grow failed
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: mdadm --grow failed
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: Changing chunk size
  • From: berk walker <berk@xxxxxxxxx>
• Re: mdadm --grow failed
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm --grow failed
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: mdadm --grow failed
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm --grow failed
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Need help to rescue my raid5 array after bad try to add new disks.
  • From: Roy Sindre Norangshol <roysn@xxxxxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: mdadm --grow failed
  • From: Neil Brown <neilb@xxxxxxx>
• mdadm --grow failed
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: Changing chunk size
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Changing chunk size
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: Changing chunk size
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Changing chunk size
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Changing chunk size
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [KJ][PATCH] is_power_of_2 in md
  • From: Vignesh Babu BM <vignesh.babu@xxxxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Neil Brown <neilb@xxxxxxx>
• 2.6.20: reproducible hard lockup with RAID-5 resync
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: [danno@xxxxxxxxxxxxx: minor cosmetic bug in md]
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID 10 resync leading to attempt to access beyond end of device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Changing chunk size
  • From: Neil Brown <neilb@xxxxxxx>
• [danno@xxxxxxxxxxxxx: minor cosmetic bug in md]
  • From: Dan Pritts <danno@xxxxxxxxxxxxx>
• Re: RAID 10 resync leading to attempt to access beyond end of device
  • From: "John Stilson" <john9601@xxxxxxxxx>
• Re: RAID 10 resync leading to attempt to access beyond end of device
  • From: "John Stilson" <john9601@xxxxxxxxx>
• Changing chunk size
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID 10 resync leading to attempt to access beyond end of device
  • From: Neil Brown <neilb@xxxxxxx>
• RAID 10 resync leading to attempt to access beyond end of device
  • From: "John Stilson" <john9601@xxxxxxxxx>
• Re: slow 'check'
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: md: md6_raid5 crash 2.6.20
  • From: Neil Brown <neilb@xxxxxxx>
• super1.c:1146: warning: 'offset' might be used uninitialized in this function
  • From: Krzysztof Oledzki <olel@xxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: md: md6_raid5 crash 2.6.20
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: md: md6_raid5 crash 2.6.20
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md: md6_raid5 crash 2.6.20
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: md: md6_raid5 crash 2.6.20
  • From: Neil Brown <neilb@xxxxxxx>
• Re: slow 'check'
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: old raid0run
  • From: Marco Scoffier <marco@xxxxxxxx>
• md: md6_raid5 crash 2.6.20
  • From: "Marc Marais" <marcm@xxxxxxxxxxxxxxxx>
• Re: old raid0run
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• old raid0run
  • From: Marco Scoffier <marco@xxxxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Neil Brown <neilb@xxxxxxx>
• Re: slow 'check'
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: slow 'check'
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid on USB flash disk
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Raid on USB flash disk
  • From: Arne Jansen <sensille@xxxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: slow 'check'
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: slow 'check'
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: slow 'check'
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: slow 'check'
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: slow 'check'
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• slow 'check'
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Hard disk wierdness in raid array
  • From: TJ <systemloc@xxxxxxxxxxxxx>
• Re: [md] RAID6: clean up CPUID and FPU enter/exit code
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: mdadm RAID5 array failure
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm RAID5 array failure
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: mdadm RAID5 array failure
  • From: Neil Brown <neilb@xxxxxxx>
• mdadm RAID5 array failure
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: [RFC][PATCH 00/12] md raid acceleration and performance analysis
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• [PATCH] md: Avoid possible BUG_ON in md bitmap handling.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Move superblock on partition resize?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Move superblock on partition resize?
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• RE: Could "bio_vec" be referenced any time?
  • From: "Yu-Chen Wu" <g944370@xxxxxxxxxxxxxx>
• RE: [RFC][PATCH 00/12] md raid acceleration and performance analysis
  • From: "Leech, Christopher" <christopher.leech@xxxxxxxxx>
• Re: Could "bio_vec" be referenced any time?
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 2.6.20] drivers/md.c: Use ARRAY_SIZE macro when appropriate
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Could "bio_vec" be referenced any time?
  • From: "Yu-Chen Wu" <g944370@xxxxxxxxxxxxxx>
• inconsitent harddisks, still after checkarray run
  • From: Michael Schmitt <mschmitt@xxxxxxxxxxxxx>
• [patch 05/59] md: pass down BIO_RW_SYNC in raid{1,10}
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• Re: Hot add not supported by version 1.x superblocks?
  • From: Sean Puttergill <puttergi@xxxxxxxx>
• Hot add not supported by version 1.x superblocks?
  • From: Sean Puttergill <puttergi@xxxxxxxx>
• Re: md device on Redhat Linux 3
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: md device on Redhat Linux 3
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20-rc6: known regressions with patches
  • From: Dave Jones <davej@xxxxxxxxxx>
• Re: 2.6.20-rc6: known regressions with patches
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: md autodetect only detects one disk in raid1
  • From: dean gaudet <dean@xxxxxxxxxx>
• md autodetect only detects one disk in raid1
  • From: kenneth johansson <ken@xxxxxxxxx>
• [PATCH 2.6.20-rc6] md: expose uuid and degraded attributes in sysfs
  • From: Iustin Pop <iusty@xxxxxxxxx>
• 2.6.20-rc6: known regressions with patches
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• 2.6.20-rc6: known unfixed regressions (part 1)
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: Synchronous mdadm --add/--re-add operations
  • From: Neil Brown <neilb@xxxxxxx>
• Synchronous mdadm --add/--re-add operations
  • From: Andre Majorel <aym-xunil@xxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• [PATCH] md: Remove unnecessary printk when raid5 gets an unaligned read.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md: Fix potential memalloc deadlock in md
  • From: NeilBrown <neilb@xxxxxxx>
• Re: There is an advice
  • From: Neil Brown <neilb@xxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Bill Cizek <cizek@xxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Pavel Machek <pavel@xxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Raid-1 to Raid-5 conversion possible?
  • From: Neil Brown <neilb@xxxxxxx>
• Raid-1 to Raid-5 conversion possible?
  • From: "Vidar Sonerud" <vidar.sonerud@xxxxxxxxx>
• Re: Ooops on read-only raid5 while unmounting as xfs
  • From: Nix <nix@xxxxxxxxxxxxx>
• 2.6.20-rc5: known unfixed regressions (v3) (part 1)
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Always ask me to run fsck...Why?
  • From: "Yu-Chen Wu" <g944370@xxxxxxxxxxxxxx>
• Nice Sideeffect of growing (was: RAID5 Resize Experience)
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 002 of 4] md: Make 'repair' actually work for raid1.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 002 of 4] md: Make 'repair' actually work for raid1.
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: [patch] md: bitmap read_page error
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Ooops on read-only raid5 while unmounting as xfs
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 2.6.20-rc5 07/12] md: move raid5 parity checks to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 05/12] md: move write operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 04/12] md: use raid5_run_ops for stripe cache operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 11/12] md: remove raid5 compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 12/12] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 09/12] md: use async_tx and raid5_run_ops for raid5 expansion operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 10/12] md: move raid5 io requests to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 08/12] md: satisfy raid5 read requests via raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 03/12] md: add raid5_run_ops and support routines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 06/12] md: move raid5 compute block operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 02/12] dmaengine: add the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2.6.20-rc5 01/12] dmaengine: add base support for the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Ooops on read-only raid5 while unmounting as xfs
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: "kyle" <kylewong@xxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• [PATCH 05/12] md: move write operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 06/12] md: move raid5 compute block operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 02/12] dmaengine: add the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 09/12] md: use async_tx and raid5_run_ops for raid5 expansion operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 10/12] md: move raid5 io requests to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 04/12] md: use raid5_run_ops for stripe cache operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 03/12] md: add raid5_run_ops and support routines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 11/12] md: remove raid5 compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 07/12] md: move raid5 parity checks to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 12/12] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 08/12] md: satisfy raid5 read requests via raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 01/12] dmaengine: add base support for the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Ooops on read-only raid5 while unmounting as xfs
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [patch] md: bitmap read_page error
  • From: "yang yin" <yinyang801120@xxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Donald Douwsma <donaldd@xxxxxxx>
• [PATCH 003 of 4] md: Make sure the events count in an md array never returns to zero.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 4] md: Make 'repair' actually work for raid1.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 4] md: Avoid reading past the end of a bitmap file.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Update email address and status for MD in MAINTAINERS.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: Introduction - Assorted bugfixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [patch] md: bitmap read_page error
  • From: Neil Brown <neilb@xxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Chuck Ebbert <cebbert@xxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Pavel Machek <pavel@xxxxxx>
• Re: What is the exacting meaning of Striped_Cache_Size?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: "kyle" <kylewong@xxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: "kyle" <kylewong@xxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: "kyle" <kylewong@xxxxxxxxxx>
• Re: change strip_cache_size freeze the whole raid
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• change strip_cache_size freeze the whole raid
  • From: "kyle" <kylewong@xxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible (multi-threaded USB no go)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• [PATCH] drivers/block/DAC960: Converted 'boolean' to 'bool'
  • From: Richard Knutsson <ricknu-0@xxxxxxxxxxxxxx>
• [patch] md: bitmap read_page error
  • From: "yang yin" <yinyang801120@xxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible (multi-threaded USB no go)
  • From: Greg KH <greg@xxxxxxxxx>
• RE: What is the exacting meaning of Striped_Cache_Size?
  • From: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
• Re: What is the exacting meaning of Striped_Cache_Size?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• What is the exacting meaning of Striped_Cache_Size?
  • From: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
• 2.6.20-rc5: cp 18gb 18gb.2 = OOM killer, reproducible just like 2.16.19.2
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: bad performance on RAID 5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible (multi-threaded USB no go)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: bad performance on RAID 5
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: thunder7@xxxxxxxxx
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: thunder7@xxxxxxxxx
• Problem
  • From: Alessio Palmero Aprosio <alessio@xxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: "Avuton Olrich" <avuton@xxxxxxxxx>
• 2.6.19.2, cp 18gb_file 18gb_file.2 = OOM killer, 100% reproducible
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Kernel 2.6.19.2 New RAID 5 Bug (oops when writing Samba -> RAID5)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: bad performance on RAID 5
  • From: "Roger Lucas" <roger@xxxxxxxxxxxxx>
• RAID5 Resize Experience
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: upgrade to mdadm 2.6 x86_64 issues
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: [PATCH 00/12] md raid acceleration and the async_tx api
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: bad performance on RAID 5
  • From: dean gaudet <dean@xxxxxxxxxx>
• upgrade to mdadm 2.6 x86_64 issues
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: bad performance on RAID 5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: bad performance on RAID 5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: bad performance on RAID 5
  • From: Sevrin Robstad <quackyo@xxxxxxxx>
• Re: bad performance on RAID 5
  • From: Sevrin Robstad <quackyo@xxxxxxxx>
• Re: bad performance on RAID 5
  • From: Mark Hahn <hahn@xxxxxxxxxxxxxxxxxxx>
• Re: bad performance on RAID 5
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• 2.6.20-rc5: knwon unfixed regressions (v2) (part1)
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: bad performance on RAID 5
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: bad performance on RAID 5
  • From: Sevrin Robstad <quackyo@xxxxxxxx>
• Re: bad performance on RAID 5
  • From: Sevrin Robstad <quackyo@xxxxxxxx>
• Ooops on read-only raid5 while unmounting as xfs
  • From: "Francois Barre" <francois.barre@xxxxxxxxx>
• Re: bad performance on RAID 5
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: [PATCH 00/12] md raid acceleration and the async_tx api
  • From: Yuri Tikhonov <yur_t@xxxxxxx>
• Re: bad performance on RAID 5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• bad performance on RAID 5
  • From: Sevrin Robstad <quackyo@xxxxxxxx>
• RAID6 reassembly oddities
  • From: Troels Bang Jensen <troels@xxxxxxxx>
• md: bug in file drivers/md/md.c, line 1652
  • From: noah <noah123@xxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: berk walker <berk@xxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: FailSpare event?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: FailSpare event?
  • From: Neil Brown <neilb@xxxxxxx>
• Man page patch (manage mode options clarification)
  • From: Andre Majorel <aym-xunil@xxxxxxxxx>
• Re: FailSpare event?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Man page patch (bold font for option names in MISC MODE section)
  • From: Andre Majorel <aym-xunil@xxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: FailSpare event?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: James Ralston <qralston+ml.linux-raid@xxxxxxxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: raid5 software vs hardware: parity calculations?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Ernst Herzberg <earny@xxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: FailSpare event?
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: FailSpare event?
  • From: "Martin Schröder" <martin@xxxxxxxxxx>
• Re: FailSpare event?
  • From: Mike Hardy <mhardy@xxxxxxx>
• Linux Software RAID 5 Performance Optimizations: 2.6.19.1: (211MB/s read & 195MB/s write)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Tweaking/Optimizing MD RAID: 195MB/s write, 181MB/s read (so far)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: Tweaking/Optimizing MD RAID: 195MB/s write, 181MB/s read (so far)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RAID5 Tweaked to 195MB/s on 4 x 150 Raptors
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Tweaking/Optimizing MD RAID: 195MB/s write, 181MB/s read (so far)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Neil Brown <neilb@xxxxxxx>
• raid5 software vs hardware: parity calculations?
  • From: James Ralston <qralston+ml.linux-raid@xxxxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: FailSpare event?
  • From: Neil Brown <neilb@xxxxxxx>
• FailSpare event?
  • From: Mike <mikee@xxxxxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: [patch] md: pass down BIO_RW_SYNC in raid{1,10}
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: [patch] md: pass down BIO_RW_SYNC in raid{1,10}
  • From: Lars Ellenberg <Lars.Ellenberg@xxxxxxxxxx>
• Re: [patch] md: pass down BIO_RW_SYNC in raid{1,10}
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [patch] md: pass down BIO_RW_SYNC in raid{1,10}
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [patch] md: pass down BIO_RW_SYNC in raid{1,10}
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: RAID1 repair issue with 2.6.16.36 kernel
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RAID1 repair issue with 2.6.16.36 kernel
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>