From: Dave Chinner <david@fromorbit.com>
To: Miquel van Smoorenburg <mikevs@xs4all.net>,
Oliver Pinter <oliver.pntr@gmail.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
xfs@oss.sgi.com, xfs-masters@oss.sgi.com
Subject: Re: [xfs-masters] Re: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c
Date: Sat, 14 Jun 2008 01:36:01 +1000 [thread overview]
Message-ID: <20080613153601.GF3700@disturbed> (raw)
In-Reply-To: <20080613072405.GA3474@anita>
On Fri, Jun 13, 2008 at 09:24:05AM +0200, Konstantin Kletschke wrote:
> Am 2008-06-13 13:08 +1000 schrieb Dave Chinner:
>
> > This commit in 2.6.26 will probably fix it.
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=75de2a91c98a6f486f261c1367fe59f5583e15a3
>
> Well, the description points out solving issues regarding dealing with
> ENOSPC shutting the fs not down when it is not really necessary. Does
> this count here, where my fs is
> /dev/sda7 120G 12G 108G 10% /home
> with inode usage of
> /dev/sda7 125001728 1310022 123691706 2% /home
Perhaps you've fragmented free space, which can lead to this
problem. Inodes require contiguous free space to be allocated.
Please search the mail list archive for this error to find more
about triaging the cause (i.e. the thread that led up to finding
the above problem).
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-06-13 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:30 XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c lists
2008-06-12 14:33 ` Oliver Pinter
2008-06-12 22:24 ` [xfs-masters] " Eric Sandeen
2008-06-13 7:15 ` Konstantin Kletschke
2008-06-12 22:27 ` Miquel van Smoorenburg
2008-06-13 3:08 ` Dave Chinner
2008-06-13 7:24 ` Konstantin Kletschke
2008-06-13 15:36 ` Dave Chinner [this message]
2008-06-13 11:28 ` Miquel van Smoorenburg
2008-06-16 15:50 ` Miquel van Smoorenburg
2008-06-17 5:31 ` Dave Chinner
2008-06-20 5:27 ` Konstantin Kletschke
2008-06-20 5:45 ` Konstantin Kletschke
2008-06-22 22:53 ` Dave Chinner
2008-06-23 7:58 ` Konstantin Kletschke
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=20080613153601.GF3700@disturbed \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikevs@xs4all.net \
--cc=oliver.pntr@gmail.com \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox