From mboxrd@z Thu Jan 1 00:00:00 1970 From: "L. M. J" Subject: Re: Corrupted ext4 filesystem after mdadm manipulation error Date: Fri, 25 Apr 2014 13:43:17 +0200 Message-ID: <2ecef7f1-fde7-48c9-87bf-47ff617956b3@email.android.com> References: <20140424070548.445497dd@netstation> <20140424194832.2d0a867f@netstation> <20140424203506.5fdee0d3@netstation> <20140424215654.0447d300@netstation> <20140425071340.1ac35ded@netstation> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Mikael Abrahamsson Cc: Scott D'Vileskis , "linux-raid@vger.kernel.org" List-Id: linux-raid.ids On 25 avril 2014 08:04:13 CEST, Mikael Abrahamsson w= rote: >On Fri, 25 Apr 2014, L.M.J wrote: > >> Well, what should I do now ? mkfs everything and restart from scratc= h >? > >Most likely this is your only option. First you overwrote the >superblocks=20 >so the drives came in the wrong order (most likely) and then you ran a= =20 >read/write fsck on it. > >The thing to do is to make sure md is read only and use fsck in=20 >readonly-mode as a diagnostics tool to see if everything is right. If >you=20 >get it wrong and do fsck in read/write mode it's going to change thing= s > >destructively. I haven't done a R/W fuck yet, only on LVM snapshot to test, never on r= eal data.=20 Does it change anything?=20 --=20 May the open source be with you my young padawan.=20 Envoy=C3=A9 de mon t=C3=A9l=C3=A9phone, excusez la bri=C3=A8vet=C3=A9. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html