From: Timothy Sesow <tsesow@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: No space left on device on xfs filesystem with 7.7TB free
Date: Sun, 27 Mar 2011 07:25:12 -0600 [thread overview]
Message-ID: <4D8F3AB8.4050803@timsesow.com> (raw)
In-Reply-To: <4D8E0774.1070200@sandeen.net>
I had the same problem recently and couldn't go to
inode64, so I put a writeup at
http://osvault.blogspot.com/2011/03/fixing-1tbyte-inode-problem-in-xfs-file.html
on what I did to find the files in the lower allocation groups
and move them.
On 03/26/2011 09:34 AM, Eric Sandeen wrote:
> On 3/26/11 8:41 AM, atyu30 atyu30 wrote:
>>
>> I'm running RedHat Linux Enterprise Server 5.2, on a 64-bit x86_64
>> Linux machine with kernel version 2.6.18-128.el5 smp. I appear to
>> have version 2.9.4 of xfsprogs.
> Just as point of reference, if you're using the xfs-kmod, that is
> extremely old, un-updated, and unsupported at this point.
>
>> I have a 22TB xfs filesystem ,Yesterday, the hard disk is full, today
>> released a 7.7T disk space.But still can not write to new file.
> You have probably run out of 32-bit inode space on your 27T filesystem.
>
>> software ambience:
>>
>> [root@Production data5]# uname -a Linux Production 2.6.18-128.el5 #1
>> SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
>>
>> [root@Production data5]# rpm -qa | grep xfs
>> xfsprogs-2.9.4-1.el5.centos xorg-x11-xfs-1.0.2-4 kmod-xfs-0.4-2
>>
> that's X11, not the filesystem, for what it's worth :)
>
>> problem:
>>
>> [root@Production data5]# df -h Filesystem Size Used Avail
>> Use% Mounted on /dev/sda1 48G 6.7G 39G 15% /
>> /dev/sda2 81G 4.0G 73G 6% /opt /dev/sdb1
>> 22T 15T 7.7T 65% /data2 tmpfs 2.0G 0 2.0G
>> 0% /dev/shm
>>
>> [root@Production data5]# df -i Filesystem Inodes IUsed
>> IFree IUse% Mounted on /dev/sda1 12812288 136847 12675441
>> 2% / /dev/sda2 21867648 8440 21859208 1% /opt
>> /dev/sdb1 23429382016 4625792 23424756224 1% /data2
>> tmpfs 504701 1 504700 1% /dev/shm
>>
>> [root@Production data5]# touch test.log touch: cannot touch
>> `test.log': No space left on device
> If your applications can handle> 32-bit inode numbers, mount -o inode64
> and see if you can create the new file.
>
> hm, we should maybe printk in this case, it comes up often enough.
>
> -Eric
>>
>> _______________________________________________ xfs mailing list
>> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-03-27 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 13:41 No space left on device on xfs filesystem with 7.7TB free atyu30 atyu30
2011-03-26 15:08 ` Christoph Hellwig
2011-03-26 15:34 ` Eric Sandeen
2011-03-27 13:25 ` Timothy Sesow [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=4D8F3AB8.4050803@timsesow.com \
--to=tsesow@gmail.com \
--cc=tim@timsesow.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.