From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs warnings on kernel 3.2.15
Date: Mon, 13 Aug 2012 17:47:40 +0200 [thread overview]
Message-ID: <3610628.Nzf1PdJg2L@saturn> (raw)
In-Reply-To: <20120811225742.GH2877@dastard>
[-- Attachment #1.1: Type: text/plain, Size: 925 bytes --]
Am Sonntag, 12. August 2012, 08:57:42 schrieb Dave Chinner:
> 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....
Je compris. As it's such a longstandig bug, I guess it won't happen too
often worldwide. Or at least doesn't get reportet. I've had it twice in
several months, and I'll run 3.6 ASAP. Thanks for investigating!
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-08-13 15:47 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
2012-08-13 15:47 ` Michael Monnerie [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=3610628.Nzf1PdJg2L@saturn \
--to=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