From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestreams option toxic ?)
Date: Mon, 05 Nov 2012 14:57:49 +0100 [thread overview]
Message-ID: <5097C5DD.3090305@univ-nantes.fr> (raw)
In-Reply-To: <20121030013309.GX29378@dastard>
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@univ-nantes.fr
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-05 13:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 14:14 Is kernel 3.6.1 or filestreams option toxic ? Yann Dupont
2012-10-23 8:24 ` Problems with kernel 3.6.x (vm ?) (was : Is kernel 3.6.1 or filestreams option toxic ?) Yann Dupont
2012-10-25 15:21 ` Yann Dupont
2012-10-25 20:55 ` Yann Dupont
2012-10-25 21:10 ` Dave Chinner
2012-10-26 10:03 ` Yann Dupont
2012-10-26 22:05 ` Yann Dupont
2012-10-28 23:48 ` Dave Chinner
2012-10-29 1:25 ` Dave Chinner
2012-10-29 8:11 ` Yann Dupont
2012-10-29 12:21 ` Dave Chinner
2012-10-29 12:18 ` Dave Chinner
2012-10-29 12:43 ` Yann Dupont
2012-10-30 1:33 ` Dave Chinner
2012-10-31 11:45 ` Gaudenz Steinlin
2012-11-05 13:57 ` Yann Dupont [this message]
2012-10-29 8:07 ` Yann Dupont
2012-10-29 8:17 ` Yann Dupont
-- strict thread matches above, loose matches on Subject: below --
2012-11-28 9:39 reste donewell
2012-11-28 20:37 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5097C5DD.3090305@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox