public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Lars Noschinski <lkml@ml.noschinski.de>, linux-kernel@vger.kernel.org
Subject: Re: XFS error & call trace
Date: Fri, 23 Jan 2009 06:51:09 +0100	[thread overview]
Message-ID: <20090123055109.GA25601@x61> (raw)
In-Reply-To: <20090121231435.GA6810@infradead.org>

On Wed, Jan 21, 2009 at 18:14:35 -0500, Christoph Hellwig wrote:
> On Wed, Jan 21, 2009 at 11:27:03PM +0100, Lars Noschinski wrote:
> > Hello!
> > 
> > I just had a crash of my XFS file system on 2.6.29-rc1 (syslog output
> > follows) After this, the file system on /home returned -EIO on most (all?)
> > operations.  After a reboot from cdrom, I found it interesting to see that
> > xfs_check found no error on this partition. Instead, the XFS on the /
> > partition had a lot of errors.
> 
> The patch below from Dave Chinner fixes it:
> 
> ---
> 
> [XFS] Long btree pointers are still 64 bit on disk
> 
> On 32 bit machines with CONFIG_LBD=n, XFS reduces the
> in memory size of xfs_fsblock_t to 32 bits so that it
> will fit within 32 bit addressing. However, the disk format
> for long btree pointers are still 64 bits in size.
> 
> The recent btree rewrite failed to take this into account

Hi,

does this commit also fix http://lkml.org/lkml/2009/1/7/324 ?

Regards,
Tino

  reply	other threads:[~2009-01-23  5:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 22:27 XFS error & call trace Lars Noschinski
2009-01-21 23:14 ` Christoph Hellwig
2009-01-23  5:51   ` Tino Keitel [this message]
2009-01-24  3:23     ` Christoph Hellwig

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=20090123055109.GA25601@x61 \
    --to=tino.keitel@gmx.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@ml.noschinski.de \
    /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