From: Dave Chinner <david@fromorbit.com>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
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, 29 Oct 2012 23:21:11 +1100 [thread overview]
Message-ID: <20121029122111.GR29378@dastard> (raw)
In-Reply-To: <508E3A2E.20901@univ-nantes.fr>
On Mon, Oct 29, 2012 at 09:11:26AM +0100, Yann Dupont wrote:
> Le 29/10/2012 02:25, Dave Chinner a écrit :
> >I can't reproduce this with a similar setup but using KVM (i.e.
> >killing the VM instead of power cycling) or forcing a shutdown of
> >the filesystem without flushing the log. The second case is very
> >much the same as power cycling, but without the potential "power
> >failure caused partial IOs to be written" problem. The only thing
> >I can see in the logprint that I haven't seen so far in my testing
> >is that your log print indicates a checkpoint that wraps the end
> >of the log. I haven't yet hit that situation by chance, so I'll
> >keep trying to see if that's the case that is causing the
> >problem.... Cheers, Dave.
>
> Ok, is your kvm guest was lvm enabled ?
No. The idea being that if it is an XFS problem, then it will show
up without needing LVM. And it did.
> I'll try to recrash the FS, this time I'll make an image of it on
> another machine for further testings. And I'll supply a usefull
> logprint
No need, I have a simple local reproducer now based on your example.
I should be able to find the problem from here....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-29 12:19 UTC|newest]
Thread overview: 21+ 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-23 8:24 ` 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 [this message]
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
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=20121029122111.GR29378@dastard \
--to=david@fromorbit.com \
--cc=Yann.Dupont@univ-nantes.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.