From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs warnings on kernel 3.2.15
Date: Sun, 12 Aug 2012 08:57:42 +1000 [thread overview]
Message-ID: <20120811225742.GH2877@dastard> (raw)
In-Reply-To: <6314061.2K1xYxIYlT@saturn>
On Sat, Aug 11, 2012 at 12:50:45PM +0200, Michael Monnerie wrote:
> Am Freitag, 10. August 2012, 08:15:18 schrieb Dave Chinner:
> > The freeze/thaw deadlock is not fixed in 3.5 and i think it missed
> > 3.6 as well so you're going to be waiting until 3.7 for this to be
> > fixed, I suspect....
>
> OK, at least you guys have a plan for a fix. I'm happy to get that fixed
> soon. Thank you.
It got included late in the 3.6-rc1 cycle, so it will be in 3.6.
> But when I think about it: Isn't that worth a backport fix? VMware isn't
> a seldom used piece of software, and we use NetApp Storage with
> snapshots, which is also used a lot worldwide. I can imagine others have
> the same problem, or is it just me?
It's a problem that has been around for, well, since freeze was
first introduced many, many years ago. And the complexity of the fix
(20+ patch series, IIRC) makes it a difficult and time consuming fix
that requires a lot of testing - it touches the VFS and has changes
all through different filesystems, including XFS. I just can't see
anyone other than enterprise distro vendors spending that much
effort to back port such an intrusive fix....
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-08-11 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 11:01 xfs warnings on kernel 3.2.15 Michael Monnerie
2012-08-09 22:15 ` Dave Chinner
2012-08-11 10:50 ` Michael Monnerie
2012-08-11 22:57 ` Dave Chinner [this message]
2012-08-13 15:47 ` Michael Monnerie
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=20120811225742.GH2877@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--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