OpenVZ Forum


Home » General » Support » Enough space, but reports 'no space left on device'
Enough space, but reports 'no space left on device' [message #35875] Wed, 29 April 2009 05:22 Go to next message
zenny
Messages: 48
Registered: November 2006
Member
I thought that this is a CentOS 4.7 issue and posted at ( http://www.centos.org/modules/newbb/viewtopic.php?topic_id=1 9958&forum=27). But CentOS states that it is a OVZ vzquota issue.

I am completely blocked to execute with the error message recurring each time without completely. I also restarted the vz service, but in vain.

I could not even run yum or use wget to get the default CentOS kernel to test whether it is associated with OVZ or CentOS! Sad

Any pointer?

Report message to a moderator

Re: Enough space, but reports 'no space left on device' [message #35878 is a reply to message #35875] Wed, 29 April 2009 05:31 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
what does df -i tells you?

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: Enough space, but reports 'no space left on device' [message #35889 is a reply to message #35878] Wed, 29 April 2009 10:50 Go to previous messageGo to next message
zenny
Messages: 48
Registered: November 2006
Member
Kir:

# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hda1 656000 656000 0 100% /
none 23463 1 23462 1% /dev/shm
/dev/hda3 8863744 207565 8656179 3% /vz

But I have nothing running except a shorewall firewall at the HN.


# ps -aux
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.3/FAQ
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.3  1832  572 ?        S    Mar29   0:01 init [3]                  
root         2  0.0  0.0     0    0 ?        S    Mar29   0:00 [migration/0/0]
root         3  0.0  0.0     0    0 ?        SN   Mar29   0:00 [ksoftirqd/0]
root         4  0.0  0.0     0    0 ?        S<   Mar29   0:00 [events/0]
root         5  0.0  0.0     0    0 ?        S<   Mar29   0:00 [khelper]
root        17  0.0  0.0     0    0 ?        S<   Mar29   0:00 [kblockd/0]
root        30  0.0  0.0     0    0 ?        S    Mar29   0:00 [khubd]
root        66  0.0  0.0     0    0 ?        S    Mar29   0:00 [pdflush]
root        67  0.0  0.0     0    0 ?        S    Mar29   0:00 [pdflush]
root        69  0.0  0.0     0    0 ?        S<   Mar29   0:00 [aio/0]
root       656  0.0  0.0     0    0 ?        S    Mar29   0:00 [kseriod]
root        65  0.0  0.0     0    0 ?        S    Mar29   0:00 [ubstatd]
root        68  0.0  0.0     0    0 ?        S    Mar29   0:00 [kswapd0]
root       761  0.0  0.0     0    0 ?        S<   Mar29   0:00 [ata/0]
root       792  0.0  0.0     0    0 ?        S<   Mar29   0:00 [kcryptd/0]
root       793  0.0  0.0     0    0 ?        S<   Mar29   0:00 [kmpathd/0]
root       794  0.0  0.0     0    0 ?        S<   Mar29   0:00 [kmirrord]
root       799  0.0  0.0     0    0 ?        S    Mar29   1:00 [kjournald]
root      4718  0.0  0.2  2620  460 ?        S<s  Mar29   0:00 udevd
root      6148  0.0  0.0     0    0 ?        S    Mar29   0:00 [kjournald]
root      8850  0.0  0.3  2028  584 ?        Ss   Mar29   0:07 syslogd -m 0
root      8855  0.0  0.1  2216  372 ?        Ss   Mar29   0:05 klogd -x
root      8892  0.0  0.2  2144  388 ?        S    Mar29   0:00 /usr/sbin/smartd
root      8904  0.0  0.5  5100 1048 ?        Ss   Mar29   0:04 /usr/sbin/sshd
root      8919  0.0  0.3  3332  748 ?        Ss   Mar29   0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
root      8928  0.0  0.4  5768  916 ?        Ss   Mar29   0:00 crond
root      8945  0.0  0.2  2532  424 ?        Ss   Mar29   0:00 /usr/sbin/atd
dbus     10360  0.0  0.4  3972  796 ?        Ss   Mar29   0:00 dbus-daemon-1 --system
root     14957  0.0  0.0  2576  116 ?        Ss   Mar29   0:02 /usr/sbin/kmsgsd
root     14959  0.0  0.0  2824  184 ?        Ss   Mar29   0:05 /usr/sbin/psadwatchd
root     14966  0.0  2.6  8600 5048 ?        Ss   Mar29   0:00 /usr/bin/perl /usr/libexec/webmin/miniserv.pl /etc/webmin/miniserv.conf
root     14970  0.0  0.6  4108 1280 ?        Ss   Mar29   0:00 login -- root     
root     14972  0.0  0.2  3504  408 tty3     Ss+  Mar29   0:00 /sbin/mingetty tty3
root     14973  0.0  0.2  1928  408 tty4     Ss+  Mar29   0:00 /sbin/mingetty tty4
root     14974  0.0  0.2  2152  408 tty5     Ss+  Mar29   0:00 /sbin/mingetty tty5
root     14975  0.0  0.2  2256  408 tty6     Ss+  Mar29   0:00 /sbin/mingetty tty6
root     15309  0.0  0.7  6012 1416 tty1     Ss   Mar29   0:00 -bash
root     15349  0.0  1.0  4912 2004 tty1     S+   Mar29   0:04 ssh root@192.168.1.250
root     21056  0.0  0.2  3096  408 tty2     Ss+  Mar30   0:00 /sbin/mingetty tty2
root      6570  0.0  5.4 14432 10176 ?       Ss   Apr27   0:07 /usr/bin/perl -w /usr/sbin/psad
root     13249  0.0  0.0     0    0 ?        S    08:28   0:00 [vzmond]
root     14620  0.0  1.1  7416 2240 ?        Ss   14:11   0:00 sshd: service [priv]
service  14624  0.0  0.7  7416 1496 ?        S    14:11   0:00 sshd: service@pts/0
service  14625  0.0  0.7  5444 1360 pts/0    Ss   14:11   0:00 -bash
root     14653  0.0  0.6  6420 1236 pts/0    S    14:12   0:00 su -
root     14654  0.0  0.7  4964 1416 pts/0    S    14:12   0:00 -bash
root     14688  0.0  0.4  2956  752 pts/0    R+   14:14   0:00 ps -aux

Report message to a moderator

Re: Enough space, but reports 'no space left on device' [message #35890 is a reply to message #35889] Wed, 29 April 2009 11:58 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
df -i tells you that there are no more free i-nodes left. And it doesn't matter what processes you have running.

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: Enough space, but reports 'no space left on device' [message #36037 is a reply to message #35890] Wed, 13 May 2009 14:44 Go to previous messageGo to next message
seanfulton is currently offline  seanfulton
Messages: 105
Registered: May 2007
Senior Member
Use vzquota to increase your inodes.

This is a frequent problem for me. When the VE is created with diskspace of X, the inodes are calculated based on X. Over time, we increase the size of the "drive" that the VE uses, and eventually, it surpasses the number of allocated inodes.

Just increase them, and remember to increase them in your ve.conf file (for some reason vzquota does not do this).

sean

Report message to a moderator

Re: Enough space, but reports 'no space left on device' [message #36041 is a reply to message #36037] Wed, 13 May 2009 18:53 Go to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
seanfulton wrote on Wed, 13 May 2009 18:44

Use vzquota to increase your inodes.

<...>
Just increase them, and remember to increase them in your ve.conf file (for some reason vzquota does not do this).



vzquota is not supposed to be used directly (well, at least in this case). Just run 
vzctl set NNN --diskinodes xxx:yyy --save

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Previous Topic: Enabling TUN/TAP for VPN on containers following guide but no result
Next Topic: port forwarding (http servers on each VPS)
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Nov 17 02:18:42 GMT 2024

Total time taken to generate the page: 0.04913 seconds
Powered by FUDforum Powered by Virtuozzo Containers