Linux RAID Storage Date Index

Thread Index

Re: grub2/grub-pc install not possible on mdadm
- From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Re: grub2/grub-pc install not possible on mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: md raid5 fsync deadlock
- From: Milan Broz <mbroz@xxxxxxxxxx>
Re: md raid5 fsync deadlock
- From: NeilBrown <neilb@xxxxxxx>
Re: debugging md2_resync hang at raise_barrier
- From: NeilBrown <neilb@xxxxxxx>
debugging md2_resync hang at raise_barrier
- From: Ray Morris <support@xxxxxxxxxxxxx>
md raid5 fsync deadlock
- From: Milan Broz <mbroz@xxxxxxxxxx>
[Patch]use atomic_dec_return() instead of atomic_dec() and atomic_read()
- From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
Re: What are these reads in what should be simply a full-stripe write?
- From: Doug Dumitru <doug@xxxxxxxxxx>
md: Return proper err if d_path error in get_bitmap_file.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: migrating from metadata 0.9 to 1.0 before growing?
- From: NeilBrown <neilb@xxxxxxx>
Adding a disk to RAID0
- From: Victor Balakine <victor.balakine@xxxxxx>
Re: What are these reads in what should be simply a full-stripe write?
- From: linbloke <linbloke@xxxxxxxxxxx>
Change metadata version?
- From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
Re: Raid5 device hangs in active state
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 device hangs in active state
- From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
Re: Raid5 device hangs in active state
- From: NeilBrown <neilb@xxxxxxx>
What are these reads in what should be simply a full-stripe write?
- From: John Adams <john.adams@xxxxxxxx>
Re: Raid5 device hangs in active state
- From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
Re: migrating from metadata 0.9 to 1.0 before growing?
- From: Lars Täuber <taeuber@xxxxxxx>
3 Drives down, Help!
- From: Jon Hardcastle <Jon@xxxxxxxxxxxxxxx>
Re: Add barrier support to dm-raid
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH] Add barrier support to dm-raid
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
grub2/grub-pc install not possible on mdadm
- From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
mdadm --assemble --scan always fail if bulit with uClibc.
- From: Piotr Karbowski <piotr.karbowski@xxxxxxxxx>
Re: Re: md:When opened /proc/mdstat, increase the refcount of
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: MD and rotational attribute
- From: NeilBrown <neilb@xxxxxxx>
Re: MD and rotational attribute
- From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: NeilBrown <neilb@xxxxxxx>
Re: md: Use existed macro instead of number
- From: NeilBrown <neilb@xxxxxxx>
Solved (for me at least!) GRUB doesn't like ServeRAID M1015/LSI 9220-8i
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: md:When opened /proc/mdstat, increase the refcount of
- From: NeilBrown <neilb@xxxxxxx>
how to use badsector function
- From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
Re: md:When opened /proc/mdstat, increase the refcount of
- From: NeilBrown <neilb@xxxxxxx>
Re: Re: md:When opened /proc/mdstat, increase the refcount of
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Re: md:When opened /proc/mdstat, increase the refcount of
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: md:When opened /proc/mdstat, increase the refcount of
- From: NeilBrown <neilb@xxxxxxx>
md:When opened /proc/mdstat, increase the refcount of
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Failed RAID6
- From: NeilBrown <neilb@xxxxxxx>
Failed RAID6
- From: Larry Owen <larryowen@xxxxxxxxxxx>
migrating from metadata 0.9 to 1.0 before growing?
- From: Lars Täuber <taeuber@xxxxxxx>
md: Use existed macro instead of number
- From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
Re: [PATCH] Use MDMON_DIR for pid files created in Monitor.c
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH] Use MDMON_DIR for pid files created in Monitor.c
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: "J. Ali Harlow" <ali@xxxxxxxxxxxxx>
Re: [PATCH] Print error message if failing to write super for 1.x metadata
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Lenny to squeeze mdadm problem + e2label problem
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH] Use MDMON_DIR for pid files created in Monitor.c
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Print error message if failing to write super for 1.x metadata
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 0/1] Make failure message on re-add more explcit
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/1] Make error message on failure to --re-add more explicit
- From: Jes.Sorensen@xxxxxxxxxx
Lenny to squeeze mdadm problem + e2label problem
- From: Manuel Arostegui <manuel@xxxxxxxxxx>
[PATCH] Print error message if failing to write super for 1.x metadata
- From: Jes.Sorensen@xxxxxxxxxx
Re: [PATCH] Print correct md device name if write_init_super fails
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: RAID1 content under Windows OS
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: [PATCH] avoid double-free upon "old buggy kernel" sysfs_read failure
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Print correct md device name if write_init_super fails
- From: NeilBrown <neilb@xxxxxxx>
Re: Question regarding RAID10
- From: NeilBrown <neilb@xxxxxxx>
Re: SES Enclosure Management.
- From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
RAID1 content under Windows OS
- From: Álvaro López López <allopez@xxxxxxx>
Re: [PATCH] avoid double-free upon "old buggy kernel" sysfs_read failure
- From: Jim Meyering <jim@xxxxxxxxxxxx>
Re: RAID10: How to mark spare as active, assume-clean documentation
- From: Phil Turmel <philip@xxxxxxxxxx>
[PATCH] Print correct md device name if write_init_super fails
- From: Jes.Sorensen@xxxxxxxxxx
Re: Starting a RADI1 array after the filesystem has being used through LVM?
- From: Phil Turmel <philip@xxxxxxxxxx>
[PATCH] avoid double-free upon "old buggy kernel" sysfs_read failure
- From: Jim Meyering <jim@xxxxxxxxxxxx>
RE: Problem rebuild raid 1 replacement disk
- From: "RANSOM, Tony" <tony.ransom@xxxxxxxxxxxxxx>
RAID10: How to mark spare as active, assume-clean documentation
- From: Anshuman Aggarwal <anshuman@xxxxxxxxxxxxx>
Starting a RADI1 array after the filesystem has being used through LVM?
- From: Danilo Godec <danilo.godec@xxxxxxxxx>
RE: Problem rebuild raid 1 replacement disk
- From: "RANSOM, Tony" <tony.ransom@xxxxxxxxxxxxxx>
MD and rotational attribute
- From: Karel Zak <kzak@xxxxxxxxxx>
Re: Problem rebuild raid 1 replacement disk
- From: NeilBrown <neilb@xxxxxxx>
RE: Problem rebuild raid 1 replacement disk
- From: "RANSOM, Tony" <tony.ransom@xxxxxxxxxxxxxx>
Re: Problem rebuild raid 1 replacement disk
- From: NeilBrown <neilb@xxxxxxx>
RE: Problem rebuild raid 1 replacement disk
- From: "RANSOM, Tony" <tony.ransom@xxxxxxxxxxxxxx>
Re: Problem rebuild raid 1 replacement disk
- From: NeilBrown <neilb@xxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: NeilBrown <neilb@xxxxxxx>
Problem rebuild raid 1 replacement disk
- From: "RANSOM, Tony" <tony.ransom@xxxxxxxxxxxxxx>
Re: [PATCH] FIX: Changes in '0' case for reshape position verification
- From: NeilBrown <neilb@xxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Install grub2 to /dev/md126 fails, revisited
- From: jlcenter@xxxxxxxxxxx
Re: mdadm segfaults on --grow
- From: NeilBrown <neilb@xxxxxxx>
mdadm segfaults on --grow
- From: eeeee <tw@xxxxxxxxxxx>
Re: zeroed superblock on raid6
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david.brown@xxxxxxxxxxxx>
zeroed superblock on raid6
- From: dragos@xxxxxxxxxxx
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: SES Enclosure Management.
- From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
Re: SES Enclosure Management.
- From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
[PATCH] FIX: Changes in '0' case for reshape position verification
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Hang in Raid-5 code (Old bug back?)
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: [PATCH] Use posix_memalign() for memory used to write bitmaps
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Use posix_memalign() for memory used to write bitmaps
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm segfault at assemble
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm dropped disk, won't re-add
- From: John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx>
Re: mdadm dropped disk, won't re-add
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: SES Enclosure Management.
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Add a spare to a poorly defined raid1
- From: David Liontooth <lionteeth@xxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
mdadm dropped disk, won't re-add
- From: John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: keld@xxxxxxxxxx
Re: Add a spare to a poorly defined raid1
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Add a spare to a poorly defined raid1
- From: David Liontooth <lionteeth@xxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: keld@xxxxxxxxxx
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: SES Enclosure Management.
- From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
Re: SES Enclosure Management.
- From: NeilBrown <neilb@xxxxxxx>
Re: SES Enclosure Management.
- From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
Re: SES Enclosure Management.
- From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
Re: SES Enclosure Management.
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: SES Enclosure Management.
- From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
Re: SES Enclosure Management.
- From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
Re: SES Enclosure Management.
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: SES Enclosure Management.
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: SES Enclosure Management.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid 5 and bad block feature
- From: NeilBrown <neilb@xxxxxxx>
Re: raid 5 and bad block feature
- From: bobzer <bobzer@xxxxxxxxx>
mdadm 3.2.3 segfault when trying to reassemble a device
- From: Nikita Kozlov <nikita@xxxxxxxxxxx>
SES Enclosure Management.
- From: Robert Woodworth <robertjwoodworth@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: keld@xxxxxxxxxx
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH] Use posix_memalign() for memory used to write bitmaps
- From: Jes.Sorensen@xxxxxxxxxx
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: keld@xxxxxxxxxx
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: RAID6 ext3 problems
- From: NeilBrown <neilb@xxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID6 ext3 problems
- From: Mark Knecht <markknecht@xxxxxxxxx>
RAID6 ext3 problems
- From: Jeff W <jeff.welling@xxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: RAID6 ext3 problems
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: RAID6 ext3 problems
- From: Jeff W <jeff.welling@xxxxxxxxx>
Re: RAID6 ext3 problems
- From: Jeff W <jeff.welling@xxxxxxxxx>
Re: RAID corruption with kernel 3.2?
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
RAID6 ext3 problems
- From: Jeff W <jeff.welling@xxxxxxxxx>
Re: RAID6 ext3 problems
- From: Mark Knecht <markknecht@xxxxxxxxx>
RAID6 ext3 problems
- From: Jeff W <jeff.welling@xxxxxxxxx>
Re: RAID corruption with kernel 3.2?
- From: Holger Kiehl <Holger.Kiehl@xxxxxx>
Re: RAID corruption with kernel 3.2?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: RAID corruption with kernel 3.2?
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Re: RAID corruption with kernel 3.2?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
RAID corruption with kernel 3.2?
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
equal / larger size still not large enough (3.2.3)
- From: Felipe Sanchez <izto@xxxxxxxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: XFS on top RAID10 with odd drives count and 2 near copies
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
mdadm devel-3.3
- From: bobzer <bobzer@xxxxxxxxxxxxx>
XFS on top RAID10 with odd drives count and 2 near copies
- From: CoolCold <coolthecold@xxxxxxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
[PATCH 17/60] md: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
[PATCH 55/60] dm: remove the second argument of k[un]map_atomic()
- From: Cong Wang <amwang@xxxxxxxxxx>
RE: [PATCH 08/12] FIX: use md position to reshape restart
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
RE: [PATCH 08/12] FIX: use md position to reshape restart
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 08/12] FIX: use md position to reshape restart
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] FIX: Add missed '0' case for reshape position verification
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
RE: [PATCH 08/12] FIX: use md position to reshape restart
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 08/12] FIX: use md position to reshape restart
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 08/12] FIX: use md position to reshape restart
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
[long] general advice: config recommendations
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: NeilBrown <neilb@xxxxxxx>
Re: Hang in Raid-5 code (Old bug back?)
- From: Dag Nygren <dag@xxxxxxxxxx>
Re: [PATCH 00/12] Problems during restart container reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 08/12] FIX: use md position to reshape restart
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] two md updates for 3.3
- From: NeilBrown <neilb@xxxxxxx>
Re: metadata 1.2 advantages?
- From: NeilBrown <neilb@xxxxxxx>
Re: remove one md and add its disk to the other md
- From: Asif Iqbal <vadud3@xxxxxxxxx>
Re: Some md/mdadm bugs
- From: NeilBrown <neilb@xxxxxxx>
Re: metadata 1.2 advantages?
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Re: metadata 1.2 advantages?
- From: NeilBrown <neilb@xxxxxxx>
remove one md and add its disk to the other md
- From: Asif Iqbal <vadud3@xxxxxxxxx>
Re: metadata 1.2 advantages?
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Re: write-intent bitmapping
- From: CoolCold <coolthecold@xxxxxxxxx>
write-intent bitmapping
- From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
metadata 1.2 advantages?
- From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Re: imsm raid is always readonly on boot
- From: NeilBrown <neilb@xxxxxxx>
Re: imsm raid is always readonly on boot
- From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: imsm raid is always readonly on boot
- From: NeilBrown <neilb@xxxxxxx>
Re: imsm raid is always readonly on boot
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: imsm raid is always readonly on boot
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: using dd (or dd_rescue) to salvage array
- From: Stefan *St0fF* Huebner <st0ff@xxxxxxx>
Re: imsm raid is always readonly on boot
- From: Stefan Priebe <s.priebe@xxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: imsm raid is always readonly on boot
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: imsm raid is always readonly on boot
- From: Stefan Priebe <s.priebe@xxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: imsm raid is always readonly on boot
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[PATCH 10/12] imsm: FIX: Clear migration record when migration switches to next volume.
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 09/12] imsm: FIX: use md position to reshape restart
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 08/12] FIX: use md position to reshape restart
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 12/12] FIX: Do not try to (continue) reshape using inactive array
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 11/12] FIX: restart reshape when reshape process is stopped just between 2 reshapes
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 03/12] FIX: Array is not run when expansion disks are added
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 02/12] imsm: FIX: No new missing disks are allowed during general migration
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 07/12] imsm: FIX: Chunk size migration problem
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 06/12] Flush mdmon before next reshape step during container operation
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 01/12] FIX: NULL pointer to strdup() can be passed
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 05/12] Fix: Sometimes mdmon throws core dump during reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 00/12] Problems during restart container reshape
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 04/12] imsm: FIX: imsm_get_allowed_degradation() doesn't count degradation for raid1
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
imsm raid is always readonly on boot
- From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Re: sb->resync_offset value after resync failure
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: NeilBrown <neilb@xxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Richard Herd <2001oddity@xxxxxxxxx>
Re: using dd (or dd_rescue) to salvage array
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: NeilBrown <neilb@xxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Richard Herd <2001oddity@xxxxxxxxx>
Re: using dd (or dd_rescue) to salvage array
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: NeilBrown <neilb@xxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Richard Herd <2001oddity@xxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Richard Herd <2001oddity@xxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: NeilBrown <neilb@xxxxxxx>
Fwd: Please Help! RAID5 -> 6 reshapre gone bad
- From: Richard Herd <2001oddity@xxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: NeilBrown <neilb@xxxxxxx>
Re: Please Help! RAID5 -> 6 reshapre gone bad
- From: Phil Turmel <philip@xxxxxxxxxx>
Please Help! RAID5 -> 6 reshapre gone bad
- From: Richard Herd <2001oddity@xxxxxxxxx>
Re: sb->resync_offset value after resync failure
- From: NeilBrown <neilb@xxxxxxx>
Re: Would different hd speeds affect md raid?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Some md/mdadm bugs
- From: NeilBrown <neilb@xxxxxxx>
Re: Some md/mdadm bugs
- From: NeilBrown <neilb@xxxxxxx>
Re: using dd (or dd_rescue) to salvage array
- From: Stefan *St0fF* Huebner <st0ff@xxxxxxx>
Re: Would different hd speeds affect md raid?
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: Would different hd speeds affect md raid?
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Would different hd speeds affect md raid?
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Joel <jdy@xxxxxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Joel <jdy@xxxxxxxxxxxxxxx>
Re: sb->resync_offset value after resync failure
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [PATCH] getinfo_super1: when deciding whether the array is clean or dirty, compare sb->resync_offset against MaxSector and not against sb->size
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
[PATCH] getinfo_super1: when deciding whether the array is clean or dirty, compare sb->resync_offset against MaxSector and not against sb->size
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: using dd (or dd_rescue) to salvage array
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Hand in Raid-5 code
- From: Dag Nygren <dag@xxxxxxxxxx>
Re: using dd (or dd_rescue) to salvage array
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
Re: [PATCH] There's no need to include linux/version.h in drivers/md/dm-bufio.c
- From: Jiri Kosina <jkosina@xxxxxxx>
using dd (or dd_rescue) to salvage array
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: Some md/mdadm bugs
- From: NeilBrown <neilb@xxxxxxx>
Raid6 rebuild question
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Some md/mdadm bugs
- From: Asdo <asdo@xxxxxxxxxxxxx>
[PATCH] Use MDMON_DIR for pid files created in Monitor.c
- From: Jes.Sorensen@xxxxxxxxxx
Re: GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Re: GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: sb->resync_offset value after resync failure
- From: NeilBrown <neilb@xxxxxxx>
Re: sb->resync_offset value after resync failure
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Re: GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: Hannes Reinecke <hare@xxxxxxx>
Re: GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: mvsas with 3.1
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Re: mvsas with 3.1
- From: Simon McNair <simonmcnair@xxxxxxxxx>
Re: rebuild raid6 after two failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: rebuild raid6 after two failures
- From: NeilBrown <neilb@xxxxxxx>
Re: rebuild raid6 after two failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Found data loss report with write-mostly
- From: NeilBrown <neilb@xxxxxxx>
Found data loss report with write-mostly
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: [dm-crypt] Kernel BUG (fs/bio.c:1499) when copying more files to an encrypted device
- From: Luzipher McLeod <luziphermcleod@xxxxxxxx>
Re: RAID6 - repeated hot-pulls issue
- From: John Gehring <john.gehring@xxxxxxxxx>
RE: [PATCH 5/5] imsm: verify maximum supported active volumes in assembly
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: RAID6 - repeated hot-pulls issue
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
RE: [PATCH] fix: do not overwrite existing devices' symlinks
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
rebuild raid6 after two failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] DM RAID: Fix memory corruption caused by repeated calls to bitmap_load
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: do not overwrite existing devices' symlinks
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/5] imsm: verify maximum supported active volumes in assembly
- From: NeilBrown <neilb@xxxxxxx>
Re: Reduce number of active RAID1 devices
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Re: Reduce number of active RAID1 devices
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Reduce number of active RAID1 devices
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
RE: [PATCH] fix: do not overwrite existing devices' symlinks
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
RE: [PATCH 5/5] imsm: verify maximum supported active volumes in assembly
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: [PATCH 4/4] Spawn mdmon with --offroot if mdadm was launched with --offroot
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
RE: [PATCH 1/4] FIX: Takeover mdmon when grow is continued from command line
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH] fix: do not overwrite existing devices' symlinks
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix, the second array need to have the whole available space on devices
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 4/4] Spawn mdmon with --offroot if mdadm was launched with --offroot
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 5/5] imsm: verify maximum supported active volumes in assembly
- From: NeilBrown <neilb@xxxxxxx>
Re: [dm-crypt] Kernel BUG (fs/bio.c:1499) when copying more files to an encrypted device
- From: Luzipher McLeod <luziphermcleod@xxxxxxxx>
Re: [PATCH 0/4] Reshape problems during double raid0 processing
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/4] FIX: Takeover mdmon when grow is continued from command line
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-6 recovery questions
- From: Mukund Sivaraman <muks@xxxxxxxx>
Re: RAID-6 recovery questions
- From: Mukund Sivaraman <muks@xxxxxxxx>
Re: Preventative replacement of active RAID1 disks
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
Re: RAID-6 recovery questions
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
[PATCH] imsm: fix, the second array need to have the whole available space on devices
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH] DM RAID: Fix memory corruption caused by repeated calls to bitmap_load
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
RE: [PATCH 0/4] Reshape problems during double raid0 processing
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: RAID-6 recovery questions
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
RAID-6 recovery questions
- From: Mukund Sivaraman <muks@xxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: Seth Jennings <spartacus06@xxxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: Trevor Cordes <trevor@xxxxxxxxxxxxx>
Re: disk-sleep problems
- From: Trevor Cordes <trevor@xxxxxxxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: LVM striping RAID volumes
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: NeilBrown <neilb@xxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: NeilBrown <neilb@xxxxxxx>
Re: add another disk to existing raid 0, ie grow raid 0 possible?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
add another disk to existing raid 0, ie grow raid 0 possible?
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: LVM striping RAID volumes
- From: Douglas Siebert <douglas-siebert@xxxxxxxxx>
Re: sb->resync_offset value after resync failure
- From: NeilBrown <neilb@xxxxxxx>
Re: sb->resync_offset value after resync failure
- From: NeilBrown <neilb@xxxxxxx>
Re: [dm-crypt] Kernel BUG (fs/bio.c:1499) when copying more files to an encrypted device
- From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
Re: LVM striping RAID volumes
- From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: Doug Dumitru <doug@xxxxxxxxxx>
Re: Help please: 2-5 tps on write with 98% iowait
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Help please: 2-5 tps on write with 98% iowait
- From: Seth Jennings <spartacus06@xxxxxxxxx>
Re: LVM striping RAID volumes
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: disk-sleep problems
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: [PATCH v3 0/4] add --offroot argument to mdadm/mdmon
- From: Doug Ledford <dledford@xxxxxxxxxx>
[PATCH 4/4] Spawn mdmon with --offroot if mdadm was launched with --offroot
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 3/4] Add --offroot argument to mdmon
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 2/4] Add --offroot argument to mdadm
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/4] mdmon: Use getopt_long() to parse command line options
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH v3 0/4] add --offroot argument to mdadm/mdmon
- From: Jes.Sorensen@xxxxxxxxxx
Re: LVM striping RAID volumes
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Raid 6--best practices
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: NeilBrown <neilb@xxxxxxx>
Re: raid array with 3T disks and GPT partition
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Kernel BUG (fs/bio.c:1499) when copying more files to an encrypted device
- From: Luzipher McLeod <luziphermcleod@xxxxxxxx>
Re: LVM striping RAID volumes
- From: David Brown <david.brown@xxxxxxxxxxxx>
LVM striping RAID volumes
- From: Douglas Siebert <douglas-siebert@xxxxxxxxx>
Re: nonstandard raid(4-ish) scheme
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: kernel watchdog: EIP: [<f85d42fa>] handle_stripe+0x24b/0x18d7 [raid456] SS:ESP 0068:ef189e54
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: nonstandard raid(4-ish) scheme
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: sb->resync_offset value after resync failure
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: nonstandard raid(4-ish) scheme
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: David Brown <david@xxxxxxxxxxxxxxx>
nonstandard raid(4-ish) scheme
- From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Michal Soltys <soltys@xxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Lennart Poettering <lpoetter@xxxxxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Kay Sievers <kay@xxxxxxxxxx>
combine multiple write-intent bitmaps
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Lennart Poettering <lpoetter@xxxxxxxxxx>
raid1 resync consuming a lot of cpu
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
kernel watchdog: EIP: [<f85d42fa>] handle_stripe+0x24b/0x18d7 [raid456] SS:ESP 0068:ef189e54
- From: Marc MERLIN <marc@xxxxxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Doug Ledford <dledford@xxxxxxxxxx>
Drive goes into slow state with uncorrectable sectors, but does not fail
- From: Jeremy Sanders <jeremy@xxxxxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[PATCH] fix: do not overwrite existing devices' symlinks
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
[PATCH 4/4] Spawn mdmon with --preboot if mdadm was launched with --preboot
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 3/4] Add --preboot argument to mdmon
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/4] mdmon: Use getopt_long() to parse command line options
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 2/4] Add --preboot argument to mdadm
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH v2 0/4] add --preboot argument to mdadm/mdmon
- From: Jes.Sorensen@xxxxxxxxxx
Re: [PATCH 3/4] Add --initrd argument to mdmon
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Raid 6--best practices
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Raid 6--best practices
- From: linbloke <linbloke@xxxxxxxxxxx>
Re: [PATCH 0/4] add --initrd argument to mdadm/mdmon
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/4] Add --initrd argument to mdmon
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] compile cleanly with -Wstrict-aliasing=1
- From: Michal Soltys <soltys@xxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Michal Soltys <soltys@xxxxxxxx>
Re: Preventative replacement of active RAID1 disks
- From: Wolfgang Denk <wd@xxxxxxx>
Re: RAID6 - repeated hot-pulls issue
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Preventative replacement of active RAID1 disks
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
Re: Preventative replacement of active RAID1 disks
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: Preventative replacement of active RAID1 disks
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: [PATCH 0/4] add --initrd argument to mdadm/mdmon
- From: Lennart Poettering <lpoetter@xxxxxxxxxx>
Re: Raid 6--best practices
- From: Shain Miley <smiley@xxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Raid 6--best practices
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: Raid 6--best practices
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: Raid 6--best practices
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
Re: Raid 6--best practices
- From: Wiliam Colls <william.colls@xxxxxxxxxx>
RE: Raid 6--best practices
- From: Shain Miley <SMiley@xxxxxxx>
Re: Raid 6--best practices
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Raid 6--best practices
- From: Shain Miley <SMiley@xxxxxxx>
sb->resync_offset value after resync failure
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
RE: [PATCH 2/4] Add --initrd argument to mdadm
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: Invalidating the pages read from a disk which md marks as faulty later
- From: NeilBrown <neilb@xxxxxxx>
FYI: Re: ugly way to avoiding gcc strict-aliasing warning?
- From: Paweł Sikora <pluto@xxxxxxxx>
Preventative replacement of active RAID1 disks
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
RE: [PATCH 2/4] Add --initrd argument to mdadm
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 2/4] Add --initrd argument to mdadm
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: RAID6, failed device, unresponsive system?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
RE: [PATCH 2/4] Add --initrd argument to mdadm
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 0/4] add --initrd argument to mdadm/mdmon
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 0/4] add --initrd argument to mdadm/mdmon
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: RAID6, failed device, unresponsive system?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: RAID6, failed device, unresponsive system?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: RAID6, failed device, unresponsive system?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
RAID6, failed device, unresponsive system?
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
[PATCH 4/4] Spawn mdmon with --initrd if mdadm was launched with --initrd
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 3/4] Add --initrd argument to mdmon
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 2/4] Add --initrd argument to mdadm
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/4] mdmon: Use getopt_long() to parse command line options
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/4] add --initrd argument to mdadm/mdmon
- From: Jes.Sorensen@xxxxxxxxxx
Re: mvsas with 3.1 (mdraid+xfs locked up, single drive w/xfs not locked up)
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: mvsas with 3.1 (mdraid+xfs locked up, single drive w/xfs not locked up)
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
disk-sleep problems
- From: Wim Delvaux <wrl.delvaux@xxxxxxxxx>
Re: Questions about MD 2-drive RAID-10
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: [PATCH] md: Remove annoying debug message when restarting
- From: Ingo Molnar <mingo@xxxxxxx>
Re: [PATCH] There's no need to include linux/version.h in drivers/md/dm-bufio.c
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: [dm-devel] [PATCH] drivers/md/dm-ioctl.c::target_message(): don't leak 'argv' mem
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
[PATCH] There's no need to include linux/version.h in drivers/md/dm-bufio.c
- From: Jesper Juhl <jj@xxxxxxxxxxxxx>
[PATCH] drivers/md/dm-ioctl.c::target_message(): don't leak 'argv' mem
- From: Jesper Juhl <jj@xxxxxxxxxxxxx>
[PATCH] md: Remove annoying debug message when restarting
- From: Sasha Levin <levinsasha928@xxxxxxxxx>
[PATCH] MD: Bitmap version cleanup.
- From: Andrei Warkentin <andrey.warkentin@xxxxxxxxx>
Re: RAID0 partition set to spare
- From: NeilBrown <neilb@xxxxxxx>
[New Here] Need some help recovering failed Raid-5, Cant seem to re-create the same size array.
- From: Steve Vialle <vevets3@xxxxxxxxx>
Re: RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: not able to resize/grow RAID-1 (beyond 1 TB?)
- From: Tomasz Chmielewski <tch@xxxxxxxx>
Re: Raid0 rebuild slows to a crawl
- From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
not able to resize/grow RAID-1 (beyond 1 TB?)
- From: Tomasz Chmielewski <tch@xxxxxxxx>
mvsas with 3.1
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: David Brown <david@xxxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Michal Soltys <soltys@xxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: David Brown <david@xxxxxxxxxxxxxxx>
[PATCH 1/5] imsm: load_super_imsm_all function refactoring
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 5/5] imsm: verify maximum supported active volumes in assembly
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 3/5] imsm: validate the number of imsm volumes per controller
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 4/5] imsm: display fd in error trace when when store_imsm_mpb failes
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 2/5] imsm: load_imsm_super_all supports loading metadata from the device list
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[PATCH 0/5] imsm: validate the number of imsm volumes per controller
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
Re: Raid0 rebuild slows to a crawl
- From: David Liontooth <lionteeth@xxxxxxxxxx>
Re: Raid1 rebuild slows to a crawl
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Raid0 rebuild slows to a crawl
- From: Kay Diederichs <kay.diederichs@xxxxxxxxxxxxxxx>
Raid0 rebuild slows to a crawl
- From: David Liontooth <lionteeth@xxxxxxxxxx>
Questions about MD 2-drive RAID-10
- From: Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Michal Soltys <soltys@xxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: RAID6 r-m-w, op-journaled fs, SSDs
- From: <pg_mh@xxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[PATCH 4/4] FIX: Typo error in fprint command
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 3/4] FIX: mdmon check in reshape_container() can cause a problem
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 2/4] FIX: External metadata sometimes is not updated
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 1/4] FIX: Takeover mdmon when grow is continued from command line
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
[PATCH 0/4] Reshape problems during double raid0 processing
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: Monitor sometimes crashes
- From: NeilBrown <neilb@xxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID10 only using 2/4 drives
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
RAID10 only using 2/4 drives
- From: Josh Reynolds <josh.reynolds@xxxxxxxxxxxxxxxxxx>
[PATCH] fix: Monitor sometimes crashes
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: [PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: Shi Xuelin-B29237 <B29237@xxxxxxxxxxxxx>
[PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: <b29237@xxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: NeilBrown <neilb@xxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1) [SOLVED]
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: NeilBrown <neilb@xxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: raid array with 3T disks and GPT partition
- From: Phillip Susi <psusi@xxxxxxxxxx>
RE: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: Bobby Kent <bpkent@xxxxxxxxxxxxxxxxxxxx>
[PULL REQUEST] two bugfixes for md.
- From: NeilBrown <neilb@xxxxxxx>
Re: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: NeilBrown <neilb@xxxxxxx>
RE: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: Bobby Kent <bpkent@xxxxxxxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Renaming MD devices (metadata=1.1)
- From: Michal Soltys <soltys@xxxxxxxx>
Renaming MD devices (metadata=1.1)
- From: Gilbert Kowarzyk <kowarzyk@xxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: NeilBrown <neilb@xxxxxxx>
Meaning of "Used Dev Space" in "mdadm --detail" output for a 6 disk RAID10 array
- From: Bobby Kent <bpkent@xxxxxxxxxxxxxxxxxxxx>
Re: "md_raid5: page allocation failure" when resyncing on 3.2
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Giving top priority to a rebuild instead of serving userland?
- From: Anssi Hannula <anssi.hannula@xxxxxx>
Re: "md_raid5: page allocation failure" when resyncing on 3.2
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: Giving top priority to a rebuild instead of serving userland?
- From: Martin Cracauer <cracauer@xxxxxxxx>
Re: Giving top priority to a rebuild instead of serving userland?
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: "md_raid5: page allocation failure" when resyncing on 3.2
- From: Roman Mamedov <rm@xxxxxxxxxx>
"md_raid5: page allocation failure" when resyncing on 3.2
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Giving top priority to a rebuild instead of serving userland?
- From: Martin Cracauer <cracauer@xxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
Wiki problems
- From: Sven Hartrumpf <hartrumpf@xxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: recovery from multiple failures
- From: NeilBrown <neilb@xxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: raid1d crash at boot
- From: NeilBrown <neilb@xxxxxxx>
Re: raid 1 bug with write-mostly and administrative failed disk
- From: NeilBrown <neilb@xxxxxxx>
Re: recovery from multiple failures
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 device hangs in active state
- From: NeilBrown <neilb@xxxxxxx>
Re: recovery from multiple failures
- From: Phil Turmel <philip@xxxxxxxxxx>
Raid5 device hangs in active state
- From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
Re: [PULL REQUEST] md for 3.3
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Re: [PULL REQUEST] md for 3.3
- From: NeilBrown <neilb@xxxxxxx>
Re: [PULL REQUEST] md for 3.3
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
recovery from multiple failures
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
Re: polling mdX/md/degraded in sysfs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: What just happened to my disks/RAID5 array?
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: raid1d crash at boot
- From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: What just happened to my disks/RAID5 array?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Jan Kasprzak <kas@xxxxxxxxxx>
Re: What just happened to my disks/RAID5 array?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: What just happened to my disks/RAID5 array?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: What just happened to my disks/RAID5 array?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: Steven Haigh <netwiz@xxxxxxxxx>
Re: implications of partitioning and raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: SMART, RAID and real world experience of failures.
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: What just happened to my disks/RAID5 array?
- From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: SMART, RAID and real world experience of failures.
- From: Roman Mamedov <rm@xxxxxxxxxx>
SMART, RAID and real world experience of failures.
- From: Steven Haigh <netwiz@xxxxxxxxx>
Re: raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
raid 1 bug with write-mostly and administrative failed disk
- From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
Re: implications of partitioning and raid
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
implications of partitioning and raid
- From: "Peter W. Morreale" <morreale@xxxxxxx>
RE: [PATCH] imsm: fix: correct calculation of UUID
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
[PATCH 1/1] Work around gcc-4.7's strict aliasing checks
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/1] gcc-4.7 build fix
- From: Jes.Sorensen@xxxxxxxxxx
polling mdX/md/degraded in sysfs
- From: Mikhail Balabin <mbalabin@xxxxxxxxx>
[PULL REQUEST] md for 3.3
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: RAID1 fail did not work properly with SSDs
- From: NeilBrown <neilb@xxxxxxx>
RAID1 fail did not work properly with SSDs
- From: "Cal Leeming [Simplicity Media Ltd]" <cal.leeming@xxxxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] imsm: fix: correct calculation of UUID
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
RE: [PATCH] imsm: fix: correct calculation of UUID
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
Spinned down raid drives sometimes not recognized anymore
- From: John Hendrikx <hjohn@xxxxxxxxx>
Re: [PATCH] imsm: fix: correct calculation of UUID
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[PATCH] imsm: fix: correct calculation of UUID
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: NeilBrown <neilb@xxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Paul Richter <iamcomcy@xxxxxxxxx>
Re: Is this RAID recoverable???
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Is this RAID recoverable???
- From: Roman Mamedov <rm@xxxxxxxxxx>
Is this RAID recoverable???
- From: Paul Richter <iamcomcy@xxxxxxxxx>
Re: [PATCH] FIX: Cannot remove failed disk from container
- From: NeilBrown <neilb@xxxxxxx>
Re: Install grub2 to /dev/md126 fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] FIX: Cannot remove failed disk from container
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: NeilBrown <neilb@xxxxxxx>
Re: dirty chunks on bitmap not clearing (RAID1)
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID0 partition set to spare
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: RAID0 partition set to spare
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Install grub2 to /dev/md126 fails
- From: jlcenter@xxxxxxxxxxx
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Michele Codutti <codutti@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Mattias Wadenstein <maswan@xxxxxxxxxx>
Re: RAID0 partition set to spare
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
RAID0 partition set to spare
- From: Steve Carlson <stevengcarlson@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
RAID5 alignment issues with 4K/AF drives (WD green ones)
- From: Michele Codutti <codutti@xxxxxxxxx>
[PATCH] FIX: Cannot remove failed disk from container
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Gordon Henderson <gordon@xxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: Btrfs: blocked for more than 120 seconds, made worse by 3.2 rc7
- From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: It is safe to stop Raid being reshaped
- From: Gordon Henderson <gordon@xxxxxxxxxx>
It is safe to stop Raid being reshaped
- From: Jeremy Thompson <jeremythompson82@xxxxxxxxx>
[PATCH][RFC] RAID5/DMA/memcpy: zero copy the bio page when possible
- From: <b29237@xxxxxxxxxxxxx>
Re: dirty chunks on bitmap not clearing (RAID1)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Re: RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
RAID1 seems not to be able to scrub pending sectors shown by smart
- From: Philip Hands <phil@xxxxxxxxx>
Subject: ANNOUNCE: mdadm 3.2.3 - A tool for managing Soft RAID under Linux
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] md bug fixes for 3.2
- From: NeilBrown <neilb@xxxxxxx>
Re: dirty chunks on bitmap not clearing (RAID1)
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm --monitor as non-root ?
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
Re: [PATCH] FIX: Verify if array name doesn't exist already
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] FIX: Verify if array name doesn't exist already
- From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
Re: Adding a new disk after disk failure on raid6 volume
- From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
Re: Adding a new disk after disk failure on raid6 volume
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Adding a new disk after disk failure on raid6 volume
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Adding a new disk after disk failure on raid6 volume
- From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
RE: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID50, despite chunk setting, does everything in 4KB blocks
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID50, despite chunk setting, does everything in 4KB blocks
- From: Chris Worley <worleys@xxxxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: make messages more understandable
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID50, despite chunk setting, does everything in 4KB blocks
- From: NeilBrown <neilb@xxxxxxx>
RAID50, despite chunk setting, does everything in 4KB blocks
- From: Chris Worley <worleys@xxxxxxxxx>
RE: [PATCH] imsm: make messages more understandable
- From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
[33/45] md/raid5: fix bug that could result in reads from a failed device.
- From: Greg KH <gregkh@xxxxxxx>
Re: [PATCH] imsm: make messages more understandable
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
RE: BUG_ON triggered in worker_enter_idle, after power failure caused potential RAID corruption (kernel 2.6.39.4)
- From: Bruce Stenning <b.stenning@xxxxxxxxxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
[PATCH] imsm: make messages more understandable
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Mount Linux Raid Array on new install
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
RE: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: ''force'' continutation of a rebuild?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: ''force'' continutation of a rebuild?
- From: NeilBrown <neilb@xxxxxxx>
''force'' continutation of a rebuild?
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: RAID5: failing an active component during spare rebuild - arrays hangs
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: Data scribbling for raid6 is wrong?
- From: David Brown <david@xxxxxxxxxxxxxxx>
RE: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: NeilBrown <neilb@xxxxxxx>
Re: Data scribbling for raid6 is wrong?
- From: Tao Guo <glorioustao@xxxxxxxxx>
Re: Data scribbling for raid6 is wrong?
- From: NeilBrown <neilb@xxxxxxx>
Last call for mdadm-3.2.3.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/3] imsm: FIX: UT '08imsm-overlap' fails
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/3] imsm: FIX: Chunk size migration is not possible
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/3] imsm: FIX: 'UT 09imsm-assemble' fails
- From: NeilBrown <neilb@xxxxxxx>
Data scribbling for raid6 is wrong?
- From: Tao Guo <glorioustao@xxxxxxxxx>
Re: Split-Brain Protection for MD arrays
- From: NeilBrown <neilb@xxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: NeilBrown <neilb@xxxxxxx>
Re: ext4 data=writeback performs worse than data=ordered now
- From: Wu Fengguang <fengguang.wu@xxxxxxxxx>
Patch "md/raid5: fix bug that could result in reads from a failed device." has been added to the 3.0-stable tree
- From: <gregkh@xxxxxxx>
Re: [PATCH] md/raid5: fix bug that could result in reads from a failed device.
- From: Greg KH <greg@xxxxxxxxx>
[PATCH] md/raid5: fix bug that could result in reads from a failed device.
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: Troy Telford <ttelford.groups@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: Troy Telford <ttelford.groups@xxxxxxxxx>
Re: RAID-6 disk superblock issue
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-6 disk superblock issue
- From: Mark Knecht <markknecht@xxxxxxxxx>

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