From: Eric Sandeen <sandeen@sandeen.net>
To: raksac@yahoo.com
Cc: xfs@oss.sgi.com
Subject: Re: BUG: soft lockup detected on CPU#1!
Date: Thu, 12 Feb 2009 16:10:44 -0600 [thread overview]
Message-ID: <49949E64.8020904@sandeen.net> (raw)
In-Reply-To: <342331.71207.qm@web30204.mail.mud.yahoo.com>
raksac@yahoo.com wrote:
> Well the problem is the older kernel XFS driver is
> buggy to such a large extent that there is data loss
> even for data on rest should a power loss occur.
>
> With a newer version back port I can preserve the
> kernel version change since it becomes far more
> reaching to the other kernel components and they have
> to move, to which ..... there is strong reservation.
>
> Hope this gives you the perspective.
It's totally understandable why you might want to do it.
It's also totally understandable why upstream developers can't spend a
lot of time on your custom codebase.
What you need, of course, is a distribution with good support for xfs,
so you can make it Someone Else's Problem. :)
-Eric
> Thanks,
> Rakesh
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-12 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 7:16 BUG: soft lockup detected on CPU#1! raksac
2009-02-11 9:21 ` Justin Piszcz
2009-02-11 23:33 ` raksac
2009-02-11 23:36 ` Justin Piszcz
2009-02-12 9:22 ` raksac
2009-02-12 21:55 ` Dave Chinner
2009-02-12 21:59 ` raksac
2009-02-12 22:10 ` Eric Sandeen [this message]
2009-02-12 22:16 ` raksac
2009-02-13 4:56 ` Eric Sandeen
2009-02-19 8:04 ` raksac
2009-02-13 9:32 ` Michael Monnerie
2009-02-11 23:34 ` raksac
2009-02-12 21:49 ` Dave Chinner
2009-02-12 21:55 ` raksac
-- strict thread matches above, loose matches on Subject: below --
2009-02-11 7:57 Rakesh
[not found] <20060717125216.GA15481@planetzork.ping.de>
[not found] ` <1153146608.1218.9.camel@localhost.localdomain>
2006-07-17 14:48 ` Jochen Heuer
2006-07-21 22:53 ` Jochen Heuer
2006-07-21 22:58 ` Jochen Heuer
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=49949E64.8020904@sandeen.net \
--to=sandeen@sandeen.net \
--cc=raksac@yahoo.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