From: Dave Chinner <david@fromorbit.com>
To: Jeff Breidenbach <jeff@jab.org>
Cc: xfs@oss.sgi.com
Subject: Re: read only remount not so happy
Date: Tue, 16 Sep 2008 15:56:14 +1000 [thread overview]
Message-ID: <20080916055614.GX5811@disturbed> (raw)
In-Reply-To: <e03b90ae0809152103w5653bdbfrc1f060d9e41e7246@mail.gmail.com>
On Mon, Sep 15, 2008 at 09:03:41PM -0700, Jeff Breidenbach wrote:
> This is starting to go downhill. Everything is still running, but some
> processes that interact with the filesystem actions are performing
> slowly.
>
> ===
>
>
> [9608310.848311] Assertion failed: atomic_read(&mp->m_active_trans) ==
> 0, file: /build/buildd/linux-2.6.24/fs/xfs/xfs_vfsops.c, line: 708
Known problem. Race in the VFS code - fix is due in 2.6.28, I think.
Details can be found by googling the error message. Reboot the system.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-09-16 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 2:04 read only remount not so happy Jeff Breidenbach
2008-09-16 4:03 ` Jeff Breidenbach
2008-09-16 5:56 ` Dave Chinner [this message]
2008-09-16 18:29 ` Christoph Hellwig
2008-09-18 5:29 ` Jeff Breidenbach
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=20080916055614.GX5811@disturbed \
--to=david@fromorbit.com \
--cc=jeff@jab.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