Ocfs2 users - Aug 2009 - no space left on device - another one

Hi,

I'm getting the no space left on device error. I'm running an EMC CX-500
with a very large file system... but only 2% consumed. Occurs on one 
system of a ~16 system cluster.
Where may I send the output of stat_sysdir.sh? Any other helpful 
information I could provide here? I used the defaults from the 
ocfs2console when the file system was made.
    uname -a: Linux 2.6.18-128.1.10.el5
    rpm -qa | grep ocfs2: ocfs2-2.6.18-128.1.10.el5-1.4.1-1.el5

The error occurs as I'm untarring a large archive. After removing the 
files from the archive I need to reboot to be able to write to the 
device again.

Please advise what other information you suggest I collect to help here 
or a course of action.
Best, James

Hi James,

James Harrell wrote:
> Hi,
> 
> I'm getting the no space left on device error. I'm running an EMC
CX-500
> with a very large file system... but only 2% consumed. Occurs on one 
> system of a ~16 system cluster.
	You may meet with the issue of "Orphan files not getting deleted". 
Please look at this link for details.
http://oss.oracle.com/pipermail/ocfs2-users/2009-August/003783.html
> Where may I send the output of stat_sysdir.sh? Any other helpful 
> information I could provide here? I used the defaults from the 
> ocfs2console when the file system was made.
yeah, stat_sysdir.sh is helpful especially it includes the information 
of orphan dir so that we can make sure that bug is the root cause in 
your case.
>     uname -a: Linux 2.6.18-128.1.10.el5
>     rpm -qa | grep ocfs2: ocfs2-2.6.18-128.1.10.el5-1.4.1-1.el5
> 
> The error occurs as I'm untarring a large archive. After removing the 
> files from the archive I need to reboot to be able to write to the 
> device again.
> 
> Please advise what other information you suggest I collect to help here 
> or a course of action.
> Best, James
Regards,
Tao