Linux RAID Storage Date Index

• Thread Index

• Re: Suggested use of --invalid-backup?
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: mpt2sas + raid10 goes boom
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: Suggested use of --invalid-backup?
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: mpt2sas + raid10 goes boom
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: mpt2sas + raid10 goes boom
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: mpt2sas + raid10 goes boom
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
• Re: mpt2sas + raid10 goes boom
  • From: Baruch Even <baruch@xxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Durval Menezes <durval.menezes@xxxxxxxxx>
• Re: mpt2sas + raid10 goes boom
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• mpt2sas + raid10 goes boom
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: RAID1 to 10 (Synology NAS)
  • From: NeilBrown <neilb@xxxxxxx>
• RAID1 to 10 (Synology NAS)
  • From: Al Grant <bigal.nz@xxxxxxxxx>
• Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Help, array corrupted after clean shutdown.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Help, array corrupted after clean shutdown.
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: bcache: BUG in fuzz testing without devices
  • From: Kent Overstreet <koverstreet@xxxxxxxxxx>
• Re: multiple disk failures in an md raid6 array
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: multiple disk failures in an md raid6 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID barely usable on my home machine
  • From: Peter Maloney <peter.maloney@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID barely usable on my home machine
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: multiple disk failures in an md raid6 array
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID barely usable on my home machine
  • From: Maik Zumstrull <maik@xxxxxxxxxxxxx>
• Re: RAID barely usable on my home machine
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• RAID barely usable on my home machine
  • From: Maik Zumstrull <maik@xxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: multiple disk failures in an md raid6 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PULL REQUEST] md updates for 3.9
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: keld@xxxxxxxxxx
• multiple disk failures in an md raid6 array
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] Manage.c: Try to get EXCL access more times while stopping the array
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH] Add updating component_size to manager thread of mdmon
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: RAID 5 doesn't scale
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• RAID 5 doesn't scale
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Xen disk write slowness in kernel 3.8.x
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: Xen disk write slowness in kernel 3.8.x
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Suggested use of --invalid-backup?
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: Solving the raid write performance problems
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• bcache: BUG in fuzz testing without devices
  • From: Sasha Levin <sasha.levin@xxxxxxxxxx>
• Re: Solving the raid write performance problems
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Solving the raid write performance problems
  • From: keld@xxxxxxxxxx
• Re: Solving the raid write performance problems
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Solving the raid write performance problems
  • From: Peter Landmann <sfrazt@xxxxxxxxxxxxxx>
• Re: reiserfsck Segfaulting om md readonly raid6 array, dmesg shows "kernel BUG at drivers/md/md.c:5790"
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• reiserfsck Segfaulting om md readonly raid6 array, dmesg shows "kernel BUG at drivers/md/md.c:5790"
  • From: Durval Menezes <durval.menezes@xxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD does not wait for drives on start-up with kernels 3.8+
  • From: CoolCold <coolthecold@xxxxxxxxx>
• MD does not wait for drives on start-up with kernels 3.8+
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Failing Reshape (SOLUTION)
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: RAID-10 with mixed block size HDDs
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: RAID-10 with mixed block size HDDs
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID-10 with mixed block size HDDs
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Failing Reshape
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: Degraded Raid 5 Assembles incorrectly(maybe), will not mount
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Kernel panic after hot remove in raid1d
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: Re: Problem with mdadm 3.2.5
  • From: Tarak Anumolu <tarak.anumolu@xxxxxxxxxxx>
• Re: RAID-10 with mixed block size HDDs
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Degraded Raid 5 Assembles incorrectly(maybe), will not mount
  • From: "Steve Macica" <macica@xxxxxxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Problem with mdadm 3.2.5
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Problem with mdadm 3.2.5
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: Problem with mdadm 3.2.5
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: NeilBrown <neilb@xxxxxxx>
• Problem with mdadm 3.2.5
  • From: Tarak Anumolu <tarak.anumolu@xxxxxxxxxxx>
• Re: [patch]raid5: make release_stripe lockless
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch]raid5: make release_stripe lockless
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch]raid5: make release_stripe lockless
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] async_tx: allow generic async_memcpy() not be effected by channel switch
  • From: Dave Jiang <dave.jiang@xxxxxxxxx>
• Re: Failing Reshape
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• RE: mdadm RAID6 faulty drive
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• DDF test fails if default udev rules are active
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Strange / inconsistent behavior with mdadm -I -R
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RAID hot_replace behavior with another disk failure
  • From: Vlad Cerny <vcerny@xxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: cpu stuck when raid5 was in recovery
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Need some information about mdadm 3.2.5
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: Need some information about mdadm 3.2.5
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• cpu stuck when raid5 was in recovery
  • From: hanguozhong <hanguozhong@xxxxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Strange / inconsistent behavior with mdadm -I -R
  • From: NeilBrown <neilb@xxxxxxx>
• Possible to change chunk size on RAID-1 without re-init or destructive result?
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• Need some information about mdadm 3.2.5
  • From: Tarak Anumolu <tarak.anumolu@xxxxxxxxxxx>
• Failing Reshape
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: mdadm RAID6 faulty drive
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxxxxxx>
• Re: RAID-10 with mixed block size HDDs
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: maurice <mhilarius@xxxxxxxxx>
• [PATCH 5/8] monitor: don't call pselect() on deleted sysfs files
  • From: mwilck@xxxxxxxx
• [PATCH 6/8] monitor: read_and_act: handle race conditions for resync_start
  • From: mwilck@xxxxxxxx
• [PATCH 8/8] tests/10ddf-create: omit log output check
  • From: mwilck@xxxxxxxx
• [PATCH 7/8] monitor: treat unreadable array_state as clean
  • From: mwilck@xxxxxxxx
• [PATCH 4/8] DDF: add code to debug state changes
  • From: mwilck@xxxxxxxx
• [PATCH 3/8] DDF: brief_detail_super_ddf: print correct UUID for subarrays
  • From: mwilck@xxxxxxxx
• [PATCH 2/8] DDF: __write_init_super_ddf: just use seq number of active header
  • From: mwilck@xxxxxxxx
• [PATCH 1/8] DDF: __write_ddf_structure: Fix wrong reference to ddf->primary
  • From: mwilck@xxxxxxxx
• Fixes for DDF test case (race conditions in mdmon)
  • From: mwilck@xxxxxxxx
• Re: RAID-10 with mixed block size HDDs
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• RAID-10 with mixed block size HDDs
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Creating a RAID10 (near) for use in a CentOS 6 system
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: mdadm RAID6 faulty drive
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Creating a RAID10 (near) for use in a CentOS 6 system
  • From: maurice <mhilarius@xxxxxxxxx>
• Structure of a reshape backup file
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• mdadm RAID6 faulty drive
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Need help with my raid5
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Need help with my raid5
  • From: Mirko <mirko76@xxxxxxxx>
• Re: Need help with my raid5
  • From: Mirko <mirko76@xxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Need help with my raid5
  • From: Mirko <mirko76@xxxxxxxx>
• Re: Need help with my raid5
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Need help with my raid5
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Need help with my raid5
  • From: Mirko <mirko76@xxxxxxxx>
• Re: [patch]raid5: make release_stripe lockless
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Strange / inconsistent behavior with mdadm -I -R
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: "Andris Berzins" <pkix@xxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Western Digital Green 3TB SATA3 experiences
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Western Digital Green 3TB SATA3 experiences
  • From: "Andris Berzins" <pkix@xxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch]raid5: make release_stripe lockless
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID10: Allow skipping recovery when clean arrays are assembled
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0 of 2 - v2] DM RAID: Add message/status support for changing sync action
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch]raid5: make release_stripe lockless
  • From: Dan Williams <djbw@xxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• [PATCH] RAID10: Allow skipping recovery when clean arrays are assembled
  • From: mwilck@xxxxxxxx
• Re: Strange / inconsistent behavior with mdadm -I -R
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re[2]: SATA start unit command?
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• [PATCH 2 of 2 - v2] DM RAID: Add message/status support for changing sync action
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 1 of 2 - v2] MD: Export 'md_reap_sync_thread' function
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 0 of 2 - v2] DM RAID: Add message/status support for changing sync action
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [PATCH] DM RAID: Add message/status support for changing sync action
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Joel Young <jdy@xxxxxxxxxxxxxxx>
• Re: SATA start unit command?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• [patch]raid5: make release_stripe lockless
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: NeilBrown <neilb@xxxxxxx>
• SATA start unit command?
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: Strange / inconsistent behavior with mdadm -I -R
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID10: Allow skipping recovery when clean arrays are assembled
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [dm-devel] [PATCH] DM RAID: Add message/status support for changing sync action
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] DM RAID: Add message/status support for changing sync action
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Handling of stale array members in Linux MD
  • From: Andrey Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• [PATCH] DM RAID: Add message/status support for changing sync action
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [Fwd: Re: Missing superblock on one of the raid devices on raid 0 with 1.2 metadata]
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: [Fwd: Re: Missing superblock on one of the raid devices on raid 0 with 1.2 metadata]
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [Fwd: Re: Missing superblock on one of the raid devices on raid 0 with 1.2 metadata]
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [Fwd: Re: Missing superblock on one of the raid devices on raid 0 with 1.2 metadata]
  • From: "Ivan Yordanov" <iyordanov@xxxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• md RAID1 passes I/O errors to the filesystem despite having alive mirrors?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• [PATCH] RAID10: Allow skipping recovery when clean arrays are assembled
  • From: mwilck@xxxxxxxx
• Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Joel Young <jdy@xxxxxxxxxxxxxxx>
• Strange / inconsistent behavior with mdadm -I -R
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Missing superblock on one of the raid devices on raid 0 with 1.2 metadata
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Missing superblock on one of the raid devices on raid 0 with 1.2 metadata
  • From: "Nikolay Kichukov" <nkichukov@xxxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Putting grub back on new mirror disk
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Joel Young <jdy@xxxxxxxxxxxxxxx>
• Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Joel Young <jdy@xxxxxxxxxxxxxxx>
• Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Putting grub back on new mirror disk
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• RAID 0 of Two RAID 5s Stays Up When Component RAID fails
  • From: Joel Young <jdy@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Taysom <taysom@xxxxxxxxxx>
• [PATCH] MD: Quickly return errors if too many devices have failed.
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Taysom <taysom@xxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: [PATCH 3/4] UAPI: Fix endianness conditionals in linux/raid/md_p.h
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: Paul Bolle <pebolle@xxxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: [PATCH] MD: Prevent sysfs operations on uninitialized kobjects
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] MD RAID5: Avoid accessing gendisk or queue structs when not available
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: [PATCH] MD: Fix typos in MD documentation
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Help with two momentarily failed drives out of a 4x3TB Raid 5
  • From: Javier Marcet <jmarcet@xxxxxxxxx>
• Re: RAID performance - new kernel results
  • From: Charles Polisher <cpolish@xxxxxxxxxxxx>
• Re: [PATCH] mdadm.8.in: Fix typo: previous -> previously
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• Re: Raid 5/10 discard support broken in 3.8.2
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Raid 5/10 discard support broken in 3.8.2
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• [PATCH] mdadm.8.in: Fix typo: previous -> previously
  • From: Wieland Hoffmann <themineo@xxxxxxxxx>
• Re: Raid 5/10 discard support broken in 3.8.2
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [PATCH] MD: Fix typos in MD documentation
  • From: Joseph Glanville <joseph.glanville@xxxxxxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH] MD: Fix typos in MD documentation
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] MD: Fix typos in MD documentation
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH] MD: Fix typos in MD documentation
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH] MD: Prevent sysfs operations on uninitialized kobjects
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH] MD RAID5: Avoid accessing gendisk or queue structs when not available
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: Raid 5/10 discard support broken in 3.8.2
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Raid 5/10 discard support broken in 3.8.2
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: Raid 5/10 discard support broken in 3.8.2
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 3/4] UAPI: Fix endianness conditionals in linux/raid/md_p.h
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: DDF / RAID10 patch series for mdadm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Raid 5/10 discard support broken in 3.8.2
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: Kernel 3.7.9 RAID6 hot replace success
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Kernel 3.7.9 RAID6 hot replace success
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• Re: help with degraded raid1 array
  • From: scar <scar@xxxxxxxxxx>
• Re: Kernel 3.7.9 RAID6 hot replace success
  • From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Taysom <taysom@xxxxxxxxxx>
• Re: Kernel 3.7.9 RAID6 hot replace success
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance - 5x SSD RAID5 - effects of stripe cache sizing
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: help with degraded raid1 array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Re: [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Kernel 3.7.9 RAID6 hot replace success
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Taysom <taysom@xxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Taysom <taysom@xxxxxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: NeilBrown <neilb@xxxxxxx>
• help with degraded raid1 array
  • From: scar <scar@xxxxxxxxxx>
• Problem creating raid10 f2 with 2 disks missing
  • From: Emilio Hodge <whiz@xxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• [PATCH] md: dm-verity: Fix to avoid a deadlock in dm-bufio
  • From: Paul Taysom <taysom@xxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• raid5 lockups post ca64cae96037de16e4af92678814f5d4bf0c1c65
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] imsm: Add NO_IMSM_PLATFORM flag description to manual.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Periodically scanning RAID arrays for inconsistencies
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: DDF / RAID10 patch series for mdadm
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH V1] raid1: rewrite the iobarrier
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH 1/4] md/raid5: Reduce one write-operation when handle badsector
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH 1/4] md/raid5: Reduce one write-operation when handle badsector
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH 4/4] md: Add prompt message about wantreplacement disk in /proc/mdstat
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH 1/4] md/raid5: Reduce one write-operation when handle badsector
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH 2/4] md/raid5: Tune judgements order.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/4] md/raid5: Reduce one write-operation when handle badsector
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH] md: use set_bit_le and clear_bit_le
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md updates for 3.9
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Persistent failures with simple md setup
  • From: NeilBrown <neilb@xxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• About SSDs
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Periodically scanning RAID arrays for inconsistencies
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] md: use set_bit_le and clear_bit_le
  • From: Akinobu Mita <akinobu.mita@xxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 12/12] Detail.c: call load_container for container subarrays
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• [PATCH 03/12] DDF: increase seq number when writing meta data
  • From: mwilck@xxxxxxxx
• DDF / RAID10 patch series for mdadm
  • From: mwilck@xxxxxxxx
• [PATCH 05/12] DDF: load_ddf_local: store VD conf for other BVDs
  • From: mwilck@xxxxxxxx
• [PATCH 08/12] DDF: container_content_ddf: handle RAID layout for RAID10
  • From: mwilck@xxxxxxxx
• [PATCH 09/12] DDF: __write_init_super_ddf: use correct VD conf
  • From: mwilck@xxxxxxxx
• [PATCH 01/12] DDF: cleanly save the secondary DDF structure
  • From: mwilck@xxxxxxxx
• [PATCH 02/12] DDF: use existing locations for primary and secondary DDF structure
  • From: mwilck@xxxxxxxx
• [PATCH 06/12] DDF: container_content_ddf: change array disk search loop
  • From: mwilck@xxxxxxxx
• [PATCH 10/12] DDF: add sanity checks in compare_super_ddf
  • From: mwilck@xxxxxxxx
• [PATCH 07/12] DDF: container_content_ddf: check for secondary RAID
  • From: mwilck@xxxxxxxx
• [PATCH 04/12] DDF: added other_bvd to struct vcl
  • From: mwilck@xxxxxxxx
• [PATCH 11/12] DDF: compare_super_ddf: merge local info of other superblock
  • From: mwilck@xxxxxxxx
• [PATCH 12/12] Detail.c: call load_container for container subarrays
  • From: mwilck@xxxxxxxx
• Re: Periodically scanning RAID arrays for inconsistencies
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Periodically scanning RAID arrays for inconsistencies
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [dm-devel] [patch] dm-cache-target: check for allocation failure
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• [patch] dm-cache-target: check for allocation failure
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: RAID performance - new kernel results
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Expanding array with multiple devices
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: NeilBrown <neilb@xxxxxxx>
• Expanding array with multiple devices
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• [PATCH 1/4] md/raid5: Reduce one write-operation when handle badsector
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/4] md/raid5: Tune judgements order.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 3/4] md: Don't do normal-write on unresync area of replacement-disk.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 4/4] md: Add prompt message about wantreplacement disk in /proc/mdstat
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: Rocketraid 640 raid 5 disabled
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Rocketraid 640 raid 5 disabled
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Corrupted FS after recovery. Coincidence?
  • From: Jamie Thompson <jamierocks@xxxxxxxxx>
• Re: Corrupted FS after recovery. Coincidence?
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Corrupted FS after recovery. Coincidence?
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Corrupted FS after recovery. Coincidence?
  • From: Jamie Thompson <jamierocks@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Persistent failures with simple md setup
  • From: Hans-Peter Jansen <hpj@xxxxxxxxx>
• Re: Rocketraid 640 raid 5 disabled
  • From: Khurram Hassan <kfhassan@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Rocketraid 640 raid 5 disabled
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Rocketraid 640 raid 5 disabled
  • From: Khurram Hassan <kfhassan@xxxxxxxxx>
• Re: [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: Dan Williams <djbw@xxxxxx>
• When does RAID synchronization status update?
  • From: "Dr. Greg Wettstein" <greg@xxxxxxxxxxxxxxxxx>
• Re: Damage when growing RAID 5 array
  • From: Kevin McAreavey <kevin.mcareavey@xxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: Joe Lawrence <Joe.Lawrence@xxxxxxxxxxx>
• Re: Damage when growing RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Damage when growing RAID 5 array
  • From: Kevin McAreavey <kevin.mcareavey@xxxxxxxxx>
• Re: Damage when growing RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Damage when growing RAID 5 array
  • From: Kevin McAreavey <kevin.mcareavey@xxxxxxxxx>
• Re: Functioning of --backup-file prior to array growth.
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Functioning of --backup-file prior to array growth.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: Damage when growing RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Backport Linux 3.7 MD RAID TRIM to Centos 6.3
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: Slow RAID 5 performance all of a sudden
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: Slow RAID 5 performance all of a sudden
  • From: Divan Santana <divan@xxxxxxxxxxxxxxxx>
• Damage when growing RAID 5 array
  • From: Kevin McAreavey <kevin.mcareavey@xxxxxxxxx>
• Re: Slow RAID 5 performance all of a sudden
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Slow RAID 5 performance all of a sudden
  • From: Divan Santana <divan@xxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: "stone@xxxxxxxxx" <stone@xxxxxxxxx>
• Re-sync in RAID 1 with bitmap setting issue
  • From: szlin <lin.sunze@xxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: NeilBrown <neilb@xxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: RAID performance - new kernel results
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• [PATCH] md/raid456: remove depends on CONFIG_EXPERIMENTAL
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• help needed - broken raid 1 array - I think I messed up
  • From: anon20120409 <anon20120409@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: Joe Lawrence <Joe.Lawrence@xxxxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance
  • From: Charles Polisher <cpolish@xxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: majianpeng <kedacomkernel@xxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: "stone@xxxxxxxxx" <stone@xxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: Joe Lawrence <Joe.Lawrence@xxxxxxxxxxx>
• BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Brocken Raid & LUKS
  • From: "stone@xxxxxxxxx" <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH linux-next v2] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: "stone@xxxxxxxxx" <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [dm-devel] [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: "stone@xxxxxxxxx" <stone@xxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Joseph Glanville <joseph.glanville@xxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• Re: [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• Re: [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• [PATCH linux-next] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Stone <stone@xxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Re: [RFC PATCH V1] raid1: rewrite the iobarrier
  • From: majianpeng <majianpeng@xxxxxxxxx>
• updated the https://raid.wiki.kernel.org/index.php/RAID_Recovery wiki
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: NeilBrown <neilb@xxxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Usefulness of RAID 4
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Brocken Raid & LUKS
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Brocken Raid & LUKS
  • From: "stone@xxxxxxxxx" <stone@xxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Re: [PATCH V1] raid5: Correct some failed-stripe because the badsector.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: Raid 6, 9 1.5T days drives, 2 "fail" one after the other
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Usefulness of RAID 4
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Raid 6, 9 1.5T days drives, 2 "fail" one after the other
  • From: NeilBrown <neilb@xxxxxxx>
• Re: problems formatting raid5
  • From: Emilio Hodge <whiz@xxxxxxx>
• Re: problems formatting raid5
  • From: Emilio Hodge <whiz@xxxxxxx>
• Re: problems formatting raid5
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: problems formatting raid5
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: problems formatting raid5
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID performance - new kernel results - 5x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: problems formatting raid5
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• [PATCH] imsm: Add NO_IMSM_PLATFORM flag description to manual.
  • From: Marcin Tomczak <marcin.tomczak@xxxxxxxxx>
• Re: problems formatting raid5
  • From: sk <sdk0084@xxxxxxxxx>
• Re: Best practice for large storage?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: problems formatting raid5
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: problems formatting raid5
  • From: sk <sdk0084@xxxxxxxxx>
• Re: problems formatting raid5
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• problems formatting raid5
  • From: sk <sdk0084@xxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance - new kernel results
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance - *Slow SSDs likely solved*
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID performance - *Slow SSDs likely solved*
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID10 layout question
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• RAID10 layout question
  • From: Chris Jones <cmsj@xxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Best practice for large storage?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: RAID performance
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Growing a raid60 (Was: Re: Best practice for large storage?)
  • From: Daniel Browning <db@xxxxxxxxx>
• Re: RAID performance
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: Best practice for large storage?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Best practice for large storage?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID performance
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: Joe Lawrence <Joe.Lawrence@xxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Best practice for large storage?
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• Best practice for large storage?
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Possible to rescue SW Raid5 with 2 missing Disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• raid5 slowpath warning?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: Joe Lawrence <Joe.Lawrence@xxxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Shrinking raid array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Shrinking raid array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid/device failure
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: mdadm: hot remove failed for /dev/sdg: Device or resource busy
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Set disk faulty / hot disk remove ioctl bug for read-only MD?
  • From: Joe Lawrence <Joe.Lawrence@xxxxxxxxxxx>
• Re: Shrinking raid array
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Shrinking raid array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Shrinking raid array
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Shrinking raid array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Shrinking raid array
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Size inconsistencies and rounding errors
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Shrinking raid array
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• decreasing array size --re-add fails
  • From: Tobias Gunkel <tobias.gunkel@xxxxxxxxx>
• decreasing array --re-add fails
  • From: Tobias Gunkel <tobias.gunkel@xxxxxxxxxxxxxxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: Unable to reactivate a RAID10 mdadm device
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Unable to reactivate a RAID10 mdadm device
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID1 lockup over multipath devices?
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: RAID performance
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: raid/device failure
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: RAID performance
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• RAID1 lockup over multipath devices?
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: [PATCH] mdadm: fix portability issues encountered while building against musl libc
  • From: John Spencer <maillist-mdadm@xxxxxxxxxxx>
• Re: help please, can't mount/recover raid 5 array
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: help please, can't mount/recover raid 5 array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: help please, can't mount/recover raid 5 array
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: [PATCHv2 2/2] udev: Fix order of execution of the md rules
  • From: Thomas Bächler <thomas@xxxxxxxxxxxxx>
• Re: raid/device failure
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: raid/device failure
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: raid/device failure
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: RAID performance
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid/device failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: raid/device failure
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: raid/device failure
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: raid/device failure
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: raid/device failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• raid/device failure
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: [PATCHv2 2/2] udev: Fix order of execution of the md rules
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] Modernize udev rules
  • From: NeilBrown <neilb@xxxxxxx>
• Re: help please, can't mount/recover raid 5 array
  • From: Dave Cundiff <syshackmin@xxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Possible to rescue SW Raid5 with 2 missing Disks
  • From: "Dragon" <Sunghost@xxxxxx>
• Re: help please, can't mount/recover raid 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5 with 2 drive failure at the same time
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• Re: RAID performance
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: help please, can't mount/recover raid 5 array
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>