mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: xfs bug in 2.6.26-rc9
Date: Fri, 11 Jul 2008 12:21:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.1.10.0807111215040.30192@uplift.swm.pp.se> (raw)
In-Reply-To: <20080711084248.GU29319@disturbed>

On Fri, 11 Jul 2008, Dave Chinner wrote:

> That aside, what was the assert failure reported prior to the oops? i.e. 
> paste the lines in the log before the ---[ cut here ]--- line? One of 
> them will start with 'Assertion failed:', I think....

These ones?

Jul  8 04:44:56 via kernel: [554197.888008] Assertion failed: whichfork == XFS_ATTR_FORK || ip->i_delayed_blks == 0, file: fs/xfs/xfs_bmap.c, line: 5879
Jul  9 03:25:21 via kernel: [42940.748007] Assertion failed: whichfork == XFS_ATTR_FORK || ip->i_delayed_blks == 0, file: fs/xfs/xfs_bmap.c, line: 5879

I'll happily rebuild the kernel without the debug option and do xfs_check 
to weed out any possible logical problem with the volume, if you don't 
need any further information from the current state of my volume.

I should also say that this assert failue happened two nights in a row so 
I guess it's fairly reproducible (didn't happen on the 10th, and today, 
the 11th it seems to have panic:ed around 03:30 (I start the 
defragmentation via cron at 03:00) which I think is related.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2008-07-11 10:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11  7:46 Mikael Abrahamsson
2008-07-11  8:42 ` Dave Chinner
2008-07-11 10:21   ` Mikael Abrahamsson [this message]
2008-07-14  7:30     ` Dave Chinner
2008-07-14  8:16       ` Mikael Abrahamsson
2008-07-14  7:34     ` Lachlan McIlroy
2008-07-14 12:13       ` Dave Chinner
2008-07-15  2:12         ` Lachlan McIlroy
2008-07-15  3:18           ` Dave Chinner
2008-07-15  6:17         ` Nick Piggin
2008-07-15 12:22           ` Christoph Hellwig
2008-07-16  4:12             ` Nick Piggin
2008-07-11 19:02   ` Sebastian Siewior
2008-07-11 19:52     ` Eric Sandeen
2008-07-11 23:22     ` Dave Chinner
2008-07-12  5:06       ` Sebastian Siewior

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=alpine.DEB.1.10.0807111215040.30192@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®