All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Chris Knadle <Chris.Knadle@coredump.us>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: assfail during unmount xfs 2.6.24.3 [from 2.6.24.y git]
Date: Sat, 8 Mar 2008 09:46:45 +1100	[thread overview]
Message-ID: <20080307224645.GW155259@sgi.com> (raw)
In-Reply-To: <200803062329.10486.Chris.Knadle@coredump.us>

On Thu, Mar 06, 2008 at 11:29:07PM -0500, Chris Knadle wrote:
> During the final unmount before reboot there was an assertion failure from XFS 
> leading to the debug output below; I've included what was available on the 
> screendump, which I handwrote + transcribed.  [I also have screenshots from a 
> 2.1 MP camera -- they're slightly ugly but usable.]  CONFIG_KEXEC was not 
> compiled in, so I was uanble to get a crashdump via SysRq.  I'm sending this 
> along in case someone working on the XFS fs can find + fix a bug.  I'm not 
> sending the kernel config in this first post just as not to spam everybody 
> with it if it's not needed -- if desired just ask and I'll send it.
> Source used: 2.6.24.y from git -- 2.6.24.3.
> 
> This is on my Desktop box, x86 system -- single P4 CPU @ 2.6 GHz, IDE disk 
> attached to an onboard HighPoint HPT370 controller, and running Debian Sid.
> 
> When replying please CC me, as I am not currently subscribed to the list.
......
> Assertion failed: atomic_read(&mp->m_active_trans) == 0, file: 
> fs/xfs/xfs_vfsops.c, line: 708

Known problem. Race in the VFS w.r.t. read-only remounts:

http://marc.info/?l=linux-kernel&m=120106649923499&w=2

The fix for the problem lies outside XFS:

http://marc.info/?l=linux-kernel&m=120109304227035&w=2

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2008-03-07 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  4:29 assfail during unmount xfs 2.6.24.3 [from 2.6.24.y git] Chris Knadle
2008-03-07 22:46 ` David Chinner [this message]
2008-03-08 20:55   ` Chris Knadle
2008-03-09 22:18     ` David Chinner
2008-03-10  6:10       ` 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=20080307224645.GW155259@sgi.com \
    --to=dgc@sgi.com \
    --cc=Chris.Knadle@coredump.us \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.