From: Patrick Schreurs <patrick@news-service.com>
To: Owen Dunn <osd1000@cam.ac.uk>, xfs@oss.sgi.com
Subject: Re: No space left on device on xfs filesystem with 1.6TB free
Date: Thu, 22 Jan 2009 11:25:13 +0100 [thread overview]
Message-ID: <49784989.1000306@news-service.com> (raw)
In-Reply-To: <20090122030955.GT10158@disturbed>
Dave Chinner wrote:
> You've run out of inode space below 1TB or free space is
> sufficiently fragmented below 1TB that new inode chunks cannot
> be allocated.
Is this related to fs growth or can this happen with any xfs partition?
Thanks,
Patrick Schreurs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-22 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 10:33 No space left on device on xfs filesystem with 1.6TB free Owen Dunn
2009-01-21 17:49 ` Bryon Roche
2009-01-21 20:08 ` Patrick Schreurs
[not found] ` <20090121225453.GN10158@disturbed>
2009-01-22 3:09 ` Dave Chinner
2009-01-22 10:25 ` Patrick Schreurs [this message]
2009-01-22 17:39 ` Eric Sandeen
2009-01-22 14:15 ` Christian Kujau
2009-01-22 23:25 ` Dave Chinner
2009-01-23 8:21 ` Christian Kujau
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=49784989.1000306@news-service.com \
--to=patrick@news-service.com \
--cc=osd1000@cam.ac.uk \
--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