From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ilia Mirkin <imirkin@alum.mit.edu>, xfs@oss.sgi.com
Subject: Re: XFS hung on 2.6.33.3 kernel
Date: Mon, 19 Jul 2010 09:33:20 +1000 [thread overview]
Message-ID: <20100718233320.GB32635@dastard> (raw)
In-Reply-To: <20100718045702.GB6282@infradead.org>
On Sun, Jul 18, 2010 at 12:57:02AM -0400, Christoph Hellwig wrote:
> On Sun, Jul 18, 2010 at 11:20:33AM +1000, Dave Chinner wrote:
> > So, back to the situation with the WARN_ON(). You're running
> > applications that are doing something that:
> >
> > a) is not supported;
> > b) compromises data integrity guarantees;
> > c) is not reliably reported; and
> > d) might be causing hangs
> >
> > Right now I'm not particularly inclined to dig into this further;
> > it's obvious the applications are doing something that is not
> > supported (by XFS or the generic page cache code), so this is the
> > first thing you really need to care about getting fixed if you value
> > your backups...
>
> While it's slightly crazy it's also a pretty easy way for users to shoot
> themselve in their feet. Unlike the generic filesystems with their
> simplistic i_mutex locking we have a way to assure this works properly
> in XFS with the shared/exclusive iolock, so I'm willing to look into
> this further.
Sorry, that wasn't paticularly clear - What I was trying to say is
that I'm not really interested in solving all the generic
buffered/direct IO coherency issues. I agree that it should not
hang, so we do need to find out why it hung....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-07-18 23:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 4:01 XFS hung on 2.6.33.3 kernel Ilia Mirkin
2010-07-18 1:20 ` Dave Chinner
2010-07-18 1:35 ` Ilia Mirkin
2010-07-18 23:50 ` Dave Chinner
2010-08-03 22:30 ` Ilia Mirkin
2010-08-04 0:47 ` Dave Chinner
2010-08-04 1:15 ` Ilia Mirkin
2010-08-04 4:27 ` Dave Chinner
2010-08-04 4:39 ` Ilia Mirkin
2010-08-04 6:53 ` Dave Chinner
2010-08-04 15:40 ` Ilia Mirkin
2010-08-05 5:45 ` Dave Chinner
2010-08-05 6:25 ` Dave Chinner
2010-08-05 6:42 ` Ilia Mirkin
2010-08-07 10:08 ` Dave Chinner
2013-04-04 21:44 ` qiyansun
2010-07-18 4:57 ` Christoph Hellwig
2010-07-18 5:28 ` Ilia Mirkin
2010-07-18 20:17 ` Ilia Mirkin
2010-07-18 23:33 ` Dave Chinner [this message]
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=20100718233320.GB32635@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=imirkin@alum.mit.edu \
--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.