Linux RAID Storage Date Index

Thread Index

Re: RAID6 check found different events, how should I proceed?
- From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
Re: RAID6 check found different events, how should I proceed?
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: RAID6 check found different events, how should I proceed?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
RAID6 check found different events, how should I proceed?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: mdadm forces resync every boot
- From: Erwan Leroux <erwan.lerou@xxxxxxxxx>
Re: LUKS superblock damaged by `mdadm --create` or user error?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Need help recovering RAID5 array
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: segfault when killing subarray of non-existent container
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Need help recovering RAID5 array
- From: Stephen Muskiewicz <stephen_muskiewicz@xxxxxxx>
mdadm forces resync every boot
- From: Daniel Frey <djqfrey@xxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: NeilBrown <neilb@xxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Re: LUKS superblock damaged by `mdadm --create` or user error?
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
LUKS superblock damaged by `mdadm --create` or user error?
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
Re: [PATCH] md: use REQ_NOIDLE flag in md_super_write()
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] md/raid5: STRIPE_ACTIVE has lock semantics, add barriers
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[PATCH] md: use REQ_NOIDLE flag in md_super_write()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Mdadm re-add fails
- From: NeilBrown <neilb@xxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: NeilBrown <neilb@xxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Mdadm re-add fails
- From: Jan Vejvalka <jan.vejvalka@xxxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md/raid1: factor out common bio handling code
- From: NeilBrown <neilb@xxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH] md/raid1: factor out common bio handling code
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Grub-install, superblock corrupted/erased and other animals
- From: NeilBrown <neilb@xxxxxxx>
Re: Assembling array with missing members
- From: Alex <mysqlstudent@xxxxxxxxx>
Re: component device mismatches found: 9600
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: component device mismatches found: 9600
- From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
Re: component device mismatches found: 9600
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: component device mismatches found: 9600
- From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
[PATCH] fix: segfault when killing subarray of non-existent container
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: Assembling array with missing members
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Assembling array with missing members
- From: Alex <mysqlstudent@xxxxxxxxx>
Re: Assembling array with missing members
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Assembling array with missing members
- From: Alex <mysqlstudent@xxxxxxxxx>
Re: linux-next: build warnings after merge of the moduleh tree
- From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Re: Do I have a bad HDD?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Do I have a bad HDD?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: component device mismatches found: 9600
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Do I have a bad HDD?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Do I have a bad HDD?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
component device mismatches found: 9600
- From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
Re: Do I have a bad HDD?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Do I have a bad HDD?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Do I have a bad HDD?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Do I have a bad HDD?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: linux-next: build warnings after merge of the moduleh tree
- From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx>
Re: upgrading the superblock version
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: data scrubbing
- From: Beolach <beolach@xxxxxxxxx>
Re: data scrubbing
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: data scrubbing
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: data scrubbing
- From: Beolach <beolach@xxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
Re: data scrubbing
- From: Thomas Harold <thomas-lists@xxxxxxxxxx>
Failures Rates Using SSD
- From: maurice <mhilarius@xxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Doug Ledford <dledford@xxxxxxxxxx>
RE: RE: RAID5/6 Offload via IOATDMA
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: data scrubbing
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: data scrubbing
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
data scrubbing
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
linux-next: build warnings after merge of the moduleh tree
- From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
Re: RE: RAID5/6 Offload via IOATDMA
- From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
RE: RAID5/6 Offload via IOATDMA
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
RAID5/6 Offload via IOATDMA
- From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: Michal Soltys <soltys@xxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: Lutz Vieweg <lvml@xxxxxx>
Re: [md PATCH 16/36] md/raid1: factor several functions out or raid1d()
- From: NeilBrown <neilb@xxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: NeilBrown <neilb@xxxxxxx>
[Patch mdadm-3.2.2] Fix readding of a readwrite drive into a writemostly array
- From: Doug Ledford <dledford@xxxxxxxxxx>
[Patch mdadm-3.2.2] Fix the fix for the readd bug
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: [md PATCH 16/36] md/raid1: factor several functions out or raid1d()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 15/36] md/raid1: improve handling of read failure during recovery.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 14/36] md/raid1: record badblocks found during resync etc.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 13/36] md/raid1: Handle write errors by updating badblock log.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 12/36] md/raid1: store behind-write pages in bi_vecs.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: Lutz Vieweg <lvml@xxxxxx>
Grub-install, superblock corrupted/erased and other animals
- From: Aaron Scheiner <blue@xxxxxxxxxxxxxx>
Re: [patch] md/raid10: double lock typo in handle_read_error()
- From: NeilBrown <neilb@xxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[patch] md/raid10: double lock typo in handle_read_error()
- From: Dan Carpenter <error27@xxxxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: keld@xxxxxxxxxx
Re: Using the new bad-block-log in md for Linux 3.1
- From: NeilBrown <neilb@xxxxxxx>
Re: Using the new bad-block-log in md for Linux 3.1
- From: keld@xxxxxxxxxx
Re: standard performance (write speed 20Mb/s)
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: [md PATCH 11/36] md/raid1: clear bad-block record when write succeeds.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 10/36] md/raid1: avoid writing to known-bad blocks on known-bad drives.
- From: NeilBrown <neilb@xxxxxxx>
Using the new bad-block-log in md for Linux 3.1
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 10/36] md/raid1: avoid writing to known-bad blocks on known-bad drives.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 09/36] md: make it easier to wait for bad blocks to be acknowledged.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log.
- From: NeilBrown <neilb@xxxxxxx>
Re: Repairing a Raid-6 array
- From: Phil Turmel <philip@xxxxxxxxxx>
Repairing a Raid-6 array
- From: Lemur Kryptering <gottail@xxxxxxxxxxxxx>
Re: [md PATCH 09/36] md: make it easier to wait for bad blocks to be acknowledged.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 08/36] md: add 'write_error' flag to component devices.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH v2] md: add documentation for bad block log
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: [md PATCH 07/36] md/raid1: avoid reading known bad blocks during resync
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 06/36] md/raid1: avoid reading from known bad blocks.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Problems with raid after reboot.
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [PATCH] RAID-6 check standalone suspend array V2.0
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 01/36] md: beginnings of bad block management.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [PATCH] mdadm.8: Disk coercion with IMSM metadata.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 20/34] md/raid5: finalise new merged handle_stripe.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [PATCH] Grow: fix version number in error message
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 01/36] md: beginnings of bad block management.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Re: [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 01/36] md: beginnings of bad block management.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 20/34] md/raid5: finalise new merged handle_stripe.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 19/34] md/raid5: move some more common code into handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 14/34] md/raid5: move more code into common handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 13/34] md/raid5: Move code for finishing a reconstruction into handle_stripe.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 11/34] md/raid5: add some more fields to stripe_head_state
- From: NeilBrown <neilb@xxxxxxx>
RAID5/6 Offload
- From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
Re: Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: Problems with raid after reboot.
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Michael Tokarev <mjt@xxxxxxxxxx>
Re: [PATCH] RAID-6 check standalone suspend array V2.0
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: [RFC PATCH 4/4] btrfs: Moved repair code from inode.c to extent_io.c
- From: Jan Schmidt <list.btrfs@xxxxxxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: maurice <mhilarius@xxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: maurice <mhilarius@xxxxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: Vasco Névoa <vasco.nevoa@xxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Michael Tokarev <mjt@xxxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: maurice <mhilarius@xxxxxxxxx>
Re: Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: [md PATCH 05/36] md: Disable bad blocks and v0.90 metadata.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 01/36] md: beginnings of bad block management.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 04/36] md: load/store badblock list from v1.x metadata
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [dm-devel] [PATCH -next] dm: fix dm-flakey printk warning
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [md PATCH 03/36] md: don't allow arrays to contain devices with bad blocks.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 01/36] md: beginnings of bad block management.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: standard performance (write speed 65Mb/s)
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: [md PATCH 20/34] md/raid5: finalise new merged handle_stripe.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 19/34] md/raid5: move some more common code into handle_stripe
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 18/34] md/raid5: move more common code into handle_stripe
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 16/34] md/raid5: unite fetch_block5 and fetch_block6
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: standard performance (write speed ??Mb/s) - new raid5 array
- From: Erwan Leroux <erwan.lerou@xxxxxxxxx>
Re: [md PATCH 15/34] md/raid5: rearrange a test in fetch_block6.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 14/34] md/raid5: move more code into common handle_stripe
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Luca Berra <bluca@xxxxxxxxxx>
Re: [md PATCH 13/34] md/raid5: Move code for finishing a reconstruction into handle_stripe.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: standard performance (write speed ??Mb/s) - new raid5 array
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: [PATCH] RAID-6 check standalone suspend array V2.0
- From: Luca Berra <bluca@xxxxxxxxxx>
Re: [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 12/34] md/raid5: move stripe_head_state and more code into handle_stripe.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 11/34] md/raid5: add some more fields to stripe_head_state
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Confusion with setting up new RAID6 with mdadm
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 1/1] md: style/readability cleanups
- From: Calvin Owens <jcalvinowens@xxxxxxxxx>
Re: [md PATCH 09/34] md/raid5: move common code into handle_stripe
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 07/34] md/raid5: Protect some more code with ->device_lock.
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [md PATCH 06/34] md/raid5: Remove use of sh->lock in sync_request
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Confusion with setting up new RAID6 with mdadm
- From: Tanguy Herrmann <dolanor@xxxxxxxxx>
Re: [dm-devel] linux-next: Tree for July 21 (drivers/md/dm-raid)
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: standard performance (write speed 65Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: standard performance (write speed ??Mb/s) - new raid5 array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH -next] dm: fix dm-flakey printk warning
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
Re: linux-next: Tree for July 21 (drivers/md/dm-raid)
- From: NeilBrown <neilb@xxxxxxx>
Re: linux-next: Tree for July 21 (drivers/md/dm-raid)
- From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
Re: standard performance (write speed 65Mb/s)
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: standard performance (write speed ??Mb/s) - new raid5 array
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: upgrading the superblock version
- From: Vasco Névoa <vasco.nevoa@xxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Erwan Leroux <erwan.lerou@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Erwan Leroux <erwan.lerou@xxxxxxxxx>
Re: Raid5 boot failure after grow
- From: Shaun Reich <predator106@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: mdadm striped parity RAID with Advanced Format drives
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
mdadm striped parity RAID with Advanced Format drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Raid5 boot failure after grow
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
upgrading the superblock version
- From: Vasco Névoa <vasco.nevoa@xxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Erwan Leroux <erwan.lerou@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
[md PATCH 36/36] md/raid10: handle further errors during fix_read_error better.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 35/36] md/raid10: Handle read errors during recovery better.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 34/36] md/raid10: simplify read error handling during recovery.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 33/36] md/raid10: record bad blocks due to write errors during resync/recovery.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 32/36] md/raid10: attempt to fix read errors during resync/check
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 31/36] md/raid10: Handle write errors by updating badblock log.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 30/36] md/raid10: clear bad-block record when write succeeds.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 29/36] md/raid10: avoid writing to known bad blocks on known bad drives.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 28/36] md/raid10 record bad blocks as needed during recovery.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 27/36] md/raid10: avoid reading known bad blocks during resync/recovery.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 26/36] md/raid10 - avoid reading from known bad blocks - part 3
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 25/36] md/raid10: avoid reading from known bad blocks - part 2
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 24/36] md/raid10: avoid reading from known bad blocks - part 1
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 23/36] md/raid10: Split handle_read_error out from raid10d.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 22/36] md/raid10: simplify/reindent some loops.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 21/36] md/raid5: Clear bad blocks on successful write.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 20/36] md/raid5. Don't write to known bad block on doubtful devices.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 19/36] md/raid5: write errors should be recorded as bad blocks if possible.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 18/36] md/raid5: use bad-block log to improve handling of uncorrectable read errors.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 17/36] md/raid5: avoid reading from known bad blocks.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 16/36] md/raid1: factor several functions out or raid1d()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 15/36] md/raid1: improve handling of read failure during recovery.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 14/36] md/raid1: record badblocks found during resync etc.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 13/36] md/raid1: Handle write errors by updating badblock log.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 12/36] md/raid1: store behind-write pages in bi_vecs.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 11/36] md/raid1: clear bad-block record when write succeeds.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 10/36] md/raid1: avoid writing to known-bad blocks on known-bad drives.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 09/36] md: make it easier to wait for bad blocks to be acknowledged.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 08/36] md: add 'write_error' flag to component devices.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 07/36] md/raid1: avoid reading known bad blocks during resync
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 06/36] md/raid1: avoid reading from known bad blocks.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 05/36] md: Disable bad blocks and v0.90 metadata.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 04/36] md: load/store badblock list from v1.x metadata
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 03/36] md: don't allow arrays to contain devices with bad blocks.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 01/36] md: beginnings of bad block management.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 00/36] md patches for 3.1 - part 2: bad block logs
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 34/34] MD bitmap: Revert DM dirty log hooks
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 33/34] MD: raid1 s/sysfs_notify_dirent/sysfs_notify_dirent_safe
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 32/34] md/raid5: Avoid BUG caused by multiple failures.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 31/34] md/raid10: move rdev->corrected_errors counting
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 30/34] md/raid5: move rdev->corrected_errors counting
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 29/34] md/raid1: move rdev->corrected_errors counting
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 28/34] md: get rid of unnecessary casts on page_address()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 27/34] md/raid10: Improve decision on whether to fail a device with a read error.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 26/34] md/raid10: Make use of new recovery_disabled handling
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 25/34] md: change managed of recovery_disabled.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 24/34] md: remove ro check in md_check_recovery()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 23/34] md: introduce link/unlink_rdev() helpers
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 22/34] md/raid: use printk_ratelimited instead of printk_ratelimit
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 21/34] md: use proper little-endian bitops
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 20/34] md/raid5: finalise new merged handle_stripe.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 19/34] md/raid5: move some more common code into handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 18/34] md/raid5: move more common code into handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 16/34] md/raid5: unite fetch_block5 and fetch_block6
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 15/34] md/raid5: rearrange a test in fetch_block6.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 14/34] md/raid5: move more code into common handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 13/34] md/raid5: Move code for finishing a reconstruction into handle_stripe.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 12/34] md/raid5: move stripe_head_state and more code into handle_stripe.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 11/34] md/raid5: add some more fields to stripe_head_state
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 09/34] md/raid5: move common code into handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 07/34] md/raid5: Protect some more code with ->device_lock.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 06/34] md/raid5: Remove use of sh->lock in sync_request
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 05/34] md/raid5: get rid of duplicated call to bio_data_dir()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 04/34] md/raid5: use kmem_cache_zalloc()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 03/34] md/raid10: share pages between read and write bio's during recovery
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 02/34] md/raid10: factor out common bio handling code
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 01/34] md/raid10: get rid of duplicated conditional expression
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 00/34] md patches for 3.1 - part 1
- From: NeilBrown <neilb@xxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Problems with raid after reboot.
- From: Matthew Tice <mjtice@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: "Pol Hallen" <raid1@xxxxxxxxxxxxxx>
Re: [PATCH] MD: generate an event when array sync is complete
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: [PATCH] RAID-6 check standalone suspend array V2.0
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Raid5 boot failure after grow
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid5 boot failure after grow
- From: Shaun Reich <predator106@xxxxxxxxx>
RE: RAID 1 using SSD and 2 HDD
- From: <brian.foster@xxxxxxx>
RE: [PATCH] mdadm.8: Disk coercion with IMSM metadata.
- From: "Naruszewicz, Maciej" <maciej.naruszewicz@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Werner Fischer <devlists@xxxxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: data corruption after rebuild
- From: Pavel Herrmann <morpheus.ibis@xxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: data corruption after rebuild
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] MD bitmap: Revert DM dirty log hooks
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] MD: generate an event when array sync is complete
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] MD: raid1 s/sysfs_notify_dirent/sysfs_notify_dirent_safe
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 boot failure after grow
- From: Phil Turmel <philip@xxxxxxxxxx>
Raid5 boot failure after grow
- From: Shaun Reich <predator106@xxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Mike Power <mpower@xxxxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: RAID 1 using SSD and 2 HDD
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
RAID 1 using SSD and 2 HDD
- From: Mike Power <mpower@xxxxxxxxxxxx>
Re: data corruption after rebuild
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: data corruption after rebuild
- From: Pavel Herrmann <morpheus.ibis@xxxxxxxxx>
Re: data corruption after rebuild
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: data corruption after rebuild
- From: Pavel Herrmann <morpheus.ibis@xxxxxxxxx>
Re: data corruption after rebuild
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: data corruption after rebuild
- From: Pavel Herrmann <morpheus.ibis@xxxxxxxxx>
Re: data corruption after rebuild
- From: Pavel Herrmann <morpheus.ibis@xxxxxxxxx>
Re: data corruption after rebuild
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
data corruption after rebuild
- From: Pavel Herrmann <morpheus.ibis@xxxxxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: how to recover filesystem after clobbering array?
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
maybe a raid10 module issue?
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: Vasco Névoa <vasco.nevoa@xxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: how to recover filesystem after clobbering array?
- From: Vasco Névoa <vasco.nevoa@xxxxxxx>
how to recover filesystem after clobbering array?
- From: Vasco Névoa <vasco.nevoa@xxxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
[PATCH] Grow: fix version number in error message
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
SSDs vs. md/sync_speed_(min|max)
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
md stuck while rebuilding?
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: Software RAID and TRIM
- From: Werner Fischer <devlists@xxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: Software RAID and TRIM
- From: Lutz Vieweg <lvml@xxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Gordon Henderson <gordon@xxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Iustin Pop <iusty@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Iustin Pop <iusty@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: "Pol Hallen" <raid1@xxxxxxxxxxxxxx>
Re: standard performance (write speed 20Mb/s)
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
standard performance (write speed 20Mb/s)
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: [PATCH] mdadm.8: Disk coercion with IMSM metadata.
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[PATCH] MD bitmap: Revert DM dirty log hooks
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH] MD: generate an event when array sync is complete
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
[PATCH] MD: raid1 s/sysfs_notify_dirent/sysfs_notify_dirent_safe
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: possible bug in md
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
sys/time.h missing from linux/raid/pq.h for userspace builds
- From: Jaakko Kantojärvi <jaakko@xxxxxxxxx>
Re: Reinstall OS Without Disturbing Software Raid Array
- From: Simon Mcnair <simonmcnair@xxxxxxxxx>
Re: [PATCH 3/3] md/raid10: move rdev->corrected_errors counting
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md: get rid of unnecessary casts on page_address()
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: FIX: getinfo_super_imsm_volume() doesn't fill all disk information
- From: NeilBrown <neilb@xxxxxxx>
Re: possible bug in md
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] mdadm: fix build failures (ppc64)
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md: remove ro check in md_check_recovery()
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH v2] md: introduce link/unlink_rdev() helpers
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] mdadm.8: Disk coercion with IMSM metadata.
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] mdadm.8: Disk coercion with IMSM metadata.
- From: "maciej.naruszewicz" <maciej.naruszewicz@xxxxxxxxx>
RE: mdadm 3.1.4 - hanging on cat /proc/mdstat
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
mdadm 3.1.4 - hanging on cat /proc/mdstat
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
RE: Resolving mdadm built RAID issue
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
RE: Resolving mdadm built RAID issue
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
RE: Resolving mdadm built RAID issue
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
Re: Reinstall OS Without Disturbing Software Raid Array
- From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
Re: Reinstall OS Without Disturbing Software Raid Array
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: Reinstall OS Without Disturbing Software Raid Array
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Reinstall OS Without Disturbing Software Raid Array
- From: Noah Swint <noah.swint@xxxxxxxxx>
Fwd: [PATCH] md: remove ro check in md_check_recovery()
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
Re: Resolving mdadm built RAID issue
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Resolving mdadm built RAID issue
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Luca Berra <bluca@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
[PATCH v2] md: introduce link/unlink_rdev() helpers
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH] md: introduce link/unlink_rdev() helpers
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH] md: remove ro check in md_check_recovery()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Help with recovering resized raid where machine crashed while PENDING
- From: Petter Reinholdtsen <pere@xxxxxxxxxx>
[PATCH] mdadm: fix build failures (ppc64)
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: dm-crypt over raid6 unreadable after crash
- From: Phil Turmel <philip@xxxxxxxxxx>
dm-crypt over raid6 unreadable after crash
- From: Louis-David Mitterrand <vindex+lists-linux-kernel@xxxxxxxxxxx>
Re: alignment of metadata 1.2 and mkfs.ext4
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: `pvmove stuck' in RH bugzilla
- From: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>
Re: `pvmove stuck' in RH bugzilla
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: alignment of metadata 1.2 and mkfs.ext4
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: alignment of metadata 1.2 and mkfs.ext4
- From: Roman Mamedov <rm@xxxxxxxxxx>
`pvmove stuck' in RH bugzilla
- From: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>
Re: alignment of metadata 1.2 and mkfs.ext4
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: alignment of metadata 1.2 and mkfs.ext4
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: alignment of metadata 1.2 and mkfs.ext4
- From: Werner Fischer <devlists@xxxxxxxx>
alignment of metadata 1.2 and mkfs.ext4
- From: "Tyler J. Wagner" <tyler@xxxxxxxxx>
alignment of metadata 1.2 and mkfs.ext4
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: Help with recovering resized raid where machine crashed while PENDING
- From: NeilBrown <neilb@xxxxxxx>
Re: possible bug in md
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
Re: Help with recovering resized raid where machine crashed while PENDING
- From: Petter Reinholdtsen <pere@xxxxxxxxxx>
Re: Curious problem with asynchronous RAID1 rebuild operations
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: Recommended sw raid setup
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
Re: Recommended sw raid setup
- From: Drew <drew.kay@xxxxxxxxx>
Re: advanced partition format, mdadm, and raw disks
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: advanced partition format, mdadm, and raw disks
- From: NeilBrown <neilb@xxxxxxx>
Re: advanced partition format, mdadm, and raw disks
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: Help with recovering resized raid where machine crashed while PENDING
- From: NeilBrown <neilb@xxxxxxx>
Re: Curious problem with asynchronous RAID1 rebuild operations
- From: NeilBrown <neilb@xxxxxxx>
Re: advanced partition format, mdadm, and raw disks
- From: NeilBrown <neilb@xxxxxxx>
Re: possible bug in md
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID and TRIM
- From: Werner Fischer <devlists@xxxxxxxx>
possible bug in md
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
advanced partition format, mdadm, and raw disks
- From: "Tyler J. Wagner" <tyler@xxxxxxxxxxx>
Re: Help with recovering resized raid where machine crashed while PENDING
- From: Petter Reinholdtsen <pere@xxxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Luca Berra <bluca@xxxxxxxxxx>
Re: Recommended sw raid setup
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Recommended sw raid setup
- From: John Obaterspok <john.obaterspok@xxxxxxxxx>
Re: Recommended sw raid setup
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Recommended sw raid setup
- From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
Re: Recommended sw raid setup
- From: Drew <drew.kay@xxxxxxxxx>
Re: Recommended sw raid setup
- From: "Scott E. Armitage" <launchpad@xxxxxxxxxxxxxxxxxxx>
Re: Recommended sw raid setup
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: Recommended sw raid setup
- From: "Scott E. Armitage" <launchpad@xxxxxxxxxxxxxxxxxxx>
Re: Recommended sw raid setup
- From: Drew <drew.kay@xxxxxxxxx>
Recommended sw raid setup
- From: John Obaterspok <john.obaterspok@xxxxxxxxx>
Curious problem with asynchronous RAID1 rebuild operations
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: David Brown <david.brown@xxxxxxxxxxxx>
Help with recovering resized raid where machine crashed while PENDING
- From: Petter Reinholdtsen <pere@xxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Karsten Römke <k.roemke@xxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
[PATCH 1/1] md: style/readability cleanups
- From: Calvin Owens <jcalvinowens@xxxxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
[PATCH] imsm: FIX: getinfo_super_imsm_volume() doesn't fill all disk information
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: NeilBrown <neilb@xxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
mdadm -git compile error
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: NeilBrown <neilb@xxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Karsten Römke <k.roemke@xxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Karsten Römke <k.roemke@xxxxxx>
Re: Antw: Re: nested block devices (partitioned RAID with LVM): where Linux sucks ;-)
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Phil Turmel <philip@xxxxxxxxxx>
[PATCH] md: get rid of unnecessary casts on page_address()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Re: misunderstanding of spare and raid devices?
- From: Karsten Römke <k.roemke@xxxxxx>
Re: Antw: Re: nested block devices (partitioned RAID with LVM): where Linux sucks ;-)
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: misunderstanding of spare and raid devices? - and one question more
- From: Karsten Römke <k.roemke@xxxxxx>
Re: misunderstanding of spare and raid devices?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: misunderstanding of spare and raid devices?
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: misunderstanding of spare and raid devices?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
misunderstanding of spare and raid devices?
- From: Karsten Römke <k.roemke@xxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: MDADM RAID5 listing active drives as spares
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID and TRIM
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID and TRIM
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: NeilBrown <neilb@xxxxxxx>
Re: Single Drive Pegged during RAID 5 synchronization
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: nested block devices (partitioned RAID with LVM): where Linux sucks ;-)
- From: Phil Turmel <philip@xxxxxxxxxx>
MDADM RAID5 listing active drives as spares
- From: Ian Whitton <boyfromthedwarf9@xxxxxxxxx>
Re: Software RAID and TRIM
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Single Drive Pegged during RAID 5 synchronization
- From: "fibreraid@xxxxxxxxx" <fibreraid@xxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: "Scott E. Armitage" <launchpad@xxxxxxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Software RAID and TRIM
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: Can't start array and Negative "Used Dev Size"
- From: NeilBrown <neilb@xxxxxxx>
Can't start array and Negative "Used Dev Size"
- From: Simon Matthews <simon.d.matthews@xxxxxxxxx>
Re: Raid auto-assembly upon boot - device order
- From: Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
[PATCH 3/3] md/raid10: move rdev->corrected_errors counting
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 2/3] md/raid5: move rdev->corrected_errors counting
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 1/3] md/raid1: move rdev->corrected_errors counting
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 0/3] count rdev->corrected_errors after final re-read
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Can reading a raid drive trigger all the other drives in that set?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: Software RAID and TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: Software RAID and TRIM
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Software RAID and TRIM
- From: Tom De Mulder <tdm27@xxxxxxxxx>
Re: Raid auto-assembly upon boot - device order
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid auto-assembly upon boot - device order
- From: Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
Re: Raid auto-assembly upon boot - device order
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid auto-assembly upon boot - device order
- From: Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
Re: [PATCH 4/8] md/raid: use printk_ratelimited instead of printk_ratelimit
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH resend 3/6] md: use proper little-endian bitops
- From: NeilBrown <neilb@xxxxxxx>
Re: [smatch stuff] md/raid5: potential null deref in debug code
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md/raid5: fix possible NULL pointer dereference in debug routine
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] mdmon.8: fix possible typos
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid auto-assembly upon boot - device order
- From: Phil Turmel <philip@xxxxxxxxxx>
Raid auto-assembly upon boot - device order
- From: Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
Re: clarifying what can be done during resync
- From: David Brown <david@xxxxxxxxxxxxxxx>
RE: clarifying what can be done during resync
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: clarifying what can be done during resync
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
[PATCH resend 3/6] md: use proper little-endian bitops
- From: Akinobu Mita <akinobu.mita@xxxxxxxxx>
[PATCH resend 0/6] use little-endian bitops properly
- From: Akinobu Mita <akinobu.mita@xxxxxxxxx>
Re: raid upgrade form 1.5T to 3T drives with 0.90 superblock
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid upgrade form 1.5T to 3T drives with 0.90 superblock
- From: NeilBrown <neilb@xxxxxxx>
[smatch stuff] md/raid5: potential null deref in debug code
- From: Dan Carpenter <error27@xxxxxxxxx>
Re: Looking for the best way to do this
- From: maurice <mhilarius@xxxxxxxxx>
Re: Looking for the best way to do this
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
Re: Looking for the best way to do this
- From: maurice <mhilarius@xxxxxxxxx>
Re: Looking for the best way to do this
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
Re: raid upgrade form 1.5T to 3T drives with 0.90 superblock
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: raid upgrade form 1.5T to 3T drives with 0.90 superblock
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH] md/raid5: fix possible NULL pointer dereference in debug routine
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 2/2] md.4: fix possible typos
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 1/2] mdmon.8: fix possible typos
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Looking for the best way to do this
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Looking for the best way to do this
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Looking for the best way to do this
- From: maurice <mhilarius@xxxxxxxxx>
RE: Issues with auto assembling or RAID10 (imsm) on boot
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
clarifying what can be done during resync
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: Looking for the best way to do this
- From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
raid upgrade form 1.5T to 3T drives with 0.90 superblock
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
can't read superblock after switching from dmraid
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: [PATCH 0/5] misc cleanups for RAID5
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Which Disks can fail?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Show DELAYED, PENDING status of resync process in "--detail"
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] mdadm --detail was incorrect for shrinking reshapes
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/4] mdadm.8: change linux version 2.6.40 -> 3.0
- From: NeilBrown <neilb@xxxxxxx>
RE: Looking for the best way to do this
- From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
Re: [PATCH 0/5] misc cleanups for RAID5
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 5/5] md/raid5: get rid of duplicated call to bio_data_dir()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 4/5] md/raid5: use r5_for_each_bio()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 3/5] md/raid5: factor out dev_need_for_write()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 2/5] md/raid5: factor out dev_need_read()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 1/5] md/raid5: use kmem_cache_zalloc()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 0/5] misc cleanups for RAID5
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: reaid problem at reboot
- From: Phil Turmel <philip@xxxxxxxxxx>
RE: reaid problem at reboot
- From: "william L'Heureux" <wil_c_will@xxxxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: NeilBrown <neilb@xxxxxxx>
Re: reaid problem at reboot
- From: Phil Turmel <philip@xxxxxxxxxx>
RE: reaid problem at reboot
- From: "william L'Heureux" <wil_c_will@xxxxxxxxxxx>
Re: reaid problem at reboot
- From: Phil Turmel <philip@xxxxxxxxxx>
RE: reaid problem at reboot
- From: "william L'Heureux" <wil_c_will@xxxxxxxxxxx>
10x2TB RAID6
- From: "Manny Street" <mann@xxxxxxxxxxxxxxxxxxxx>
Re: reaid problem at reboot
- From: Phil Turmel <philip@xxxxxxxxxx>
RE: reaid problem at reboot
- From: "william L'Heureux" <wil_c_will@xxxxxxxxxxx>
RE: reaid problem at reboot
- From: "william L'Heureux" <wil_c_will@xxxxxxxxxxx>
Re: reaid problem at reboot
- From: Phil Turmel <philip@xxxxxxxxxx>
Looking for the best way to do this
- From: maurice <mhilarius@xxxxxxxxx>
[PATCH 4/4] .gitignore: ignore mdadm.8 file
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 3/4] mdadm.8: fix possible typos
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 2/4] mdadm.8: move description of --add under Grow mode
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 1/4] mdadm.8: change linux version 2.6.40 -> 3.0
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Which Disks can fail?
- From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Mail etiquette
- From: Phillip Susi <psusi@xxxxxxxxxx>
Re: Nested RAID and booting
- From: Phillip Susi <psusi@xxxxxxxxxx>
reaid problem at reboot
- From: "william L'Heureux" <wil_c_will@xxxxxxxxxxx>
Re: Bug or not? Same array reports different/transformed UUID depending on check-method used.
- From: jeffs_linux@xxxxxxxxxxx
Re: Which Disks can fail?
- From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Re: Which Disks can fail?
- From: NeilBrown <neilb@xxxxxxx>
Re: Which Disks can fail?
- From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Re: Which Disks can fail?
- From: NeilBrown <neilb@xxxxxxx>
Which Disks can fail?
- From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Bug or not? Same array reports different/transformed UUID depending on check-method used.
- From: Luca Berra <bluca@xxxxxxxxxx>
RE: Issues with auto assembling or RAID10 (imsm) on boot
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: Issues with auto assembling or RAID10 (imsm) on boot
- From: Phil Turmel <philip@xxxxxxxxxx>
RE: Issues with auto assembling or RAID10 (imsm) on boot
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: Issues with auto assembling or RAID10 (imsm) on boot
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: flummoxed why I can't umount my md device. fuser and lsof show no files locked
- From: Phil Turmel <philip@xxxxxxxxxx>
Issues with auto assembling or RAID10 (imsm) on boot
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re: flummoxed why I can't umount my md device. fuser and lsof show no files locked
- From: Simon McNair <simonmcnair@xxxxxxxxx>
Re: flummoxed why I can't umount my md device. fuser and lsof show no files locked
- From: Roman Mamedov <rm@xxxxxxxxxx>
flummoxed why I can't umount my md device. fuser and lsof show no files locked
- From: Simon McNair <simonmcnair@xxxxxxxxx>
[PATCH] mdadm --detail was incorrect for shrinking reshapes
- From: Andrew Burgess <aab@xxxxxxxxxxx>
Newb question: Auto assembling of RAID10 (imsm) on boot
- From: "Sandra Escandor" <sescandor@xxxxxxxxxx>
Re:
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: check vs repair -- mismatch count goes up in repair, zeros in check?
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 issues
- From: Chad Walker <chad@xxxxxxxxxxxxxxxxxxxxxxx>
Re: raid6 issues
- From: NeilBrown <neilb@xxxxxxx>
[no subject]
- From: "Dragon" <Sunghost@xxxxxx>
Re: raid6 issues
- From: Chad Walker <chad@xxxxxxxxxxxxxxxxxxxxxxx>
Re: raid6 issues
- From: Chad Walker <chad@xxxxxxxxxxxxxxxxxxxxxxx>
check vs repair -- mismatch count goes up in repair, zeros in check?
- From: Rory Jaffe <rsjaffe@xxxxxxxxx>
[PATCH] Show DELAYED, PENDING status of resync process in "--detail"
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: Simon Mcnair <simonmcnair@xxxxxxxxx>
Bug or not? Same array reports different/transformed UUID depending on check-method used.
- From: jeffs_linux@xxxxxxxxxxx
Re: [PATCH/RFC] Fix resync hang after surprise removal
- From: James Paradis <jparadis@xxxxxxxxxx>
Re: [PATCH] mdadm: Linux 3.x version change
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: [PATCH] mdadm: Linux 3.x version change
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] mdadm: Linux 3.x version change
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: mdadm 3.2.1 segfaulting on boot when missing RaidDevice 0
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] gcc warnings again
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] md/raid1: factor out common bio handling code
- From: Namhyung Kim <namhyung@xxxxxxxxx>
raid6 issues
- From: Chad Walker <chad@xxxxxxxxxxxxxxxxxxxxxxx>
md0_raid5 process consuming 100% CPU on disk failure
- From: Shivani Bhope <sbhope@xxxxxxxxxx>
Re: mdadm and disk failures
- From: Mike Power <mpower@xxxxxxxxxxxx>
mdadm 3.2.1 segfaulting on boot when missing RaidDevice 0
- From: "Lawrence, Joe" <Joe.Lawrence@xxxxxxxxxxx>
Re: mark spare as active sync device?
- From: Lars Täuber <taeuber@xxxxxxx>
[PATCH] gcc warnings again
- From: Luca Berra <bluca@xxxxxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: md 3.2.1 and xfs kernel panic on Linux 2.6.38
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: mdadm and disk failures
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: mdadm and disk failures
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: mdadm and disk failures
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
mdadm and disk failures
- From: Mike Power <mpower@xxxxxxxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: md 3.2.1 and xfs kernel panic on Linux 2.6.38
- From: NeilBrown <neilb@xxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: NeilBrown <neilb@xxxxxxx>
Re: md 3.2.1 and xfs kernel panic on Linux 2.6.38
- From: NeilBrown <neilb@xxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: [PATCH/RFC] Fix resync hang after surprise removal
- From: NeilBrown <neilb@xxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: NeilBrown <neilb@xxxxxxx>
Re: mark spare as active sync device?
- From: NeilBrown <neilb@xxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: NeilBrown <neilb@xxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: [PATCH v2 1/5] md/raid10: optimize read_balance() for 'far offset' arrays
- From: NeilBrown <neilb@xxxxxxx>
[PATCH/RFC] Fix resync hang after surprise removal
- From: Jim Paradis <jparadis@xxxxxxxxxx>
Re: [PATCH v2 1/5] md/raid10: optimize read_balance() for 'far offset' arrays
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [PATCH v2 1/5] md/raid10: optimize read_balance() for 'far offset' arrays
- From: Namhyung Kim <namhyung@xxxxxxxxx>
mark spare as active sync device?
- From: Lars Täuber <taeuber@xxxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Gordon Henderson <gordon@xxxxxxxxxx>
Re: [PATCH v2 1/5] md/raid10: optimize read_balance() for 'far offset' arrays
- From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
Re: [PATCH RESEND 0/5] md/raid10 changes
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [PATCH RESEND 0/5] md/raid10 changes
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/5] md/raid10: spread read for subordinate r10bios during recovery
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH v2 1/5] md/raid10: optimize read_balance() for 'far offset' arrays
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 5/5] md/raid10: spread read for subordinate r10bios during recovery
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH v2 4/5] md/raid10: share pages between read and write bio's during recovery
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 3/5] md/raid10: factor out common bio handling code
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 2/5] md/raid10: get rid of duplicated conditional expression
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH v2 1/5] md/raid10: optimize read_balance() for 'far offset' arrays
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH RESEND 0/5] md/raid10 changes
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: [PATCH] imsm: Metadata Attributes compatibility support
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: FIX: Sometimes reshape cannot be finished
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] imsm: Metadata Attributes compatibility support
- From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
[PATCH] imsm: FIX: Sometimes reshape cannot be finished
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: [PATCH 1/4] imsm: FIX: Cannot create volume
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 1/3] md/raid5: fix raid5_set_bi_hw_segments
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH/RFC] md/multipath: implement I/O balancing
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/2] imsm: FIX: klocwork: passed dev pointer to is_gen_migration() can be NULL
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/4] FIX: Cannot create volume
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/4] imsm: FIX: Cannot create volume
- From: NeilBrown <neilb@xxxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Tim Blundell <tim.blundell@xxxxxxxxx>
[PATCH 2/3] md/raid5: fix FUA request handling in ops_run_io()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 3/3] md/raid5: remove unusual use of bio_iovec_idx()
- From: Namhyung Kim <namhyung@xxxxxxxxx>
[PATCH 1/3] md/raid5: fix raid5_set_bi_hw_segments
- From: Namhyung Kim <namhyung@xxxxxxxxx>
Re: Maximizing failed disk replacement on a RAID5 array
- From: Durval Menezes <durval.menezes@xxxxxxxxx>
Re: Maximizing failed disk replacement on a RAID5 array
- From: Durval Menezes <durval.menezes@xxxxxxxxx>
md 3.2.1 and xfs kernel panic on Linux 2.6.38
- From: "fibreraid@xxxxxxxxx" <fibreraid@xxxxxxxxx>
Re: Triple-parity raid6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Why do I get different results for 'mdadm --detail' & 'mdadm --examine' for the same array?
- From: jeffs_linux@xxxxxxxxxxx
Re: Maximizing failed disk replacement on a RAID5 array
- From: Durval Menezes <durval.menezes@xxxxxxxxx>
Re: Triple-parity raid6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Triple-parity raid6
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Triple-parity raid6
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Triple-parity raid6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Triple-parity raid6
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Triple-parity raid6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Triple-parity raid6
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
mdadm: failed to RUN_ARRAY /dev/md0: Input/output error
- From: Pol Hallen <raid1@xxxxxxxxxxxxxx>
Re: Triple-parity raid6
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Triple-parity raid6
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Disk upgrade
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re:
- From: Phil Turmel <philip@xxxxxxxxxx>
[no subject]
- From: "Dragon" <Sunghost@xxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: HDD reports errors while completing RAID6 array check
- From: Roman Mamedov <rm@xxxxxxxxxx>
HDD reports errors while completing RAID6 array check
- From: Mathias Burén <mathias.buren@xxxxxxxxx>

[Index of Archives] [Linux RAID Wiki] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux Block] [Linux IDE] [Linux SCSI] [Linux Hams] [Device Mapper] [Kernel] [Linux Admin] [Linux Net] [GFS] [RPM] [git] [Yosemite Forum] [Linux Networking]