<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><div>>Em Tue, 6 Dec 2011 17:58:15 +0800<br>>"Ramappa, Ravi (NSN - IN/Bangalore)" <ravi.ramappa at nsn.com> escreveu:<br>><br>>> Hi ,<br>>><br>>> I am getting the error "No space left on device" on a device with free<br>>> space which is ocfs2 filesystem.<br>>> Additional information is as below,<br>>><br>>> [root at sai93 staging]# debugfs.ocfs2 -n -R "stats" /dev/sdb1 | grep -i<br>>> "Cluster Size"<br>>> Block Size Bits: 12 Cluster Size Bits: 15<br>>><br>>> [root at sai93 ~]# cat /etc/redhat-release<br>>> Red Hat Enterprise Linux Server release 5.3 (Tikanga)<br>>><br>>> [root at sai93 ~]# uname -r<br>>> 2.6.18-128.el5<br>>><br>>> [root at sai93 ~]# rpm -qa| grep
ocfs<br>>> ocfs2console-1.4.4-1.el5<br>>> ocfs2-2.6.18-128.el5-1.4.7-1.el5<br>>> ocfs2-tools-1.4.4-1.el5<br>>><br>>> [root at sai93 ~]# cat /etc/ocfs2/cluster.conf<br>>> node:<br>>> ip_port = 7777<br>>> ip_address = 10.71.10.93<br>>> number = 0<br>>> name = sai93<br>>> cluster = ocfs2<br>>> node:<br>>> ip_port = 7777<br>>> ip_address = 10.71.10.94<br>>> number = 1<br>>> name = sai94<br>>> cluster = ocfs2<br>>> cluster:<br>>> node_count =2<br>>> name = ocfs2<br>>><br>>> [root at sai93
~]#<br>>><br>>> The only way I overcome this error is by unmounting the ocfs2<br>>> filesystem, doing a fsck followed by server reboot.<br>>><br>>> 988 fsck.ocfs2 /dev/sdb1<br>>> 989 mount -a<br>>> 990 df -h<br>>> 991 touch /mnt/staging/test<br>>> 992 man fsck.ocfs2<br>>> 993 umount /mnt<br>>> 994 service ocfs2 stop<br>>> 995 dmesg<br>>> 996 reboot<br>>><br>>> After restarting the servers I have executed the stat_sysdir.sh<br>>> script, the output of which is attached herwith. Kindly confirm<br>>> whether I need to do any changes to ocfs2 configuration , to avoid<br>>> the above error.<br>>><br>>> <<output.zip>><br>>><br>>> Thanks & Regards,<br>>><br>>> Ravi
Ramappa<br>><br>>Hello,<br>><br>>This is a known issue and was fixed in ocfs2 1.6 series by enabling the<br>>discontig-bg feature.<br>><br>>If you are not using DRDB you can upgrade your kernel and ocfs2-tools<br>>using the ULEK 5.5 series, provided by oracle at<br>><a href="http://public-yum.oracle.com/" target="_blank">http://public-yum.oracle.com/</a> .<br>><br>>Regards,<br>>Sérgio<br><br>We are also having a similar issue, but we are using DRBD. We are set at the minimum 2 node slots, so I can't reduce those any more.<br><br>Is there any other good way to fix this problem, at least for a while? What about ways to preemptively clear some fragmentation before we get the dreaded error?<br><br>I think moving files off the filesystem and back works somewhat, but how can I tell which files to move would have the most effect?<br><br>Thanks,<br>Herman<br><br></div></div></body></html>