From: David Chinner <dgc@sgi.com>
To: "Christian Røsnes" <christian.rosnes@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c
Date: Tue, 11 Mar 2008 23:21:03 +1100 [thread overview]
Message-ID: <20080311122103.GP155407@sgi.com> (raw)
In-Reply-To: <1a4a774c0803110419n645da456leaedd98593300726@mail.gmail.com>
On Tue, Mar 11, 2008 at 12:19:29PM +0100, Christian Røsnes wrote:
> On Tue, Mar 11, 2008 at 10:34 AM, David Chinner <dgc@sgi.com> wrote:
> >
> > On Tue, Mar 11, 2008 at 09:08:31AM +0100, Christian Røsnes wrote:
>
> > > I'll try to add some printk statements to the codepaths you mentioned,
> > > and see where it leads.
> >
> > Definitely worth confirming this is where the error is coming from.
> >
>
> if (tagno == agno) {
> printk("XFS: xfs_dialloc:0021\n");
> *inop = NULLFSINO;
> return noroom ? ENOSPC : 0;
> }
>
> seems to be what triggers this inside xfs_dialloc.
>
> Here a trace which give some indication to the codepath taken inside
> xfs_dialloc (xfs_ialloc.c):
Yup, that's trying to allocate in each AG and failing. Almost certainly
the problem is the described alignment issue.
FYI, I'm travelling tomorrow so I won't really get a chance to look
at this more until thursday....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-03-11 12:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 10:51 XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c Christian Røsnes
2008-02-13 11:04 ` Justin Piszcz
2008-02-13 11:44 ` Christian Røsnes
2008-02-13 21:45 ` David Chinner
2008-02-14 8:41 ` Christian Røsnes
2008-03-05 13:53 ` Christian Røsnes
2008-03-06 11:10 ` Christian Røsnes
2008-03-07 11:19 ` Christian Røsnes
2008-03-10 0:08 ` David Chinner
2008-03-10 8:34 ` Christian Røsnes
2008-03-10 10:02 ` Christian Røsnes
2008-03-10 22:21 ` David Chinner
2008-03-11 8:08 ` Christian Røsnes
2008-03-11 9:34 ` David Chinner
2008-03-11 11:19 ` Christian Røsnes
2008-03-11 12:21 ` David Chinner [this message]
2008-03-11 12:39 ` Christian Røsnes
[not found] ` <20080312232425.GR155407@sgi.com>
[not found] ` <1a4a774c0803130114l3927051byd54cd96cdb0efbe7@mail.gmail.com>
[not found] ` <20080313090830.GD95344431@sgi.com>
[not found] ` <1a4a774c0803130214x406a4eb9wfb8738d1f503663f@mail.gmail.com>
[not found] ` <20080313092139.GF95344431@sgi.com>
[not found] ` <1a4a774c0803130227l2fdf4861v21183b9bd3e7ce8d@mail.gmail.com>
[not found] ` <20080313113634.GH95344431@sgi.com>
[not found] ` <1a4a774c0803130446x609b9cb2mf3da323183c35606@mail.gmail.com>
2008-03-13 14:53 ` David Chinner
2008-03-14 9:02 ` Christian Røsnes
2008-03-09 22:59 ` David Chinner
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=20080311122103.GP155407@sgi.com \
--to=dgc@sgi.com \
--cc=christian.rosnes@gmail.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 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.