Thanks for the quick response. I've cloned Linux's master branch (which
has the commit), built it, tested it, and everything works, so it looks
like this was indeed the bug I was seeing (that, or something else
between 4.2.3 and what I tested fixed things).
On 2015-10-21 10:11, Heinz Mauelsha
On 2015-10-21 09:19, Austin S Hemmelgarn wrote:
Hmm, dm-de...@redhat.org seems to have bounced for me. Any ideas why
RedHat would be blocking inbound mail from Google's mail servers?
On 2015-10-20 11:12, Austin S Hemmelgarn wrote:
I think I've stumbled upon a bug in DM-RAID. The primary sympt
On 2015-10-20 11:12, Austin S Hemmelgarn wrote:
I think I've stumbled upon a bug in DM-RAID. The primary symptom is that when
creating a new DM-RAID based device (using either LVM or dmsetup) in a RAID1
configuration, it very quickly claims one by one that all of the disks failed
except the firs
Added dm-devel, which is probably the more appropriate list for dm
things.
NeilBrown
Austin S Hemmelgarn writes:
> I think I've stumbled upon a bug in DM-RAID. The primary symptom is that when
> creating a new DM-RAID based device (using either LVM or dmsetup) in a RAID1
> configuration, it v
I think I've stumbled upon a bug in DM-RAID. The primary symptom is that when
creating a new DM-RAID based device (using either LVM or dmsetup) in a RAID1
configuration, it very quickly claims one by one that all of the disks failed
except the first, and goes degraded. When this happens on a give
5 matches
Mail list logo
