messages from 2011-07-21 02:58:49 to 2011-08-01 15:33:06 UTC [more...]
[PATCH] fix: segfault when killing subarray of non-existent container
2011-08-01 15:33 UTC
Assembling array with missing members
2011-08-01 11:17 UTC (4+ messages)
linux-next: build warnings after merge of the moduleh tree
2011-08-01 0:35 UTC (3+ messages)
Do I have a bad HDD?
2011-07-31 23:56 UTC (8+ messages)
component device mismatches found: 9600
2011-07-31 18:32 UTC (2+ messages)
upgrading the superblock version
2011-07-31 4:47 UTC (3+ messages)
data scrubbing
2011-07-29 22:37 UTC (8+ messages)
RAID 1 using SSD and 2 HDD
2011-07-29 18:31 UTC (17+ messages)
` Failures Rates Using SSD
RAID5/6 Offload via IOATDMA
2011-07-29 15:01 UTC (4+ messages)
` "
Using the new bad-block-log in md for Linux 3.1
2011-07-28 12:53 UTC (13+ messages)
[md PATCH 00/36] md patches for 3.1 - part 2: bad block logs
2011-07-28 1:39 UTC (57+ messages)
` [md PATCH 03/36] md: don't allow arrays to contain devices with bad blocks
` [md PATCH 04/36] md: load/store badblock list from v1.x metadata
` [md PATCH 01/36] md: beginnings of bad block management
` [md PATCH 02/36] md/bad-block-log: add sysfs interface for accessing bad-block-log
` [PATCH v2] md: add documentation for bad block log
` [md PATCH 10/36] md/raid1: avoid writing to known-bad blocks on known-bad drives
` [md PATCH 12/36] md/raid1: store behind-write pages in bi_vecs
` [md PATCH 09/36] md: make it easier to wait for bad blocks to be acknowledged
` [md PATCH 11/36] md/raid1: clear bad-block record when write succeeds
` [md PATCH 06/36] md/raid1: avoid reading from known bad blocks
` [md PATCH 08/36] md: add 'write_error' flag to component devices
` [md PATCH 13/36] md/raid1: Handle write errors by updating badblock log
` [md PATCH 14/36] md/raid1: record badblocks found during resync etc
` [md PATCH 07/36] md/raid1: avoid reading known bad blocks during resync
` [md PATCH 05/36] md: Disable bad blocks and v0.90 metadata
` [md PATCH 15/36] md/raid1: improve handling of read failure during recovery
` [md PATCH 16/36] md/raid1: factor several functions out or raid1d()
` [md PATCH 32/36] md/raid10: attempt to fix read errors during resync/check
` [md PATCH 26/36] md/raid10 - avoid reading from known bad blocks - part 3
` [md PATCH 31/36] md/raid10: Handle write errors by updating badblock log
` [md PATCH 25/36] md/raid10: avoid reading from known bad blocks - part 2
` [md PATCH 34/36] md/raid10: simplify read error handling during recovery
` [md PATCH 28/36] md/raid10 record bad blocks as needed "
` [md PATCH 30/36] md/raid10: clear bad-block record when write succeeds
` [md PATCH 33/36] md/raid10: record bad blocks due to write errors during resync/recovery
` [md PATCH 29/36] md/raid10: avoid writing to known bad blocks on known bad drives
` [md PATCH 27/36] md/raid10: avoid reading known bad blocks during resync/recovery
` [md PATCH 35/36] md/raid10: Handle read errors during recovery better
` [md PATCH 36/36] md/raid10: handle further errors during fix_read_error better
[Patch mdadm-3.2.2] Fix readding of a readwrite drive into a writemostly array
2011-07-27 18:34 UTC
[Patch mdadm-3.2.2] Fix the fix for the readd bug
2011-07-27 18:30 UTC
standard performance (write speed 20Mb/s)
2011-07-27 13:54 UTC (15+ messages)
` standard performance (write speed ??Mb/s) - new raid5 array
Grub-install, superblock corrupted/erased and other animals
2011-07-27 12:16 UTC
[patch] md/raid10: double lock typo in handle_read_error()
2011-07-27 10:59 UTC (2+ messages)
Repairing a Raid-6 array
2011-07-26 22:41 UTC (2+ messages)
[md PATCH 00/34] md patches for 3.1 - part 1
2011-07-26 15:01 UTC (48+ messages)
` [md PATCH 06/34] md/raid5: Remove use of sh->lock in sync_request
` [md PATCH 09/34] md/raid5: move common code into handle_stripe
` [md PATCH 11/34] md/raid5: add some more fields to stripe_head_state
` [md PATCH 10/34] md/raid5: unify stripe_head_state and r6_state
` [md PATCH 08/34] md/raid5: replace sh->lock with an 'active' flag
` [md PATCH 07/34] md/raid5: Protect some more code with ->device_lock
` [md PATCH 12/34] md/raid5: move stripe_head_state and more code into handle_stripe
` [md PATCH 18/34] md/raid5: move more common "
` [md PATCH 17/34] md/raid5: unite handle_stripe_dirtying5 and handle_stripe_dirtying6
` [md PATCH 19/34] md/raid5: move some more common code into handle_stripe
` [md PATCH 13/34] md/raid5: Move code for finishing a reconstruction "
` [md PATCH 14/34] md/raid5: move more code into common handle_stripe
` [md PATCH 15/34] md/raid5: rearrange a test in fetch_block6
` [md PATCH 16/34] md/raid5: unite fetch_block5 and fetch_block6
` [md PATCH 20/34] md/raid5: finalise new merged handle_stripe
Problems with raid after reboot
2011-07-26 8:37 UTC (9+ messages)
[PATCH] RAID-6 check standalone
2011-07-26 5:25 UTC (16+ messages)
` [PATCH] RAID-6 check standalone code cleanup
` [PATCH] RAID-6 check standalone suspend array
` [PATCH] RAID-6 check standalone suspend array V2.0
[PATCH] mdadm.8: Disk coercion with IMSM metadata
2011-07-26 5:15 UTC (5+ messages)
[PATCH] Grow: fix version number in error message
2011-07-26 4:31 UTC (2+ messages)
RAID5/6 Offload
2011-07-25 23:44 UTC
mdadm striped parity RAID with Advanced Format drives
2011-07-25 18:57 UTC (13+ messages)
Ticket Number (7PWYZ2011)
2011-07-25 14:25 UTC
[RFC PATCH 4/4] btrfs: Moved repair code from inode.c to extent_io.c
2011-07-25 8:52 UTC
standard performance (write speed 20Mb/s)
2011-07-25 6:39 UTC (13+ messages)
` standard performance (write speed 65Mb/s)
how to recover filesystem after clobbering array?
2011-07-23 19:04 UTC (7+ messages)
REPLY ASAP
2011-07-22 17:35 UTC
linux-next: Tree for July 21 (drivers/md/dm-raid)
2011-07-22 16:25 UTC (5+ messages)
` [dm-devel] "
` [PATCH -next] dm: fix dm-flakey printk warning
` [dm-devel] "
Confusion with setting up new RAID6 with mdadm
2011-07-22 5:17 UTC (4+ messages)
[PATCH 1/1] md: style/readability cleanups
2011-07-22 4:42 UTC
Raid5 boot failure after grow
2011-07-21 15:18 UTC (5+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).