From: Krzysztof Adamski <k@adamski.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS disk half full, yet it is reporting out of disk (linux)
Date: Fri, 21 Aug 2009 23:30:53 -0400 [thread overview]
Message-ID: <1250911853.8535.26.camel@oxygen.netxsys.com> (raw)
In-Reply-To: <20090822031317.GA20065@puku.stupidest.org>
On Fri, 2009-08-21 at 20:13 -0700, Chris Wedgwood wrote:
> On Fri, Aug 21, 2009 at 07:06:56PM -0400, Krzysztof Adamski wrote:
>
> > I'm running a 64bit kernel Linux (Debian Lenny) self compiled kernel
> > 2.6.30.4. I have created a 5T xfs filesystem, it is about half full
> > but I get "No space left on device"
> >
> > Here is the output of df:
> > gen:/fstore-1# df .
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > /dev/mapper/mega--raid--1-fstore--1
> > 5265707008 2711698716 2554008292 52% /fstore-1
> > gen:/fstore-1# df -i .
> > Filesystem Inodes IUsed IFree IUse% Mounted on
> > /dev/mapper/mega--raid--1-fstore--1
> > 1053167616 736704 1052430912 1% /fstore-1
> > gen:/fstore-1# >abc
> > -bash: abc: No space left on device
> >
> > What limit did I hit?
>
> lower 2T of disk full? so it might have trouble allocating free space
> for inodes
>
> does remoutning with inode64 help?
Yes, that helped, thanks.
The explanation in the man page for mount of the inode64 is not clear on
the effect of this option.
K
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-08-22 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 23:06 XFS disk half full, yet it is reporting out of disk (linux) Krzysztof Adamski
[not found] ` <20090822031317.GA20065@puku.stupidest.org>
2009-08-22 3:30 ` Krzysztof Adamski [this message]
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=1250911853.8535.26.camel@oxygen.netxsys.com \
--to=k@adamski.org \
--cc=cw@f00f.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