> > > What happened was: > > > - a device (sdg1) was added as a write-mostly member to a degraded > > > two-member RAID1 (md3) and started recovering; > > > > May I be so frank as to guessing you found an old drive and added as > > write-mostly? sdg is the bad drive here… > > This is correct, but I should note that I did not add it as > write-mostly just > because it's an older drive, but because it is my normal set-up for > md3: > a RAID1 mirror of a fast SSD (sdf) and a write-mostly HDD (sdg in this > case). This makes perfectly sense, but the HDD obviously isn't good, and perhaps some data were bad on the SSD as well. I'd replace the HDD with something else, perhaps after a badblocks test, and at least with a short SMART test, and rebuild. The errors on the filesystem should be solveable with an fsck. If not, well, I hope you have a good backup… -- Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 98013356 roy@xxxxxxxxxxxxx http://blogg.karlsbakk.net/ GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
