Re: Raid1 problem can't add remove or mark faulty -- it did work

On Saturday March 26, [EMAIL PROTECTED] wrote: > i have a strange problem -- can't get a fully funtional 2 drive raid > back up running-- it may or may not be a drive bios interaction don't > know. none of the mdadm manage functions will work add remove or mark faulty > i have purged and reinstal

Re: [PATCH md ] md: allow degraded raid1 array to resync after an unclean shutdown.

> The following is (I think) appropriate for 2.4.30. The bug it fixes > can result in data corruption in a fairly unusual circumstance (having > a 3 drive raid1 array running in degraded mode, and suffering a system > crash). What's unusual? Having a 3 drive raid1 array? It's not unusual for a

Raid1 problem can't add remove or mark faulty -- it did work

i have a strange problem -- can't get a fully funtional 2 drive raid back up running-- it may or may not be a drive bios interaction don't know. none of the mdadm manage functions will work add remove or mark faulty i have purged and reinstalled the mdadm package twice. below is all the info i c

forcing larger block sizes?

it's obvious in retrospect, but I was recently surprised to find how huge a difference it makes to use larger blocks with raid, especially raid5. (a large, aligned r5 write can avoid parity reads, and thus *flies*!). so how do you get the filesystem to produce larger IOs? "large" here is much l