Linux RAID Storage Date Index
![](array.png)
[Prev Page][Next Page]
- Re: question: no-bitmap RAID1 with off-site drive
- From: starlight.2012q4@xxxxxxxxxxx
- Raid over USB disks and eject
- From: Salatiel Filho <salatiel.filho@xxxxxxxxx>
- Re: [PATCH 1/3] Align FAILED to test name to be parsable
- From: NeilBrown <neilb@xxxxxxx>
- Re: question: no-bitmap RAID1 with off-site drive
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
- Re: question: no-bitmap RAID1 with off-site drive
- From: starlight.2012q4@xxxxxxxxxxx
- question: no-bitmap RAID1 with off-site drive
- From: starlight.2012q4@xxxxxxxxxxx
- mdadm: error when using multiple ARRAY <ignore> lines in mdadm.conf
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- mdadm: ARRAY <ignore> lines not correctly handled
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: mystified by behaviour of mdadm raid5 -> raid0 conversion
- From: Geoff Attwater <geoffwater@xxxxxxxxx>
- [PATCH] Keep track on which kernel the test suite has run
- From: Gilles Espinasse <g.esp@xxxxxxx>
- Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
- [PATCH] imsm: Forbid spanning between multiple controllers.
- From: Marcin Tomczak <marcin.tomczak@xxxxxxxxx>
- Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
- Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
- Re: [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
- [PATCH] lib/raid6: Add AVX2 optimized recovery functions
- From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
- Re: [PATCH] raid5: panic() on dma_wait_for_async_tx() error
- From: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx>
- Re: [PATCH] raid5: panic() on dma_wait_for_async_tx() error
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
- [PATCH] raid5: panic() on dma_wait_for_async_tx() error
- From: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx>
- RAID10 hot replacement issue
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- [PATCH 1/2 V1] md:Avoid write invalid address if read_seqretry returned true.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Suggestions?: file copy to array grown by MDADM results in different md5sum value
- From: Blair Sonnen <blair.sonnen@xxxxxxxxx>
- Re: mystified by behaviour of mdadm raid5 -> raid0 conversion
- From: NeilBrown <neilb@xxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: joystick <joystick@xxxxxxxxxxxxx>
- Re: Problem with DISCARD and RAID10
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
- Re: Problem with DISCARD and RAID10
- From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Error correction and Bad block tracking in RAID5
- From: Teng-Feng Yang <shinrairis@xxxxxxxxx>
- mystified by behaviour of mdadm raid5 -> raid0 conversion
- From: Geoff Attwater <geoffwater@xxxxxxxxx>
- Re: [dm-devel] [PATCH] Fix deadlock with request based dm and some drivers
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: joystick <joystick@xxxxxxxxxxxxx>
- Re: [PATCH] Fix deadlock with request based dm and some drivers
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
- Re: [PATCH] Fix deadlock with request based dm and some drivers
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
- Re: Problem with DISCARD and RAID5
- From: Shaohua Li <shli@xxxxxxxxxx>
- Re: Problem with DISCARD and RAID10
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
- Re: [PATCH] Fix deadlock with request based dm and some drivers
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
- Re: Problem with DISCARD and RAID10
- From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
- Re: Problem with DISCARD and RAID10
- From: Holger Kiehl <Holger.Kiehl@xxxxxx>
- R: Data recovery after the failure of two disks of 4
- From: Carabetta Giulio <g.carabetta@xxxxxx>
- Re: [PATCH] Fix deadlock with request based dm and some drivers
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
- Re: [PATCH] Fix deadlock with request based dm and some drivers
- From: "Jun'ichi Nomura" <j-nomura@xxxxxxxxxxxxx>
- Re: Problem with DISCARD and RAID10
- From: Shaohua Li <shli@xxxxxxxxxx>
- [PATCH] Fix deadlock with request based dm and some drivers
- From: Jens Axboe <jaxboe@xxxxxxxxxxxx>
- Re: Re: [PATCH 1/2] md:Avoid write invalid address if read_seqretry returned true.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Re: [PATCH 1/2] md:Avoid write invalid address if read_seqretry returned true.
- From: NeilBrown <neilb@xxxxxxx>
- Re: Re: [PATCH 1/2] md:Avoid write invalid address if read_seqretry returned true.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Re: [PATCH 2/2] md: Reassigned the parameters if read_seqretry returned true in func md_is_badblock.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 1/2] md:Avoid write invalid address if read_seqretry returned true.
- From: NeilBrown <neilb@xxxxxxx>
- Problem with DISCARD and RAID10
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
- [PATCH 2/2] md: Reassigned the parameters if read_seqretry returned true in func md_is_badblock.
- From: majianpeng <majianpeng@xxxxxxxxx>
- [PATCH 1/2] md:Avoid write invalid address if read_seqretry returned true.
- From: majianpeng <majianpeng@xxxxxxxxx>
- [PATCH 0/2] Fix two bugs about forgetting to assigne to some parameters if read_seqretry returned true.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Re: Problem with DISCARD and RAID5
- From: Jens Axboe <axboe@xxxxxxxxx>
- Re: Problem with DISCARD and RAID5
- From: Dave Chinner <david@xxxxxxxxxxxxx>
- Re: merging printk and WARN
- From: David Sterba <dave@xxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: NeilBrown <neilb@xxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: NeilBrown <neilb@xxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: is "replaceable" in 3.2 considered stable
- From: NeilBrown <neilb@xxxxxxx>
- is "replaceable" in 3.2 considered stable
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- merging printk and WARN
- From: Julia Lawall <julia.lawall@xxxxxxx>
- Re: [PATCH] Remove VLAIS usage from dm-crypt
- From: Milan Broz <mbroz@xxxxxxxxxx>
- [PATCH 3/16] drivers/md/raid5.c: use WARN
- From: Julia Lawall <Julia.Lawall@xxxxxxx>
- Compilation error on today's git
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
- Re: mdadm recovery after HW failure: missing blocks at the end
- From: Sebastian Hegler <sebastian.hegler@xxxxxxxxxxxxx>
- An md1 array doesn't re-assemble after reboot (/dev/sdf2 reports being an active member for /dev/md1, but a --re-add fails).
- From: Marc MERLIN <marc@xxxxxxxxxxx>
- Re: mdadm recovery after HW failure: missing blocks at the end
- From: Sebastian Hegler <sebastian.hegler@xxxxxxxxxxxxx>
- Re: Problem with DISCARD and RAID5
- From: Shaohua Li <shli@xxxxxxxxxx>
- mdadm recovery after HW failure: missing blocks at the end
- From: Sebastian Hegler <sebastian.hegler@xxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: 3TB drives failure rate (summary)
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate (summary)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate (summary)
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate (summary)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate (summary)
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Wolfgang Denk <wd@xxxxxxx>
- Re: About RAID1/10 io barrier between normal io and resync/recovery io.
- From: NeilBrown <neilb@xxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- About RAID1/10 io barrier between normal io and resync/recovery io.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Problem with DISCARD and RAID5
- From: NeilBrown <neilb@xxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Curtis J Blank <curt@xxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Curtis J Blank <curt@xxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: 3TB drives failure rate (summary)
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- 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: [RFC 1/2]raid1: only write mismatch sectors in sync
- From: Shaohua Li <shli@xxxxxxxxxx>
- [PULL REQUEST] md fixes (plus UAPI reorg) for 3.7
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 3/5] md: Increase the frequency of recording checkpoint of recovery.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH V1] md:Add place to update ->recovery_cp.
- From: NeilBrown <neilb@xxxxxxx>
- 3TB drives failure rate (summary)
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Curt Blank <curt@xxxxxxxxxxxxxx>
- [PATCH] Remove VLAIS usage from dm-crypt
- From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
- [PATCH] Removing the use of VLAIS from the Linux Kernel
- From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Curtis J Blank <curt@xxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: task xfssyncd blocked while raid5 was in recovery
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: MDADM after QNAP Support disaster QNAP 859 Pro
- From: NeilBrown <neilb@xxxxxxx>
- Re: task xfssyncd blocked while raid5 was in recovery
- From: hanguozhong <hanguozhong@xxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Roberto Spadim <rspadim@xxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Curt Blank <curt@xxxxxxxxxxxxxx>
- Re: Best way (only?) to setup SSD's for using TRIM
- From: Curtis J Blank <curt@xxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: RAID and LVM alignment when expanding PVs
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: Re: [PATCH 3/5] md: Increase the frequency of recording checkpoint of recovery.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Re: 3TB drives failure rate
- From: David Brown <david.brown@xxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Roman Mamedov <rm@xxxxxxxxxx>
- Re: Re: [PATCH 1/5] md: When resync aborted,using ->curr_resync as the last completed request rather than ->curr_resync_completed.
- From: majianpeng <majianpeng@xxxxxxxxx>
- [PATCH V1] md:Add place to update ->recovery_cp.
- From: kernelmail <kedacomkernel@xxxxxxxxx>
- Re: Re: [PATCH 2/5] md:Add place to update ->recovery_cp.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Re: Re: [PATCH 4/5] md: Return proper error rather than EIO.
- From: majianpeng <majianpeng@xxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: joystick <joystick@xxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: joystick <joystick@xxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Peter Kieser <peter@xxxxxxxxx>
- Re: Commit "db91ff55bdf06736b" using curr_resync_completed instead of curr_resync when interrupted the resync operation
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH] MD RAID10: Fix oops when creating RAID10 arrays via dm-raid.c
- From: NeilBrown <neilb@xxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: joystick <joystick@xxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Phil Turmel <philip@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: joystick <joystick@xxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: [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: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 4/5] md: Return proper error rather than EIO.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 3/5] md: Increase the frequency of recording checkpoint of recovery.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 2/5] md:Add place to update ->recovery_cp.
- From: NeilBrown <neilb@xxxxxxx>
- Re: [PATCH 1/5] md: When resync aborted,using ->curr_resync as the last completed request rather than ->curr_resync_completed.
- From: NeilBrown <neilb@xxxxxxx>
- Re: 3TB drives failure rate
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: 3TB drives failure rate
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
- Re: 3TB drives failure rate
- From: Roman Mamedov <rm@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Roman Mamedov <rm@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Roman Mamedov <rm@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Roman Mamedov <rm@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
- Best way (only?) to setup SSD's for using TRIM
- From: Curtis J Blank <curt@xxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Joe Landman <joe.landman@xxxxxxxxx>
- Re: 3TB drives failure rate
- From: Ed W <lists@xxxxxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Michael Tokarev <mjt@xxxxxxxxxx>
- Re: 3TB drives failure rate
- From: John Robinson <john.robinson@xxxxxxxxxxx>
- Re: 3TB drives failure rate
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
- 3TB drives failure rate
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
- Re: RAID and LVM alignment when expanding PVs
- From: Erez Zarum <erezzarum@xxxxxxxxx>
- Re: RAID and LVM alignment when expanding PVs
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- Re: RAID and LVM alignment when expanding PVs
- From: Erez Zarum <erezzarum@xxxxxxxxx>
- Re: RAID and LVM alignment when expanding PVs
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
- RAID and LVM alignment when expanding PVs
- From: Erez Zarum <erezzarum@xxxxxxxxx>
- 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
- 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
- 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
- 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.
- 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
- 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
- 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
- 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
- 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>
[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]