From: Stian Jordet <liste@jordet.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs bug in 2.6.17.9?
Date: Fri, 25 Aug 2006 01:47:43 +0200 [thread overview]
Message-ID: <1156463263.19666.7.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0608240942180.30908@p34.internal.lan>
tor, 24,.08.2006 kl. 09.42 -0400, skrev Justin Piszcz:
> Aug 24 09:22:09 buick kernel: xfs_da_do_buf: bno 16777216
>
> That is the bug from 2.6.17 -> 2.6.17.6.
>
> It was patched in 2.6.17.7, but I assume(?) if you never fixed your FS to
> begin with, you will still have the problem. Read the XFS FAQ, and backup
> your data before you do that :)
As I just wrote to Martin, I did run a couple of those kernels. But even
with updated xfsprogs I can't fix the errors... Is that "normal", or am
I in deep trouble?
Best regards,
Stian
next prev parent reply other threads:[~2006-08-25 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 9:45 xfs bug in 2.6.17.9? Stian Jordet
2006-08-24 12:29 ` Martin Steigerwald
2006-08-24 23:45 ` Stian Jordet
2006-08-24 13:42 ` Justin Piszcz
2006-08-24 23:47 ` Stian Jordet [this message]
2006-08-25 1:58 ` Nathan Scott
2006-08-25 6:15 ` Stian Jordet
2006-08-25 8:38 ` Stian Jordet
2006-08-25 5:08 ` Chris Wedgwood
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=1156463263.19666.7.camel@localhost.localdomain \
--to=liste@jordet.net \
--cc=jpiszcz@lucidpixels.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