Linux RAID Storage Date Index

• Thread Index

• MDADM after QNAP Support disaster QNAP 859 Pro
  • From: Sam van Ratt <sam.vanratt@xxxxxxx>
• [PATCH 1/5] md: When resync aborted,using ->curr_resync as the last completed request rather than ->curr_resync_completed.
  • From: kernelmail <kedacomkernel@xxxxxxxxx>
• [PATCH 2/5] md:Add place to update ->recovery_cp.
  • From: kernelmail <kedacomkernel@xxxxxxxxx>
• [PATCH 5/5] md/raid5: Using conf->max_degraded rather than 2 to determine whether there is excess compute-disks for raid4/5/6.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 4/5] md: Return proper error rather than EIO.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 3/5] md: Increase the frequency of recording checkpoint of recovery.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 0/5] Fix some trival bugs.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: mdadm: Cannot convert RAID1 of this size - reduce size to multiple of 4K first.
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Re: mdadm: Cannot convert RAID1 of this size - reduce size to multiple of 4K first.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• mdadm: Cannot convert RAID1 of this size - reduce size to multiple of 4K first.
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: Jivko Sabev <jsabev@xxxxxxxxxx>
• Subject: ANNOUNCE: mdadm 3.2.6 - A tool for managing Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] MD RAID10: Fix oops when creating RAID10 arrays via dm-raid.c
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Commit "db91ff55bdf06736b" using curr_resync_completed instead of curr_resync when interrupted the resync operation
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH] md/raid1: Initialize conf->raid_disks before using it.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid1: Initialize conf->raid_disks before using it.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Add flag MD_DISK_REPLACEMNT in kernel
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: NeilBrown <neilb@xxxxxxx>
• RE: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: hanguozhong <hanguozhong@xxxxxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Create new md devices consistently
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH] Create new md devices consistently
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: John Robinson <john.robinson@xxxxxxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: Jivko Sabev <jsabev@xxxxxxxxxx>
• Re: [PATCH 1/3] Align FAILED to test name to be parsable
  • From: g.esp@xxxxxxx
• About re-adding disk to raid which havent' bitmap
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH 1/3] Align FAILED to test name to be parsable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 4x3TB raid5 - no autodetect
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re[2]: 4x3TB raid5 - no autodetect
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: 4x3TB raid5 - no autodetect
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• 4x3TB raid5 - no autodetect
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: [PATCH 1/3] Align FAILED to test name to be parsable
  • From: g.esp@xxxxxxx
• Re: [PATCH] md faulty: use disk_stack_limits()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid device gone underneath array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/3] Allow escape by ctrl-c broken by --no-error change
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] Replace --no-error by --keep-going
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Align FAILED to test name to be parsable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Planning a bug-fix release for mdadm: mdadm 3.2.6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm: super0: do not override uuid with homehost
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: mdadm: super0: do not override uuid with homehost
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• [PATCH 3/3] Replace --no-error by --keep-going
  • From: Gilles Espinasse <g.esp@xxxxxxx>
• [PATCH 2/3] Allow escape by ctrl-c broken by --no-error change
  • From: Gilles Espinasse <g.esp@xxxxxxx>
• [PATCH 1/3] Align FAILED to test name to be parsable
  • From: Gilles Espinasse <g.esp@xxxxxxx>
• Re: Planning a bug-fix release for mdadm: mdadm 3.2.6
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• mdadm: super0: do not override uuid with homehost
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Planning a bug-fix release for mdadm: mdadm 3.2.6
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Dead three-disk RAID-5. Help?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Dead three-disk RAID-5. Help?
  • From: Ken <ravenpi@xxxxxxxxx>
• [PATCH] md faulty: use disk_stack_limits()
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• Re: Offtopic: on case
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid device gone underneath array
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Offtopic: on case (was: R: RAID6 reshape, 2 disk failures)
  • From: Carabetta Giulio <g.carabetta@xxxxxx>
• Re: raid device gone underneath array
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: raid device gone underneath array
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid device gone underneath array
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: raid device gone underneath array
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• raid device gone underneath array
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: Jivko Sabev <jsabev@xxxxxxxxxx>
• Re: Interrupted reshape -- mangled backup ?
  • From: Haakon Alstadheim <hakon.alstadheim@xxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• system hang at reboot while one disk failed in raid5
  • From: hanguozhong <hanguozhong@xxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Planning a bug-fix release for mdadm: mdadm 3.2.6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Cannot auto assemble a raid1 array on boot
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Cannot auto assemble a raid1 array on boot
  • From: Jivko Sabev <jsabev@xxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Interrupted reshape -- mangled backup ?
  • From: NeilBrown <neilb@xxxxxxx>
• Interrupted reshape -- mangled backup ?
  • From: Haakon Alstadheim <hakon.alstadheim@xxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Strange crash on Dell R720xd
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape, 2 disk failures
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RAID6 reshape, 2 disk failures
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Strange crash on Dell R720xd
  • From: Dan Williams <djbw@xxxxxx>
• Re: Strange crash on Dell R720xd
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: Strange crash on Dell R720xd
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: mdadm 3.2.5: Assemble doesn't scale correctly
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Strange crash on Dell R720xd
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: Strange crash on Dell R720xd
  • From: Borislav Petkov <bp@xxxxxxxxx>
• Re: Are piggybacking of write and redirection of read available in md driver now?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Are piggybacking of write and redirection of read available in md driver now?
  • From: hui jiao <simonjiaoh@xxxxxxxxx>
• Re: [GIT PULL] Disintegrate UAPI for raid
  • From: NeilBrown <neilb@xxxxxxx>
• Re: convert metadata version: possible/wise?
  • From: Drew <drew.kay@xxxxxxxxx>
• convert metadata version: possible/wise?
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• mdadm 3.2.5: Assemble doesn't scale correctly
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• MD hangs while removing spare
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: 4HDD Raid5 - 2 Disk fails
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: [PATCH 2/2] How about moving a code bdev->bd_invalidated = 0; into check_disk_size_change() instead of putting the code every time after check_disk_size_change().
  • From: MITSUNARI Shigeo <herumi@xxxxxxxxx>
• [PATCH 1/2] block: fs: bd_invalidated should be cleared in check_disk_size_change
  • From: MITSUNARI Shigeo <herumi@xxxxxxxxx>
• [PATCH 2/2] How about moving a code bdev->bd_invalidated = 0; into check_disk_size_change() instead of putting the code every time after check_disk_size_change().
  • From: MITSUNARI Shigeo <herumi@xxxxxxxxx>
• Re: RAID-6 problem
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: RAID-6 problem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: RAID-6 problem
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID-6 problem
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RAID-6 problem
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• [PULL REQUEST] md updates for 3.7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: hotunpluged a disk, raid5 disappeared after reboot
  • From: hanguozhong <hanguozhong@xxxxxxxxxxxx>
• Re: Re: task xfssyncd blocked while raid5 was in recovery
  • From: hanguozhong <hanguozhong@xxxxxxxxxxxx>
• Re: Assemble-Resize-Stop loop doesn't work correctly
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix tests sh too many arguments warnings
  • From: NeilBrown <neilb@xxxxxxx>
• Re: task xfssyncd blocked while raid5 was in recovery
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] Fix tests sh too many arguments warnings
  • From: Gilles Espinasse <g.esp@xxxxxxx>
• hotunpluged a disk, raid5 disappeared after reboot
  • From: GuoZhong Han <hanguozhong@xxxxxxxxxxxx>
• task xfssyncd blocked while raid5 was in recovery
  • From: GuoZhong Han <hanguozhong@xxxxxxxxxxxx>
• Assemble-Resize-Stop loop doesn't work correctly
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: Arun Khan <knura9@xxxxxxxxx>
• [GIT PULL] Disintegrate UAPI for raid
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH] md: register new md sysfs file 'uuid' read-only
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Issue recovering a md device with first 4kB lost.
  • From: Massimo Gais <massimo.gais@xxxxxx>
• Re: Issue recovering a md device with first 4kB lost.
  • From: Massimo Gais <massimo.gais@xxxxxx>
• Re: Issue recovering a md device with first 4kB lost.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Issue recovering a md device with first 4kB lost.
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: [PATCH] Fix race between removing raid1 device and I/O error handling on underlying device
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] md: register new md sysfs file 'uuid' read-only
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix race between removing raid1 device and I/O error handling on underlying device
  • From: NeilBrown <neilb@xxxxxxx>
• Issue recovering a md device with first 4kB lost.
  • From: Massimo Gais <massimo.gais@xxxxxx>
• Re: [PATCH] md: register new md sysfs file 'uuid' read-only
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH] md: register new md sysfs file 'uuid' read-only
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• [PATCH] Fix race between removing raid1 device and I/O error handling on underlying device
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re[2]: Promise SATA TX4 300 + 3TB disks?
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re[2]: Promise SATA TX4 300 + 3TB disks?
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Promise SATA TX4 300 + 3TB disks?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Promise SATA TX4 300 + 3TB disks?
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: raid repair checkpoint enhancement
  • From: NeilBrown <neilb@xxxxxxx>
• raid repair checkpoint enhancement
  • From: "Ryan, MichaelS (ENG Redmond)" <michaels.ryan@xxxxxxx>
• Re: 4HDD Raid5 - 2 Disk fails
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: 4HDD Raid5 - 2 Disk fails
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: 4HDD Raid5 - 2 Disk fails
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• 4HDD Raid5 - 2 Disk fails
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: [v3 PATCH] imsm: Allow to specify controller for --detail-platform.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: Arun Khan <knura9@xxxxxxxxx>
• Re: CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• CentOS 6.2 on partition able RAID1 (md_d0) - kernel panic with either disk not present
  • From: Arun Khan <knura9@xxxxxxxxx>
• [v3 PATCH] imsm: Allow to specify controller for --detail-platform.
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• Re: [PATCH] Add zlib license to crc32.c
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] Add zlib license to crc32.c
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [PATCH 2/6] imsm: Add --controller-path option for --detail-platform.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch] md/raid10: use correct limit variable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 rebuild stuck
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: Mark Munoz <mark.munoz@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] md: register new md sysfs file 'uuid' read-only
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 rebuild stuck
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID6 rebuild stuck
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 rebuild stuck
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID6 rebuild stuck
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: [PATCH 2/6] imsm: Add --controller-path option for --detail-platform.
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH] md: register new md sysfs file 'uuid' read-only
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] [patch] dm thin: check kmalloc in dm_deferred_set_create()
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6. [SOLVED]
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [patch] dm thin: check kmalloc in dm_deferred_set_create()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 2/6] imsm: Add --controller-path option for --detail-platform.
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6. [SOLVED]
  • From: EJ Vincent <ej@xxxxxxxxx>
• [patch] md/raid10: use correct limit variable
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 6/6] Add MD_ARRAY_SIZE for --examine --export
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/6] Display size with human_size_brief with a chosen prefix
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/6] Synchronize size calculation in human_size and human_size_brief
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/6] Fix return code for --detail-platform
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/6] imsm: Add --controller-path option for --detail-platform.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/6] imsm: Add --export option for --detail-platform
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 rebuild stuck
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: [md PATCH 01/10] md: allow a reshape operation to be reversed.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: Mark Munoz <mark.munoz@xxxxxxxxxxxxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 rebuild stuck
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: Mark Munoz <mark.munoz@xxxxxxxxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Pierre Beck <mail@xxxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: "Stefan /*St0fF*/ Hübner" <st0ff.npl@xxxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Pierre Beck <mail@xxxxxxxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdadm git does not work?
  • From: NeilBrown <neilb@xxxxxxx>
• RAID6 rebuild stuck
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• mdadm git does not work?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [md PATCH 01/10] md: allow a reshape operation to be reversed.
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [md PATCH 01/10] md: allow a reshape operation to be reversed.
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: Aaron Greenspan <aarong@xxxxxxxxxxxxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: Aaron Greenspan <aarong@xxxxxxxxxxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: "Stefan /*St0fF*/ Hübner" <st0ff.npl@xxxxxxxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: keld@xxxxxxxxxx
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
• Re: Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ Vincent <ej@xxxxxxxxx>
• Upgrade from Ubuntu 10.04 to 12.04 broken raid6.
  • From: EJ <ej@xxxxxxxxx>
• RAID10 copies and missing devices on init
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: mdadm --grow Hard Drive Size Puzzle
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: MD RAID Bug 7/15/12
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• mdadm --grow Hard Drive Size Puzzle
  • From: Aaron Greenspan <aarong@xxxxxxxxxxxxxxxxx>
• MD RAID Bug 7/15/12
  • From: Mark Munoz <mark.munoz@xxxxxxxxxxxxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• Re: [PATCH] mdadm: autodetect being run in an initramfs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdadm: autodetect being run in an initramfs
  • From: Dave Reisner <d@xxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: autodetect being run in an initramfs
  • From: Dave Reisner <d@xxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: autodetect being run in an initramfs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdadm: autodetect being run in an initramfs
  • From: Dmitrijs Ledkovs <dmitrij.ledkov@xxxxxxxxxxxx>
• Re: [PATCH] mdadm: autodetect being run in an initramfs
  • From: Dmitrijs Ledkovs <dmitrij.ledkov@xxxxxxxxxxxx>
• [PATCH] mdadm: autodetect being run in an initramfs
  • From: Dave Reisner <dreisner@xxxxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] 2 bugfixes for md in 3.6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• RE: [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• [PATCH 6/6] Add MD_ARRAY_SIZE for --examine --export
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH 5/6] Display size with human_size_brief with a chosen prefix
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH 4/6] Synchronize size calculation in human_size and human_size_brief
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH 3/6] Fix return code for --detail-platform
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH 2/6] imsm: Add --controller-path option for --detail-platform.
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH 1/6] imsm: Add --export option for --detail-platform
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [mdadm,v1 PATCH 0/6] Extend mdadm [...] --export
  • From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
• [PATCH] dm persistent data: convert to use le32_add_cpu()
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: keld@xxxxxxxxxx
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: keld@xxxxxxxxxx
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: John Robinson <john.robinson@xxxxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: keld@xxxxxxxxxx
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [RFC PATCH] raid5: Correct some failed-stripe which because the badsector.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: sync action not working/ignored
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH] raid5: Correct some failed-stripe which because the badsector.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: keld@xxxxxxxxxx
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: <jakub@xxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• RE: [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] raid5: Fix to_read/to_write judgement.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: NeilBrown <neilb@xxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing silent data corruption
  • From: Jakub Husák <jakub@xxxxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• bug: 4-disk md raid10 far2 can be assembled clean with only two disks, causing "silent" data corruption
  • From: Jakub Husák <jakub@xxxxxxxxxxx>
• Re: sync action not working/ignored
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Hello,Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Hello,Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: sync action not working/ignored
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• sync action not working/ignored
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Shouldn't --zero-superblock reset the UUID?
  • From: "mirovis" <mirovis@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• [RFC PATCH] raid5: Correct some failed-stripe which because the badsector.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 3/3] raid5: Fix to_read/to_write judgement.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 2/3] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 1/3] raid5: Add per-stripe lock on toread in func
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 0/3] raid5: fix three bugs.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Shouldn't --zero-superblock reset the UUID?
  • From: "mirovis" <mirovis@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• hung in raise_barrier() in raid1.c -- any ideas?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• RAID array on block device vs. on partition
  • From: "Andrew Dedesko" <adedesko@xxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Re: [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [PATCH] md: Add two chances to update sync/recovery checkpoint
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md: Add two chances to update sync/recovery checkpoint
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [PATCH] md/bitmap:Don't use IS_ERR to judge alloc_page().
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [PATCH - v2] DM RAID: Fix for ineffective "sync" directive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: imsm: re-enable size expansion to the max value
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: adjust parse_size() to the unsigned size variable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: imsm: do not accept too small sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix segfaults in Detail()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Kasper Sandberg <kontakt@xxxxxxxxxxxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Ferry <iscsitmp@xxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: freaky <freaky@xxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: freaky <freaky@xxxxxxxxxxxxx>
• GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Can't reshape RAID1 to RAID5 due to chunk size
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Arne Redlich <arne.redlich@xxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can't reshape RAID1 to RAID5 due to chunk size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PULL REQUEST] 3 fixes for md in 3.6.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Stop IMSM verify?
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Re: MD device always starting as /dev/md127
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: MD device always starting as /dev/md127
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD device always starting as /dev/md127
  • From: Phil Turmel <philip@xxxxxxxxxx>
• MD device always starting as /dev/md127
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Ferry <iscsitmp@xxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: GuoZhong Han <hanguozhong@xxxxxxxxxxxx>
• [patch 2/2]MD: raid5 avoid unnecessary zero page for trim
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• Re: Stop IMSM verify?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong count of devices in /proc/mdstat after "want_replacement"
  • From: NeilBrown <neilb@xxxxxxx>
• Wrong count of devices in /proc/mdstat after "want_replacement"
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• RE: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: NeilBrown <neilb@xxxxxxx>
• RE: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• 3.6-rc5 cgroups blkio throttle + md regression
  • From: Joseph Glanville <joseph.glanville@xxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: mdadm kernel log messages explained
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• mdadm kernel log messages explained
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• mdadm kernel log messages explained
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• [PATCH] md: Add two chances to update sync/recovery checkpoint
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH] md/bitmap:Don't use IS_ERR to judge alloc_page().
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Small short question
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH - v2] DM RAID: Fix for ineffective "sync" directive
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Small short question
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [PATCH] fix: imsm: do not accept too small sizes
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] fix: adjust parse_size() to the unsigned size variable
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] fix: imsm: re-enable size expansion to the max value
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid5:bad sectors after lost power
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid5:bad sectors after lost power
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• RE: [PATCH] fix segfaults in Detail()
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid5:bad sectors after lost power
  • From: Mathias Buren <mathias.buren@xxxxxxxxx>
• raid5:bad sectors after lost power
  • From: "vincent" <hanguozhong@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: John Robinson <john.robinson@xxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: hank <pyu@xxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Mathias Buren <mathias.buren@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: GuoZhong Han <hanguozhong@xxxxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: hank <pyu@xxxxxxxxxx>
• Re: Stop IMSM verify?
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Re: Stop IMSM verify?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm forces resync every boot
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Stop IMSM verify?
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How can I ensure that my swraid saves checkpoints with sysrq reboot?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: How can I ensure that my swraid saves checkpoints with sysrq reboot?
  • From: NeilBrown <neilb@xxxxxxx>
• How can I ensure that my swraid saves checkpoints with sysrq reboot?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Howto avoid full re-sync
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• R: Data recovery after the failure of two disks of 4
  • From: Carabetta Giulio <g.carabetta@xxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• make filesystem failed while the capacity of raid5 is big than 16TB
  • From: "vincent" <hanguozhong@xxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Can't reshape RAID1 to RAID5 due to chunk size
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Kasper Sandberg <kontakt@xxxxxxxxxxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Data recovery after the failure of two disks of 4
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v2]raid5: fix directio regression
  • From: NeilBrown <neilb@xxxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about bitmap for raid6
  • From: NeilBrown <neilb@xxxxxxx>
• status of patches ( raid5 multiple threads )
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• FW: question about bitmap for raid6
  • From: Ming Lei <Ming.Lei@xxxxxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH RESEND] Fix and extend raid6check repair
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Howto avoid full re-sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Safe disk replace
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Howto avoid full re-sync
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• [PATCH] dm mpath: move the dereference below the NULL test
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Howto avoid full re-sync
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Content Of Files May Be Changed After One Disk Is Failed In RAID5
  • From: clplayer <cl.player@xxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• [PATCH] fix segfaults in Detail()
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• [PATCH] dm-bufio: use list_move instead of list_del/list_add
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: Safe disk replace
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• [PATCH 3/3] raid5:Move comment to func handle_stripe.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 2/3] raid5: If stripe was on delay state,it don't judge other disks state.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 1/3] raid5: remove unnecessary parameter.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 0/3][trivial] Fix some trivial bugs
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Safe disk replace
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [PATCH] DM RAID: Fix comparison of index and quantity for "rebuild" parameter
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• [PATCH] DM RAID: Fix comparison of index and quantity for "rebuild" parameter
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Data recovery after the failure of two disks of 4
  • From: Carabetta Giulio <g.carabetta@xxxxxx>
• Re: [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problems after extending partition [SOLVED]
  • From: Ross Boylan <ross@xxxxxxxxxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: Safe disk replace
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Safe disk replace
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Safe disk replace
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Safe disk replace
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Safe disk replace
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Safe disk replace
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: hank <pyu@xxxxxxxxxx>
• Re: mdadm.conf on Ubuntu - it's alive!
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• RE: mdadm.conf on Ubuntu - it's alive!
  • From: Gilbert Standen <gstanden@xxxxxxxxxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: Problems after extending partition
  • From: Ross Boylan <ross@xxxxxxxxxxxxxxxx>
• Re: Problems after extending partition
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Problems after extending partition
  • From: Ross Boylan <ross@xxxxxxxxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• [RFC][PATCH] Immutable bio vecs
  • From: Kent Overstreet <koverstreet@xxxxxxxxxx>
• Re: mdadm: Assemble.c: "force-one" update conflicts with the split-brain protection logic
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• md raid with lvm lv member
  • From: Markus Falb <markus.falb@xxxxxxxx>
• [PATCH 3 of 3] DM RAID: Add rebuild capability for RAID10
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 2 of 3] DM RAID: Move 'rebuild' checking code to its own function
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: Confusion about chunk/stripe size mdadm in combination with LVM stripe size
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: Lose two disks during Raid 10 rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Confusion about chunk/stripe size mdadm in combination with LVM stripe size
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Dan Williams <djbw@xxxxxx>
• mdadm: Assemble.c: "force-one" update conflicts with the split-brain protection logic
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: md raid6 not working
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• [PATCH] raid5: remove unnecessary "set_bit(STRIPE_HANDLE,&sh->state)" in func handle_stripe_dirtying.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• RE: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: md raid6 not working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: Dan Williams <djbw@xxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: Michael-John Turner <mj@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• RE: md raid6 not working
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid6 not working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: NeilBrown <neilb@xxxxxxx>
• Controller problems during reshape -> can't continue reshape after reboot.
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• md raid6 not working
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: Dan Williams <djbw@xxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Using SCSI timeouts in place of ERC
  • From: joystick <joystick@xxxxxxxxxxxxx>
• mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: NeilBrown <neilb@xxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Issue with md and 4K sector alignment
  • From: Kyle Brantley <kyle@xxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Recovering from the kernel bug
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• md raid behavior, bad sector uncorrectable read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Few questions about TRIM/discard
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Inexpensive RAID1 controller for home server?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Michael Tokarev <mjt@xxxxxxxxxx>