public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: XFS filesystem reports as full though it isn't
Date: Tue, 20 May 2008 16:10:47 +1000	[thread overview]
Message-ID: <20080520061047.GP103491721@sgi.com> (raw)
In-Reply-To: <20080519221057.75e0a775@galadriel.home>

On Mon, May 19, 2008 at 10:10:57PM +0200, Emmanuel Florac wrote:
> Le Sun, 18 May 2008 15:42:08 +0200 vous écriviez:
> 
> > IIRC I tried both, however I'll double check monday...
> 
> Well obviously I didn't try both, because it worked as expected when
> using "inode64". However there'ssomething slightly weird in the data
> layout:
> 
> /dev/dm-0:
> AG     Inodes    IUsed    IFree    Use%
>   0      4288     4277       11     99%
>   1         0        0        0      0%
>   2         0        0        0      0%
.....

If there's no free space in AGs > 0 when you enable inode64, then
you will still get enospc...

> See how all inodes are in the same vg? is it OK?
                                     ^^ AG

This is typical of inode32 allocation...

Cheers,

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

  reply	other threads:[~2008-05-20  6:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 20:27 XFS filesystem reports as full though it isn't Emmanuel Florac
2008-05-18 12:45 ` Emmanuel Florac
2008-05-18 13:18 ` Christoph Hellwig
2008-05-18 13:21   ` Christoph Hellwig
2008-05-18 13:42     ` Emmanuel Florac
2008-05-19 20:10       ` Emmanuel Florac
2008-05-20  6:10         ` David Chinner [this message]
2008-05-20 10:17           ` Emmanuel Florac
2008-05-20 10:19         ` Christoph Hellwig
2008-05-20 12:39           ` Emmanuel Florac
2008-05-19 11:31 ` Christian Røsnes
2008-05-19 11:48   ` Christian Røsnes
2008-05-19 20:39     ` Emmanuel Florac

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=20080520061047.GP103491721@sgi.com \
    --to=dgc@sgi.com \
    --cc=eflorac@intellique.com \
    --cc=hch@infradead.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