Le 30/10/2012 02:33, Dave Chinner a écrit :
Not really a huge chase, just a simple matter of isolation. The patch below should fix the problem.
Yes, it does. Thanks a lot for the fast answer and this one-letter-patch !
However, the fact that recovery succeeded on 3.4 means you may have a corrupted filesystem. The bug has been present since 3.0-rc1 (which was a fix for vmap memory leaks), and recovery is trying to replay stale items from the previous log buffer. As such, it is possible that changes from a previous checkpoint to have overwritten more recent changes in the current checkpoint. As such, you should
Ouch.
probably run xfs_repair -n over the filesystems that you remounted on 3.4 that failed on 3.6 just to make sure they are OK.
Will do. As someone else pointed out, I think it should go to stable release. Thanks a lot for your time, Cheers -- Yann Dupont - Service IRTS, DSI Université de Nantes Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@xxxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
