xfs
[Top] [All Lists]

Re: False No space left on device error

To: Michael Ramsey <Michael.Ramsey@xxxxxxxxxx>
Subject: Re: False No space left on device error
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Wed, 01 Jun 2005 18:39:06 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <BE5986C67D271E4EA72B61F406AB91F29C7C79@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <BE5986C67D271E4EA72B61F406AB91F29C7C79@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)
My best guess is that this is the inode32 allocator running out of < 2T blocks to allocate inodes... I'd have to think about how to prove this theory.

-Eric

Michael Ramsey wrote:
logfs2.nyc#uname -a
Linux logfs2.nyc 2.6.11-1.27_FC3smp #1 SMP Tue May 17
20:38:05 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux

logfs2.nyc#df -h
/dev/mapper/raidvol-vol1 9.0T  7.1T  2.0T  79% /u01

logfs2.nyc#rpm -qa |grep xfs
xfsprogs-2.6.13-2

logfs2.nyc#df -i
/dev/mapper/raidvol-vol1  8236943008 3834112 8233108896
1% /u01

logfs2.nyc#cd /u01
logfs2.nyc#rm a
rm: remove regular empty file `a'? y
logfs2.nyc#touch a
logfs2.nyc#touch b
touch: cannot touch `b': No space left on device
logfs2.nyc#rm a
rm: remove regular empty file `a'? y
logfs2.nyc#touch b
logfs2.nyc#touch a
touch: cannot touch `a': No space left on device

Logfs2.nyc#mount
/dev/mapper/raidvol-vol1 on /u01 type xfs (rw)


Michael Ramsey




[[HTML alternate version deleted]]



<Prev in Thread] Current Thread [Next in Thread>