Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 27/01/2015, à 14:02

neovea

Probleme d'espace disque sur /dev/root

Bonjour à toutes et tous,

J'administre un vps cloud de chez OVH avec un espace disque de 50gb. Les applications qui tournent dessus sont assez triviales : liferay + tomcat + bdd. Le tout occupe environ 10gb.

`df -h`, renvoit :

   

 Filesystem      Size  Used Avail Use% Mounted on
    /dev/root        48G   45G  570M  99% /
    devtmpfs        2.0G  4.0K  2.0G   1% /dev
    none            4.0K     0  4.0K   0% /sys/fs/cgroup
    none            395M  524K  395M   1% /run
    none            5.0M     0  5.0M   0% /run/lock
    none            2.0G     0  2.0G   0% /run/shm
    none            100M     0  100M   0% /run/user

`df -i` renvoit :

   

Filesystem      Inodes IUsed   IFree IUse% Mounted on
    /dev/root      3141600 78065 3063535    3% /
    devtmpfs        505084  1438  503646    1% /dev
    none            505206     2  505204    1% /sys/fs/cgroup
    none            505206   891  504315    1% /run
    none            505206     2  505204    1% /run/lock
    none            505206     1  505205    1% /run/shm
    none            505206     2  505204    1% /run/user

Mais `du -sh / | sort -nr | head`, renvoit :

   

du: cannot access â/sys/kernel/slab/L2TP/IPv6â: No such file or directory
    du: cannot access â/sys/kernel/slab/L2TP/IPâ: No such file or directory
    du: cannot access â/proc/391/task/391/fd/4â: No such file or directory
    du: cannot access â/proc/391/task/391/fdinfo/4â: No such file or directory
    du: cannot access â/proc/391/fd/4â: No such file or directory
    du: cannot access â/proc/391/fdinfo/4â: No such file or directory
    du: cannot access â/proc/402â: No such file or directory
    du: cannot access â/proc/32350â: No such file or directory
    du: cannot access â/proc/32354â: No such file or directory
    du: cannot access â/proc/32356â: No such file or directory
    du: cannot access â/proc/32360â: No such file or directory
    du: cannot access â/proc/32363â: No such file or directory
    du: cannot access â/proc/32368â: No such file or directory
    8.9G    /

Je sais que du et df renvoient des informations différentes car df renvoit le filesystem disk usage alors que du renvoit l'espace occupé par les fichiers sur le disque.
Le dossier de logs pese ~167M, donc j'écarte cette source du problème.

`cat /proc/mounts` renvoit :

   

rootfs / rootfs rw 0 0
    /dev/root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
    devtmpfs /dev devtmpfs rw,relatime,size=2020336k,nr_inodes=505084,mode=755 0 0
    sysfs /sys sysfs rw,relatime 0 0
    none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
    none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
    none /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
    none /sys/fs/cgroup tmpfs rw,relatime,size=4k,mode=755 0 0
    none /sys/fs/fuse/connections fusectl rw,relatime 0 0
    none /sys/kernel/security securityfs rw,relatime 0 0
    none /run tmpfs rw,nosuid,noexec,relatime,size=404168k,mode=755 0 0
    none /sys/fs/pstore pstore rw,relatime 0 0
    none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
    none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
    none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0
    systemd /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,name=systemd 0 0

autoclean et autoremove n'y changent rien.

Par contre j'ai un cron de backup de mes appli web et mysql qui envoit tout sur dropbox. Mais les dump pèsent au max 1.7gb.

Merci pour votre aide.

Dernière modification par neovea (Le 28/01/2015, à 09:51)

Hors ligne

#2 Le 27/01/2015, à 20:44

tiramiseb

Re : Probleme d'espace disque sur /dev/root

Salut,

Que donne la commande suivante ?

du -shc /*

PS : mets les retours de commandes entre balises "code", obtenues en cliquant sur l'icônebt_pre.png.
1369359175.gif

Hors ligne

#3 Le 28/01/2015, à 09:53

neovea

Re : Probleme d'espace disque sur /dev/root

Ok désolé pour les code blocks, trop l'habitude du markdown...
Voici ce que renvoit la commande donnée :

9.6M    /bin
21M     /boot
4.0K    /dev
7.6M    /etc
6.1G    /home
29M     /lib
4.0K    /lib64
16K     /lost+found
8.0K    /media
4.0K    /mnt
233M    /opt
du: cannot access â/proc/28058â: No such file or directory
du: cannot access â/proc/28063â: No such file or directory
du: cannot access â/proc/28066â: No such file or directory
du: cannot access â/proc/28070â: No such file or directory
du: cannot access â/proc/28071â: No such file or directory
du: cannot access â/proc/28075â: No such file or directory
du: cannot access â/proc/28077â: No such file or directory
du: cannot access â/proc/28080â: No such file or directory
du: cannot access â/proc/28084â: No such file or directory
du: cannot access â/proc/28087â: No such file or directory
du: cannot access â/proc/28090â: No such file or directory
du: cannot access â/proc/28096â: No such file or directory
du: cannot access â/proc/28099/task/28099/fdâ: No such file or directory
du: cannot access â/proc/28099/task/28099/fdinfoâ: No such file or directory
du: cannot access â/proc/28099/task/28099/nsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/environâ: No such file or directory
du: cannot access â/proc/28099/task/28099/auxvâ: No such file or directory
du: cannot access â/proc/28099/task/28099/statusâ: No such file or directory
du: cannot access â/proc/28099/task/28099/personalityâ: No such file or directory
du: cannot access â/proc/28099/task/28099/limitsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/commâ: No such file or directory
du: cannot access â/proc/28099/task/28099/syscallâ: No such file or directory
du: cannot access â/proc/28099/task/28099/cmdlineâ: No such file or directory
du: cannot access â/proc/28099/task/28099/statâ: No such file or directory
du: cannot access â/proc/28099/task/28099/statmâ: No such file or directory
du: cannot access â/proc/28099/task/28099/mapsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/numa_mapsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/memâ: No such file or directory
du: cannot access â/proc/28099/task/28099/cwdâ: No such file or directory
du: cannot access â/proc/28099/task/28099/rootâ: No such file or directory
du: cannot access â/proc/28099/task/28099/exeâ: No such file or directory
du: cannot access â/proc/28099/task/28099/mountsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/mountinfoâ: No such file or directory
du: cannot access â/proc/28099/task/28099/clear_refsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/smapsâ: No such file or directory
du: cannot access â/proc/28099/task/28099/pagemapâ: No such file or directory
du: cannot access â/proc/28099/task/28099/wchanâ: No such file or directory
du: cannot access â/proc/28099/task/28099/cpusetâ: No such file or directory
du: cannot access â/proc/28099/task/28099/cgroupâ: No such file or directory
du: cannot access â/proc/28099/task/28099/oom_scoreâ: No such file or directory
du: cannot access â/proc/28099/task/28099/oom_adjâ: No such file or directory
du: cannot access â/proc/28099/task/28099/oom_score_adjâ: No such file or directory
du: cannot access â/proc/28099/task/28099/ioâ: No such file or directory
du: cannot access â/proc/28099/fdâ: No such process
du: cannot access â/proc/28099/fdinfoâ: No such process
du: cannot access â/proc/28099/nsâ: No such process
du: cannot access â/proc/28099/netâ: No such process
du: cannot access â/proc/28099/environâ: No such process
du: cannot access â/proc/28099/auxvâ: No such process
du: cannot access â/proc/28099/statusâ: No such process
du: cannot access â/proc/28099/personalityâ: No such process
du: cannot access â/proc/28099/limitsâ: No such process
du: cannot access â/proc/28099/commâ: No such process
du: cannot access â/proc/28099/syscallâ: No such process
du: cannot access â/proc/28099/cmdlineâ: No such process
du: cannot access â/proc/28099/statâ: No such process
du: cannot access â/proc/28099/statmâ: No such process
du: cannot access â/proc/28099/mapsâ: No such process
du: cannot access â/proc/28099/numa_mapsâ: No such process
du: cannot access â/proc/28099/memâ: No such process
du: cannot access â/proc/28099/cwdâ: No such process
du: cannot access â/proc/28099/rootâ: No such process
du: cannot access â/proc/28099/exeâ: No such process
du: cannot access â/proc/28099/mountsâ: No such process
du: cannot access â/proc/28099/mountinfoâ: No such process
du: cannot access â/proc/28099/mountstatsâ: No such process
du: cannot access â/proc/28099/clear_refsâ: No such process
du: cannot access â/proc/28099/smapsâ: No such process
du: cannot access â/proc/28099/pagemapâ: No such process
du: cannot access â/proc/28099/wchanâ: No such process
du: cannot access â/proc/28099/cpusetâ: No such process
du: cannot access â/proc/28099/cgroupâ: No such process
du: cannot access â/proc/28099/oom_scoreâ: No such process
du: cannot access â/proc/28099/oom_adjâ: No such process
du: cannot access â/proc/28099/oom_score_adjâ: No such process
du: cannot access â/proc/28099/coredump_filterâ: No such process
du: cannot access â/proc/28099/ioâ: No such process
du: cannot access â/proc/28633/task/28633/fd/4â: No such file or directory
du: cannot access â/proc/28633/task/28633/fdinfo/4â: No such file or directory
du: cannot access â/proc/28633/fd/4â: No such file or directory
du: cannot access â/proc/28633/fdinfo/4â: No such file or directory
du: cannot access â/proc/28635â: No such file or directory
0       /proc
212K    /root
516K    /run
24M     /sbin
4.0K    /srv
du: cannot access â/sys/kernel/slab/L2TP/IPv6â: No such file or directory
du: cannot access â/sys/kernel/slab/L2TP/IPâ: No such file or directory
0       /sys
44K     /tmp
1002M   /usr
876M    /var
8.3G    total

Hors ligne

#4 Le 28/01/2015, à 21:19

tiramiseb

Re : Probleme d'espace disque sur /dev/root

Ok, les fichiers "visibles" prennent donc moins que l'espace réellement utilisé.

Je vois deux possibilités qui peuvent expliquer ça :
- soit tu as un programme qui écrit dans un fichier qui a été supprimé : l'espace disque est utilisé mais le fichier n'est plus visible dans l'arborescence. Dans ce cas, un simple redémarrage résoudrait ce problème à coup sûr ;
- soit tu as quelque chose de monté par-dessus un répertoire dans lequel il y a des fichiers : ces fichiers ne sont plus alors visibles par un "du" - cela étant dit, dans la mesure où tu n'as qu'une seule partition, c'est moins probable... sauf si tu as quelque chose caché derrière /dev, /sys, /proc, /run ou un autre, mais ça m'étonnerait beaucoup.

Hors ligne

#5 Le 02/02/2015, à 10:07

neovea

Re : Probleme d'espace disque sur /dev/root

Bonjour,
Pour répondre au problème, voici ce qui se passait : j'utilisais un script qui lançait les backups de mes applications et les synchronisait sur dropbox. Sauf que pour une raison indéterminée, le script s'exécutait de multiples fois au lieu d'une seule. Du coup ça mangeait tout l'espace disque. Merci pour l'aide, j'ai au moins appris quelque chose smile

Hors ligne