Linux RAID Storage Date Index

Thread Index

Re: Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: [RFC PATCH 0/4] md/mdadm: introduce request function mode support
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: [RFC PATCH 0/4] md/mdadm: introduce request function mode support
- From: Roberto Spadim <rspadim@xxxxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Dag Nygren <dag@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Failed RAID5 & recovery advise
- From: Henry Golas <Henry.Golas@xxxxxxxxxxx>
Re[2]: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
Re: [RFC PATCH 0/4] md/mdadm: introduce request function mode support
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
Re: 3.16-rc1 kernel BUG triggered at mutex.c:586
- From: Mike Galbraith <umgwanakikbuti@xxxxxxxxx>
Re[2]: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
PATCH: align-spelling-of-md
- From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re[2]: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Phil Turmel <philip@xxxxxxxxxx>
3.16-rc1 kernel BUG triggered at mutex.c:586
- From: Vlad Yasevich <vyasevich@xxxxxxxxx>
Re[2]: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
Re: raid5.c::grow_stripes() kmem_cache_create() race
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: PATCH: RAID10-layout-descriptions
- From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: How to fix this superblock?
- From: Pete <psid@xxxxxxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: How to fix this superblock?
- From: NeilBrown <neilb@xxxxxxx>
How to fix this superblock?
- From: Pete <psid@xxxxxxxxxxxxxxxx>
Re: PATCH: RAID10-layout-descriptions
- From: NeilBrown <neilb@xxxxxxx>
Re: Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
PATCH: RAID10-layout-descriptions
- From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
Found duplicate PV: using /dev/sda3 not /dev/md1
- From: Rainer Fügenstein <rfu@xxxxxxxxxx>
Re: RAID newbie, 1 vs 5, chunk sizes
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
RAID newbie, 1 vs 5, chunk sizes
- From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: "ptschack ." <ptschack@xxxxxxxxxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: NeilBrown <neilb@xxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: "ptschack ." <ptschack@xxxxxxxxxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: NeilBrown <neilb@xxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: "ptschack ." <ptschack@xxxxxxxxxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: "ptschack ." <ptschack@xxxxxxxxxxxxxx>
Re: Help with corrupted MDADM Raid6
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH] Forbid merging with partially assembled IMSM array
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
Help with corrupted MDADM Raid6
- From: "ptschack ." <ptschack@xxxxxxxxxxxxxx>
Re: WD Red vs SE/RE drives for mdadm RAID1 (TLER?)
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: md-raid paranoia mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: md-raid paranoia mode?
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: md-raid paranoia mode?
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: md-raid paranoia mode?
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: raid5.c::grow_stripes() kmem_cache_create() race
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Do not set default 'before.layout' when reshaping from RAID4 to RAID4
- From: NeilBrown <neilb@xxxxxxx>
Re: md-raid paranoia mode?
- From: Mattias Wadenstein <maswan@xxxxxxxxxx>
Re: md-raid paranoia mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: md-raid paranoia mode?
- From: NeilBrown <neilb@xxxxxxx>
Re: md-raid paranoia mode?
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: WD Red vs SE/RE drives for mdadm RAID1 (TLER?)
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: WD Red vs SE/RE drives for mdadm RAID1 (TLER?)
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: md-raid paranoia mode?
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: md-raid paranoia mode?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
raid5.c::grow_stripes() kmem_cache_create() race
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
WD Red vs SE/RE drives for mdadm RAID1 (TLER?)
- From: Mark Knecht <markknecht@xxxxxxxxx>
RE: [PATCH] Do not set default 'before.layout' when reshaping from RAID4 to RAID4
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
Re: md-raid paranoia mode?
- From: Bart Kus <me@xxxxxxxx>
Re: Unable to re-assemble a raid 10 after it has FAILED.
- From: Alberto Morell <amp4tj@xxxxxxxxx>
md-raid paranoia mode?
- From: Bart Kus <me@xxxxxxxx>
Re: md kernel thread hung in raid1_add_disk
- From: NeilBrown <neilb@xxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: Fwd: Unable to re-assemble a raid 10 after it has FAILED.
- From: "John Stoffel" <john@xxxxxxxxxxx>
md kernel thread hung in raid1_add_disk
- From: Matthias Eble <psychotrahe@xxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Unable to re-assemble a raid 10 after it has FAILED.
- From: NeilBrown <neilb@xxxxxxx>
Fwd: Unable to re-assemble a raid 10 after it has FAILED.
- From: Alberto Morell <amp4tj@xxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: [patch 1/1] raid5: speedup sync_request processing
- From: NeilBrown <neilb@xxxxxxx>
Re: mismatches after growing raid1 and re-adding a failed drive
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: NeilBrown <neilb@xxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
[patch 1/1] raid5: speedup sync_request processing
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
[patch 1/1] raid5: speedup sync_request processing
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Wolfgang Denk <wd@xxxxxxx>
Re: RAID-10 explicitly defined drive pairs?
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
Re: Recovering RAID set after OS disk failed
- From: Davide Guarisco <guarisco@xxxxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: writing zeros to bad sector results in persistent read error
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
writing zeros to bad sector results in persistent read error
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
mismatches after growing raid1 and re-adding a failed drive
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Recovering data from a shrunk RAID 10 array
- From: NeilBrown <neilb@xxxxxxx>
ANNOUNCE: mdadm 3.3.1 - A tool for managing md Soft RAID under Linux
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Forbid merging with partially assembled IMSM array
- From: NeilBrown <neilb@xxxxxxx>
deadlock between retry_aligned_read with barrier io
- From: hui jiao <simonjiaoh@xxxxxxxxx>
[RFC PATCH 4/4] mdadm: introduce '--use-requestfn' create/assembly option
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[RFC PATCH 3/4] md: handle IO latency accounting in rqfn mode
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[RFC PATCH 2/4] md: introduce request function mode support
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[RFC PATCH 1/4] md: complete bio accounting and add io_latency extension
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[RFC PATCH 0/4] md/mdadm: introduce request function mode support
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Recovering data from a shrunk RAID 10 array
- From: RedShift <redshift@xxxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
RE: [PATCH] Forbid merging with partially assembled IMSM array
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
Re: Recovering RAID set after OS disk failed
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: Recovering RAID set after OS disk failed
- From: Davide Guarisco <guarisco@xxxxxxxxxxxxx>
Re: [patch 1/1] raid0: discard requests do not align to chunk boundary
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
Re: [PATCH] Forbid merging with partially assembled IMSM array
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 1/1] raid0: discard requests do not align to chunk boundary
- From: NeilBrown <neilb@xxxxxxx>
[patch 1/1] raid0: discard requests do not align to chunk boundary
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: Roberto Spadim <rspadim@xxxxxxxxx>
RE: [PATCH] Forbid merging with partially assembled IMSM array
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
RE: [PATCH 1/1] md: Do only necessary operations when adding device to RO array
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Recovering RAID set after OS disk failed
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: Recovering RAID set after OS disk failed
- From: Davide Guarisco <guarisco@xxxxxxxxxxxxx>
Re: [PULL REQUEST - 3.15] to md bugfixes, tagged for -stable
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST - 3.15] to md bugfixes, tagged for -stable
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: retry load_and_parse_mpb if we suspect mdmon has made modifications
- From: NeilBrown <neilb@xxxxxxx>
Re: Home desktop/server RAID upgrade
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: [PATCH] imsm: retry load_and_parse_mpb if we suspect mdmon has made modifications
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
RE: Recovering RAID set after OS disk failed
- From: Kővári Péter <peter@xxxxxxxxxxxxxx>
Re: [RFC] Process requests instead of bios to use a scheduler
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: [RFC] Process requests instead of bios to use a scheduler
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC] Process requests instead of bios to use a scheduler
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Recovering RAID set after OS disk failed
- From: Davide Guarisco <guarisco@xxxxxxxxxxxxx>
Re: [PATCH 2/2] Grow: Do not fork via systemd if freeze_reshape is set
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] Grow: Use 'forked' also for reshape_container in Grow_continue
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: retry load_and_parse_mpb if we suspect mdmon has made modifications
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/1] md: Do only necessary operations when adding device to RO array
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Do not set default 'before.layout' when reshaping from RAID4 to RAID4
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Forbid merging with partially assembled IMSM array
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC] Process requests instead of bios to use a scheduler
- From: NeilBrown <neilb@xxxxxxx>
Re: How to identify a failed md array
- From: NeilBrown <neilb@xxxxxxx>
Help fixing broken array after power loss
- From: "Andrew Hodgetts" <andrew.hodgetts@xxxxxxxxxxxxxx>
Re: How to identify a failed md array
- From: Sebastian Herbszt <herbszt@xxxxxx>
Re: Home desktop/server RAID upgrade
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: Roberto Spadim <rspadim@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Home desktop/server RAID upgrade
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Home desktop/server RAID upgrade
- From: Mark Knecht <markknecht@xxxxxxxxx>
FW: [PATCH 2/2] Grow: Do not fork via systemd if freeze_reshape is set
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
FW: [PATCH 1/2] Grow: Use 'forked' also for reshape_container in Grow_continue
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
[PATCH 1/1] md: Do only necessary operations when adding device to RO array
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
[PATCH] Do not set default 'before.layout' when reshaping from RAID4 to RAID4
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
[PATCH] Forbid merging with partially assembled IMSM array
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
[PATCH] imsm: retry load_and_parse_mpb if we suspect mdmon has made modifications
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Keep existing slot number after replacing drive
- From: Thomas Leuxner <tlx@xxxxxxxxxxx>
[patch] DM RAID: fix a couple integer overflows
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: NeilBrown <neilb@xxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: NeilBrown <neilb@xxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: forumscollective@xxxxxxxxx
Re: How to identify a failed md array
- From: NeilBrown <neilb@xxxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: NeilBrown <neilb@xxxxxxx>
RE: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
- From: "Li, Zhen-Hua" <zhen-hual@xxxxxx>
Re: Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: [PATCH 1/1] driver/md/block: Alloc space for member flush_rq
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[RFC] Process requests instead of bios to use a scheduler
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: [patch 1/3]raid5: adjust order of some operations in handle_stripe
- From: Shaohua Li <shli@xxxxxxxxxx>
[PATCH 1/1] driver/md/block: Alloc space for member flush_rq
- From: "Li, Zhen-Hua" <zhen-hual@xxxxxx>
Re: Which RAID do you recommend for home use?
- From: linuxmasterjedi@xxxxxxx
Re: [patch 1/3]raid5: adjust order of some operations in handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 1/3]raid5: adjust order of some operations in handle_stripe
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 1/3]raid5: adjust order of some operations in handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 1/1] raid5: avoid release list until last reference of the stripe
- From: NeilBrown <neilb@xxxxxxx>
[patch 1/1] raid5: avoid release list until last reference of the stripe
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
Re: Which RAID do you recommend for home use?
- From: Matt Garman <matthew.garman@xxxxxxxxx>
Which RAID do you recommend for home use?
- From: "L. M. J" <linuxmasterjedi@xxxxxxx>
"not enough operational devices (2/4 failed)" Can I recover?
- From: Steve Lorimer <steve.lorimer@xxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: NeilBrown <neilb@xxxxxxx>
Understanding raid array status: Active vs Clean
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: George Duffield <forumscollective@xxxxxxxxx>
How to identify a failed md array
- From: Sebastian Herbszt <herbszt@xxxxxx>
Re: bcache errors
- From: roma1390 <roma1390@xxxxxxxxx>
Re: Seeking help fixing a failed array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
color box, display box, corrugated box, color card, blister card, color sleeve, hang tag, label
- From: Jinghao Printing - CHINA <dewaynerw5v@xxxxxxxxx>
Re: Seeking help fixing a failed array
- From: Marnitz Gray <marnitz@xxxxxxxxxxxxxx>
Re: Seeking help fixing a failed array
- From: Marnitz Gray <marnitz@xxxxxxxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: NeilBrown <neilb@xxxxxxx>
Aiming for release of mdadm-3.3.1 next week (early June)
- From: NeilBrown <neilb@xxxxxxx>
Re: Seeking help fixing a failed array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Seeking help fixing a failed array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
md raid hanging in raid1 rebuild
- From: Thilo Molitor <thilo@xxxxxxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: Dylan Distasio <interzone@xxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: Seeking help fixing a failed array
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
Seeking help fixing a failed array
- From: Marnitz Gray <marnitz@xxxxxxxxxxxxxx>
Re: Broken raid 5
- From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
Invalid bitmap file superblock: bad magic
- From: "Liu H.T" <liuhongtong86@xxxxxxxxx>
[PATCH] md: Use time_in_range()
- From: Manuel Schölling <manuel.schoelling@xxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
[patch 3/3]raid5: reduce handle_stripe() called times for full stripe write
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 1/3]raid5: adjust order of some operations in handle_stripe
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 2/3]raid5: make raid_run_ops take reference of ops_request
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: Broken raid 5
- From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
Re: Rebuilding a RAID5 array after drive (hardware) failure
- From: NeilBrown <neilb@xxxxxxx>
Rebuilding a RAID5 array after drive (hardware) failure
- From: George Duffield <forumscollective@xxxxxxxxx>
Re: [PATCH] mdadm: Do not reimplment offsetof
- From: NeilBrown <neilb@xxxxxxx>
Broken raid 5
- From: "L. M. J" <linuxmasterjedi@xxxxxxx>
[PATCH] mdadm: Do not reimplment offsetof
- From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: NeilBrown <neilb@xxxxxxx>
Re: Stuck array after reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: System freeze triggered by RAID 10 resync and high io
- From: NeilBrown <neilb@xxxxxxx>
System freeze triggered by RAID 10 resync and high io
- From: christian.schwarz@xxxxxxxxx
Stuck array after reshape
- From: Davíð Steinn Geirsson <david@xxxxxx>
Re: Stuck array after reshape
- From: Davíð Steinn Geirsson <david@xxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: NeilBrown <neilb@xxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: Patrik Horník <patrik@xxxxxx>
Re: evacuating drives in a RAID10 array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [RFC]raid5: adjust operation order of handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
Re: IMSM - problem with reshape+systemd
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 9/13] md: make return of 0 explicit
- From: NeilBrown <neilb@xxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: NeilBrown <neilb@xxxxxxx>
evacuating drives in a RAID10 array
- From: Bryan Carmula <bryancarmula@xxxxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: bcache errors
- From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
bcache errors
- From: roma1390 <roma1390@xxxxxxxxx>
[PATCH 0/13] make return of 0 explicit
- From: Julia Lawall <Julia.Lawall@xxxxxxx>
[PATCH 9/13] md: make return of 0 explicit
- From: Julia Lawall <Julia.Lawall@xxxxxxx>
Re: [RFC]raid5: adjust operation order of handle_stripe
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC]raid5: adjust operation order of handle_stripe
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: High CPU usage / low speed when reading from degraded RAID6
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
High CPU usage / low speed when reading from degraded RAID6
- From: Patrik Horník <patrik@xxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
RE: IMSM - problem with reshape+systemd
- From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
Re: Data offset
- From: Patrik Horník <patrik@xxxxxx>
Re: Data offset
- From: NeilBrown <neilb@xxxxxxx>
Data offset
- From: Patrik Horník <patrik@xxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: Patrik Horník <patrik@xxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: NeilBrown <neilb@xxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: Patrik Horník <patrik@xxxxxx>
Re: IMSM - problem with reshape+systemd
- From: NeilBrown <neilb@xxxxxxx>
Re: boot fails incrementally starting raid arrays
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[RFC]raid5: adjust operation order of handle_stripe
- From: Shaohua Li <shli@xxxxxxxxxx>
[GIT PULL REQUEST] two bug fixes for md - both tagged for -stable.
- From: NeilBrown <neilb@xxxxxxx>
boot fails incrementally starting raid arrays
- From: Steven <steven-e@xxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
Re: Big mistake while changing a RAID5 disk (was Corrupted ext4 filesystem ...)
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: task mdadm blocked when stopping array, 3.15rc3
- From: NeilBrown <neilb@xxxxxxx>
Big mistake while changing a RAID5 disk (was Corrupted ext4 filesystem ...)
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
task mdadm blocked when stopping array, 3.15rc3
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: [PATCH] Fix race between --create and --incremental
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Fix race between --create and --incremental
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: [PATCH] Create: don't default to bitmap=internal when it is not supported
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Raid6 Root crashed
- From: Dragon <Sunghost@xxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: NeilBrown <neilb@xxxxxxx>
[RFC]raid5: add an option to avoid copy data from bio to stripe cache
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [PATCH] Create: don't default to bitmap=internal when it is not supported
- From: NeilBrown <neilb@xxxxxxx>
Re: Re-creating/Fixing Raid5 from superblock Info
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Re-creating/Fixing Raid5 from superblock Info
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re-creating/Fixing Raid5 from superblock Info
- From: "Meyer, Adrian" <adrian_meyer@xxxxxxxxxxx>
Is disk order relative or are the numbers absolute?
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L. M. J" <linuxmasterjedi@xxxxxxx>
Re: Why would a recreation cause a different number of blocks??
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Why would a recreation cause a different number of blocks??
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Why would a recreation cause a different number of blocks??
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Why would a recreation cause a different number of blocks??
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: Why would a recreation cause a different number of blocks??
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Repaired the sectors of a drive, how do I get the md to assemble and start degraded?
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Why would a recreation cause a different number of blocks??
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Repaired the sectors of a drive, how do I get the md to assemble and start degraded?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: NeilBrown <neilb@xxxxxxx>
Why would a recreation cause a different number of blocks??
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Repaired the sectors of a drive, how do I get the md to assemble and start degraded?
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: Repaired the sectors of a drive, how do I get the md to assemble and start degraded?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Repaired the sectors of a drive, how do I get the md to assemble and start degraded?
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 10/11] imsm: assemble cache volumes
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 02/11] make must_be_container() more selective
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 01/11] sysfs: fix sysfs_set_array() to accept valid negative array levels
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: NeilBrown <neilb@xxxxxxx>
[RFC mdadm PATCH 08/11] imsm: read cache metadata
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 09/11] imsm: examine cache configurations
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 06/11] imsm: immutable volume id
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 11/11] imsm: support cache enabled arrays
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 04/11] Assemble: teardown partially assembled arrays
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 07/11] imsm: cache metadata definitions
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 05/11] Examine: support for coalescing "cache legs"
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 03/11] Assemble: show the uuid in the verbose case
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC mdadm PATCH 00/11] Intel(R) Smart Response Technology mdadm enumeration/assembly
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 0/3] Base compatibility support for Intel(R) Smart Response Technology
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 3/3] md/isrt: write support
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 2/3] md/isrt: read support
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 1/3] md/isrt: base infrastructure and metadata loading
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Corrupted ext4 filesystem after mdadm manipulation error
- From: "L.M.J" <linuxmasterjedi@xxxxxxx>
Re: IMSM - problem with reshape+systemd
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: Pasi Kärkkäinen <pasik@xxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
raid 10 only spares showing
- From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
Re: Cry for help before I screw up a raid recovery more...
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: Cry for help before I screw up a raid recovery more...
- From: Andrew Ryder <tireman@xxxxxxx>
Re: Cry for help before I screw up a raid recovery more...
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: Cry for help before I screw up a raid recovery more...
- From: Andrew Ryder <tireman@xxxxxxx>
Cry for help before I screw up a raid recovery more...
- From: Jeff Wiegley <jeffw@xxxxxxxx>
Re: md disk fault communication code
- From: NeilBrown <neilb@xxxxxxx>
Re: md disk fault communication code
- From: Sonu a <p10sonu@xxxxxxxxx>
Re: md disk fault communication code
- From: NeilBrown <neilb@xxxxxxx>
md disk fault communication code
- From: Sonu a <p10sonu@xxxxxxxxx>
Re: dmcrypt on top of raid5, or raid5 on top of dmcrypt?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
[GIT PULL REQUEST] one md BUG-fix for 3.15-rc
- From: NeilBrown <neilb@xxxxxxx>
Re: dmcrypt on top of raid5, or raid5 on top of dmcrypt?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
[PATCH] Create: don't default to bitmap=internal when it is not supported
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: Force mdadm to not prompt the user
- From: Francis Moreau <francis.moro@xxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [patch]raid5: delete another BUG_ON
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: Force mdadm to not prompt the user
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch]raid5: delete another BUG_ON
- From: NeilBrown <neilb@xxxxxxx>
Force mdadm to not prompt the user
- From: Francis Moreau <francis.moro@xxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: NeilBrown <neilb@xxxxxxx>
[patch]raid5: delete another BUG_ON
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: Drew <drew.kay@xxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
Re: Some info given by 'mdadm --detail --export' are not convenient to use
- From: bobzer <bobzer@xxxxxxxxx>
Re: cannot re-assmble mdadm array
- From: NeilBrown <neilb@xxxxxxx>
Re: Guess the size of a RAID{5,6} device
- From: NeilBrown <neilb@xxxxxxx>
Re: Some info given by 'mdadm --detail --export' are not convenient to use
- From: Francis Moreau <francis.moro@xxxxxxxxx>
Re: Guess the size of a RAID{5,6} device
- From: Francis Moreau <francis.moro@xxxxxxxxx>
cannot re-assmble mdadm array
- From: Andrew Ryder <tireman@xxxxxxx>
Re: Guess the size of a RAID{5,6} device
- From: NeilBrown <neilb@xxxxxxx>
Re: Some info given by 'mdadm --detail --export' are not convenient to use
- From: NeilBrown <neilb@xxxxxxx>
[GIT PULL REQUEST] md for 3.15
- From: NeilBrown <neilb@xxxxxxx>
dmcrypt on top of raid5, or raid5 on top of dmcrypt?
- From: Marc MERLIN <marc@xxxxxxxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
Some info given by 'mdadm --detail --export' are not convenient to use
- From: Francis Moreau <francis.moro@xxxxxxxxx>
Re: Hardware advice for software raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH] Fix race between --create and --incremental
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Guess the size of a RAID{5,6} device
- From: Francis Moreau <francis.moro@xxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
RE: Nvidia Raid5 Failure‏
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
Re: Nvidia Raid5 Failure
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[no subject]
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
Nvidia Raid5 Failure
- From: peter davidson <merrymeetpete@xxxxxxxxxxx>
Re: [PATCH] Fix race between --create and --incremental
- From: NeilBrown <neilb@xxxxxxx>
Re: Hardware advice for software raid
- From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
[PATCH] Fix race between --create and --incremental
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: [patch]raid5: get_active_stripe avoids device_lock
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch]raid5: make_request does less prepare wait
- From: NeilBrown <neilb@xxxxxxx>
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: [patch]raid5: get_active_stripe avoids device_lock
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch]raid5: make_request does less prepare wait
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch]raid5: get_active_stripe avoids device_lock
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch]raid5: make_request does less prepare wait
- From: NeilBrown <neilb@xxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Assistance needed with a failed RAID-5 array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
[patch]raid5: get_active_stripe avoids device_lock
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch]raid5: make_request does less prepare wait
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: Hardware advice for software raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Hardware advice for software raid
- From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
Assistance needed with a failed RAID-5 array
- From: Alan Worstell <aworstell@xxxxxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
RE: Problem Syncing raid1
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
Re: Problem Syncing raid1
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Problem Syncing raid1
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Problem Syncing raid1
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: NeilBrown <neilb@xxxxxxx>
RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
RE: Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
Re: Problem Syncing raid1
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Problem Syncing raid1
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Problem Syncing raid1
- From: Christian Schmitz <schnet@xxxxxxxxxxx>
Re: Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
[LVM/RAID BUG DATA DESTRUCTION] 3.12.14 raid1 initialisation + --write-mostly destroys LV
- From: David Lamparter <equinox@xxxxxxxxxx>
Re: [linux-lvm] [LVM/RAID BUG DATA DESTRUCTION] 3.12.14 raid1 initialisation + --write-mostly destroys LV
- From: David Lamparter <equinox@xxxxxxxxxx>
RE: Can't grow IMSM RAID5
- From: "Paszkiewicz, Artur" <artur.paszkiewicz@xxxxxxxxx>
Re: Hardware advice for software raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
Re: strange status raid 5
- From: bobzer <bobzer@xxxxxxxxx>
Re: strange status raid 5
- From: NeilBrown <neilb@xxxxxxx>
Re: Hardware advice for software raid
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Hardware advice for software raid
- From: Matt Garman <matthew.garman@xxxxxxxxx>
Hardware advice for software raid
- From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
Re: Can't grow IMSM RAID5
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
Re: Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
Re: Can't grow IMSM RAID5
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Catalin Marinas <catalin.marinas@xxxxxxx>
Can't grow IMSM RAID5
- From: "nixbugz" <nixbugz@xxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
Re: strange status raid 5
- From: bobzer <bobzer@xxxxxxxxx>
Re: strange status raid 5
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
strange status raid 5
- From: bobzer <bobzer@xxxxxxxxx>
Re: Raid10 to Raid0 conversion
- From: Marcin Wanat <mwanat@xxxxxxxxx>
Re: RAIS5 Rebuild Help - Possible Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
Re: RAIS5 Rebuild Help - Possible Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: RAIS5 Rebuild Help - Possible Data Offset
- From: Yorik <yoriks13@xxxxxxxxxxxxxx>
Re: Raid10 to Raid0 conversion
- From: NeilBrown <neilb@xxxxxxx>
Re: RAIS5 Rebuild Help - Possible Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: Check/repair command?
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6check.c patches
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 3.2 108/200] md/raid5: Fix CPU hotplug callback registration
- From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
Re: raid resync speed
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Tide <lovetide@xxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Tide <lovetide@xxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size
- From: Tide <lovetide@xxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Tide <lovetide@xxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Tide <lovetide@xxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
raid6check.c patches
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: Larry Fenske <LFenske@xxxxxxx>
Array created by mdadm 3.2 & 3.3 have different array size, why?
- From: "Tide" <lovetide@xxxxxx>
[PATCH] dm cache: remove unused function too_many_discard_blocks
- From: SeongJae Park <sj38.park@xxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH] fix write-mostly logic
- From: "Vladimir B. Savkin" <master@xxxxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: Missing superblocks from almost all my drives
- From: Caspar Smit <c.smit@xxxxxxxxxx>
Re: Missing superblocks from almost all my drives
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Missing superblocks from almost all my drives
- From: Mark Munoz <mark.munoz@xxxxxxxxxxxxxxxxxxx>
Check/repair command?
- From: Phillip Susi <psusi@xxxxxxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
[PATCH] drivers/md: Use RCU_INIT_POINTER(x, NULL) in dm.c
- From: Monam Agarwal <monamagarwal123@xxxxxxxxx>
Re: Raid10 to Raid0 conversion
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Raid10 to Raid0 conversion
- From: Marcin Wanat <mwanat@xxxxxxxxx>
patch: raid5: avoid release list until last reference
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
Re: raid resync speed
- From: Jeff Allison <jeff.allison@xxxxxxxxxxxxxxx>
Re: raid resync speed
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: raid resync speed
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: raid resync speed
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: raid resync speed
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
RE: raid6 - data intefrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
raid resync speed
- From: Jeff Allison <jeff.allison@xxxxxxxxxxxxxxx>
Re: [PATCH 2/2] md: fix deadlock while suspending RAID array
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/1] Work around architectures having statfs.f_type defined as long
- From: NeilBrown <neilb@xxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH 1/1] Work around architectures having statfs.f_type defined as long
- From: Arnd Bergmann <arnd@xxxxxxxx>
[PATCH 0/1] Work around systems defining statfs.f_type as long
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/1] Work around architectures having statfs.f_type defined as long
- From: Jes.Sorensen@xxxxxxxxxx
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH 0/2] md: fix fix deadlock while suspending RAID array
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: [PATCH 2/2] md: Add support for RAID-1 consistency check feature
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] md: Add configurability for consistency check feature
- From: NeilBrown <neilb@xxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Catalin Marinas <catalin.marinas@xxxxxxx>
[PATCH 1/2] md: Add configurability for consistency check feature
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
[PATCH 2/2] md: Add support for RAID-1 consistency check feature
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
[PATCH 0/2] md: Add consistency check feature for level-1 RAID
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
[PATCH] md: Fixed issue in raid1 that may lead to data corruption
- From: Ralph Mueck <linux-kernel@xxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: NeilBrown <neilb@xxxxxxx>
Re: Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
"Free swap" drops during raid data-check
- From: Rolf Fokkens <rolf@xxxxxxxxxxxxxx>
Re: raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Raid stalls during --replace and other disk activity...
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid stalls during --replace and other disk activity...
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Raid stalls during --replace and other disk activity...
- From: Phil Turmel <philip@xxxxxxxxxx>
[PATCH] raid6check.c: move manual repair code to separate function
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
[PATCH] raid6check.c: move autorepair code to separate function
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
[PATCH] raid6check.c: lock the stripe until necessary
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Recent 3.x kernels: Memory leak causing OOMs
- From: Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>
Raid stalls during --replace and other disk activity...
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: mapping disk sectors to files
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: mapping disk sectors to files
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
mapping disk sectors to files
- From: Thorsten von Eicken <tve@xxxxxxxxxxxxx>
Re: Growing RAID5 SSD Array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
Re: calculating optimal chunk size for Linux software-RAID
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
Growing RAID5 SSD Array
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: NeilBrown <neilb@xxxxxxx>
Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: Linux software-RAID and bootloader
- From: Martin T <m4rtntns@xxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: calculating optimal chunk size for Linux software-RAID
- From: Martin T <m4rtntns@xxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: Raul Dias <raul@xxxxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: David Brown <david.brown@xxxxxxxxxxxx>
RE: raid6 - data integrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx>
Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
[PATCH] poll/wait/md: allow module to safely support 'poll' on /proc files
- From: NeilBrown <neilb@xxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: Replace RAID devices without resorting to degraded mode?
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
[PATCH 1/2] md: move up mddev locking functions
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
[PATCH 2/2] md: fix deadlock while suspending RAID array
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
[PATCH 0/2] md: fix fix deadlock while suspending RAID array
- From: Simon Guinot <simon.guinot@xxxxxxxxxxxx>
Replace RAID devices without resorting to degraded mode?
- From: "Scott D'Vileskis" <sdvileskis@xxxxxxxxx>
Re: calculating optimal chunk size for Linux software-RAID
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: [PATCH] mdmon@.service: Change type of process start-up to 'forking'.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid6 - data intefrity issue - data mis-compare on rebuilding RAID 6 - with 100 Mb resync speed.
- From: NeilBrown <neilb@xxxxxxx>
Re: grub and mdadm
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: grub and mdadm
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: NeilBrown <neilb@xxxxxxx>
grub and mdadm
- From: AdsGroup <AdsGroup@xxxxxxx>
Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
Re: Linux software-RAID and bootloader
- From: Raul Dias <raul@xxxxxxxxxxx>
Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
Re: I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
I've made a bit of a mess in my raid setup
- From: Federico Foschini <undicizeri@xxxxxxxxx>
Re: calculating optimal chunk size for Linux software-RAID
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Linux software-RAID and bootloader
- From: Martin T <m4rtntns@xxxxxxxxx>
Re: calculating optimal chunk size for Linux software-RAID
- From: Martin T <m4rtntns@xxxxxxxxx>
Re: Is mdadm.conf needed?
- From: Martin T <m4rtntns@xxxxxxxxx>
Re: calculating optimal chunk size for Linux software-RAID
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Is mdadm.conf needed?
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Is mdadm.conf needed?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: Linux software-RAID and bootloader
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: Is mdadm.conf needed?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Linux software-RAID and bootloader
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: randconfig build error with next-20140307, in drivers/md/dm-era-target.c
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Linux software-RAID and bootloader
- From: Martin T <m4rtntns@xxxxxxxxx>
Is mdadm.conf needed?
- From: Martin T <m4rtntns@xxxxxxxxx>
calculating optimal chunk size for Linux software-RAID
- From: Martin T <m4rtntns@xxxxxxxxx>
Re: Grow on RAID 6 failed can I revert back to previous total drives?
- From: Jared Raddigan <jraddigan@xxxxxxx>
[PATCH] mdmon@.service: Change type of process start-up to 'forking'.
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
Re: RAID 10 problems, two disks marked as spare
- From: Jim Bauwens <jim@xxxxxxx>
Grow on RAID 6 failed can I revert back to previous total drives?
- From: Jared Raddigan <jraddigan@xxxxxxx>
Re: RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
Re: raid5 write latency is 10x the drive latency
- From: NeilBrown <neilb@xxxxxxx>
Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: RAID5 hard freeze
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: External USB-SATA bridge rewriting logical block sizes
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: raid5 write latency is 10x the drive latency
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
[PATCH 3.8 59/67] md/raid5: Fix CPU hotplug callback registration
- From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
Re: External USB-SATA bridge rewriting logical block sizes
- From: Jan Kundrát <jkt@xxxxxxxxxx>
Re: External USB-SATA bridge rewriting logical block sizes
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
raid5 write latency is 10x the drive latency
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
External USB-SATA bridge rewriting logical block sizes
- From: Jan Kundrát <jkt@xxxxxxxxxx>
Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: NeilBrown <neilb@xxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: NeilBrown <neilb@xxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Raid 5 events not updates after resync
- From: John <linux_mailing@xxxxxxxxxxxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: [md PATCH 00/10] md patches for 3.5: RAID10 reshape
- From: Phillip Susi <psusi@xxxxxxxxxx>
Re: RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
Re: [md PATCH 00/10] md patches for 3.5: RAID10 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 00/10] md patches for 3.5: RAID10 reshape
- From: Phillip Susi <psusi@xxxxxxxxxx>
Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
RAID 10 problems, two disks marked as spare
- From: jim@xxxxxxx
Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
[PATCH 2/2] imsm: improved platform capabilities checking
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
[PATCH 1/2] imsm: support for second AHCI controller in EFI mode
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
[PATCH 0/2] imsm: fixes for platform capabilities checking
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: Recovering RAID-6 from a Failed Grow
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
[PATCH] md / procfs: avoid Oops if md-mod removed while /proc/mdstat is being polled.
- From: NeilBrown <neilb@xxxxxxx>
Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: NeilBrown <neilb@xxxxxxx>
Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
Re: RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: md raid6: slow resync if fs is mounted rw
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
how to handle bad sectors in md control areas?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: Reshape RAID10 -> RAID1
- From: Charles Polisher <cpolish@xxxxxxxxxxxx>
Recovering RAID-6 from a Failed Grow
- From: Karl Wilbur <karl@xxxxxxxxxxxxxx>
Re: Reshape RAID10 -> RAID1
- From: NeilBrown <neilb@xxxxxxx>
Reshape RAID10 -> RAID1
- From: Charles Polisher <cpolish@xxxxxxxxxxxx>
Re: Cannot assemble DDF raid
- From: NeilBrown <neilb@xxxxxxx>
Re: md raid6: slow resync if fs is mounted rw
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: md raid6: slow resync if fs is mounted rw
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
md raid6: slow resync if fs is mounted rw
- From: Jakob Unterwurzacher <jakobunt@xxxxxxxxx>
Re: [PATCH] dm-raid: check events in super_validate
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
Re: [PATCH] dm-raid: check events in super_validate
- From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
Re: dm thin: inverted down_trylock() test
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: mdadm won't remove drive from array
- From: Caspar Smit <c.smit@xxxxxxxxxx>
[patch] dm thin: inverted down_trylock() test
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: NeilBrown <neilb@xxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Questions regarding bad block management
- From: NeilBrown <neilb@xxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: [PATCH] dm-raid: check events in super_validate
- From: NeilBrown <neilb@xxxxxxx>
Re: non-persistent superblocks? [WORKAROUND]
- From: NeilBrown <neilb@xxxxxxx>
Re: feature re-quest for "re-write"
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5 hard freeze
- From: NeilBrown <neilb@xxxxxxx>
Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: NeilBrown <neilb@xxxxxxx>
Re: request help with RAID1 array that endlessly attempts to sync
- From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
RAID5 hard freeze
- From: Denis Golovan <denis.golovan@xxxxxxxxx>
Re: mdadm won't remove drive from array
- From: NeilBrown <neilb@xxxxxxx>
Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
[PATCH v5 2/3] fs: btrfs: Adds new par3456 modes to support up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
[PATCH v5 3/3] btrfs-progs: Adds new par3456 modes to support up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
[PATCH v5 0/3] New RAID library supporting up to six parities
- From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
Re: raid 'check' does not provoke expected i/o error
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
[3.8.y.z extended stable] Patch "md/raid5: Fix CPU hotplug callback registration" has been added to staging queue
- From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
Re: mdadm won't remove drive from array
- From: Caspar Smit <c.smit@xxxxxxxxxx>
AW: AW: AW: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
Re: QNAP 8 port RAID5 md0 recovery of missing MBR and md superblocks
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Data Offset
- From: wiebittewas <wiebittewas@xxxxxxxxxxxxxx>
Re: mdadm won't remove drive from array
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
mdadm won't remove drive from array
- From: Caspar Smit <c.smit@xxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: What is the sector size in /sys/block/md*/md items?
- From: NeilBrown <neilb@xxxxxxx>
Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: feature re-quest for "re-write"
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
What is the sector size in /sys/block/md*/md items?
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
mdadm may fail to assemble clean raid5 array with failed drive
- From: Eivind Sarto <eivindsarto@xxxxxxxxx>
feature re-quest for "re-write"
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: raid 'check' does not provoke expected i/o error
- From: Larry Fenske <LFenske@xxxxxxx>
[PATCH 3.5 54/60] md/raid5: Fix CPU hotplug callback registration
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
[3.5.y.z extended stable] Patch "md/raid5: Fix CPU hotplug callback registration" has been added to staging queue
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
[PATCH 3.11 102/121] md/raid5: Fix CPU hotplug callback registration
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
[3.11.y.z extended stable] Patch "md/raid5: Fix CPU hotplug callback registration" has been added to staging queue
- From: Luis Henriques <luis.henriques@xxxxxxxxxxxxx>
Re: AW: raid 'check' does not provoke expected i/o error
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
AW: raid 'check' does not provoke expected i/o error
- From: "Samer, Michael (I/ET-83, extern)" <extern.michael.samer@xxxxxxx>
raid 'check' does not provoke expected i/o error
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Cannot assemble DDF raid
- From: Christian Iversen <ci@xxxxxxxxxx>
[PATCH 3.4 21/25] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
[PATCH 3.10 58/66] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
[PATCH 3.12 73/82] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
[PATCH 3.13 90/99] md/raid5: Fix CPU hotplug callback registration
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Re: [PATCH] bcache: fix NULL pointer deref in blk_add_request_payload
- From: Lars Ellenberg <lars@xxxxxxxxxx>
[PATCH] bcache: fix NULL pointer deref in blk_add_request_payload
- From: Lars Ellenberg <lars@xxxxxxxxxx>
Re: Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@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]