On Thu, 2009-04-09 at 00:14 +0200, LCID Fire wrote: > > Most fscks can be told to run read-only so they won't write to the > > device and also interactive so they ask before writing so you should be > > able to avoid recopying. The ext3 journal recovery violates at least one > > of these IIRC (or used to) so if it's ext3 find an option to tell it to > > ignore the journal. > Too late. The journal recovery did complain quite a bit and I didn't > know better than to have it fix the things it liked to fix. Sorry to hear that. Actually our advice should have been to assemble the array read-only, then all manner of fs bugs/features could not write to it. If anyone ever implements the --wild-ass-guess/--recreate mdadm option perhaps that should automatically set read-only? -- 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
