From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com, Dave Chinner <david@fromorbit.com>
Subject: Re: permanent kernel upgrading (was: bug and fun with XFS: unable to handle kernel NULL pointer dereference)
Date: Mon, 26 Jul 2010 07:52:54 +0200 [thread overview]
Message-ID: <201007260752.59573@zmi.at> (raw)
In-Reply-To: <20100726001859.GD655@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 2341 bytes --]
On Montag, 26. Juli 2010 Dave Chinner wrote:
> > # mount /disks/work/
> > # umount /disks/work/
> > umount: /disks/work: device is busy.
> > (In some cases useful info about processes that use
> > the device is found by lsof(8) or fuser(1))
>
> Some other process has taken a reference to the fs, I'd say.
> And if that process triggered an oops, then you'd see this.
This is definitely improbable ;-). I stopped all processes, except sshd
and mingetty (for the console processes), and "lsof" reported no open
files. I'd swear it must be a bug, but as you said 2.6.27 (openSUSE
11.1) is just too old to take care.
> Corrupt attribute fork - matches with the oops signatures. I'd
> definitely consider upgrading your kernel as a first step...
That's why I wrote "which I planned to migrate". I was just in the
process of doing so.
This brings me to another question: openSUSE 11.1 is, despite being old,
still maintained, so I was under the impression that I'd get updates for
problems. But I already received "upgrade your kernel" the last time for
my openSUSE 11.2 with it's kernel vmlinuz-2.6.31.12, which by the time
was the latest release (in the meantime openSUSE 11.3 got released).
So is this just a generic recommendation of developers who love the
bleeding-edge stuff and know how many problems they fixed since 2.6.27
("yak, that old stuff, how could it ever run?"), or is it known that not
enough fixes go into "maintained" kernels by distributions?
I have tons of servers to maintain, and can't compile kernels on my own
anymore (I did this when I was younger), so I used openSUSE and I am in
the process of replacing servers to SLES, which should receive much
better services but still kernel upgrading is not supported on such
platforms. So what is the best practice that one should choose when
running "long time services" where you can't upgrade all the time?
Just curious. :-)
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- 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
next prev parent reply other threads:[~2010-07-26 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 22:19 bug and fun with XFS: unable to handle kernel NULL pointer dereference Michael Monnerie
2010-07-26 0:18 ` Dave Chinner
2010-07-26 5:52 ` Michael Monnerie [this message]
2010-07-26 7:17 ` permanent kernel upgrading (was: bug and fun with XFS: unable to handle kernel NULL pointer dereference) Dave Chinner
2010-07-26 8:43 ` 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=201007260752.59573@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=david@fromorbit.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