On Tue, Jul 25, 2017 at 07:16:04PM +0200, Emmanuel Florac wrote: > Le Mon, 24 Jul 2017 10:51:25 -0400 > Brian Foster <bfoster@xxxxxxxxxx> écrivait: > > > There are several fixes in-flight for the issues uncovered by this > > metadump. I think you'll want to include the following 3 patches to > > xfsprogs: > > > > http://marc.info/?l=linux-xfs&m=150047977108174&w=2 > > http://marc.info/?l=linux-xfs&m=150040481220074&w=2 > > http://marc.info/?l=linux-xfs&m=150040481820076&w=2 > > > > BTW to which branch do these apply? > > For some reason I've tried xfs_repair 4.12 on another image I had tried > 4.7 and 4.9 on, and... it seems to have repaired it. I'm trying to > understand how that happened... I believe these should apply to for-next. FWIW, the error in your previous mail looks like the one that is fixed by the latter two patches above. Brian > > -- > ------------------------------------------------------------------------ > Emmanuel Florac | Direction technique > | Intellique > | <eflorac@xxxxxxxxxxxxxx> > | +33 1 78 94 84 02 > ------------------------------------------------------------------------ -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
