URL: https://linuxfr.org/forums/linux-debian-ubuntu/posts/probleme-espace-disque-et-systeme-de-fichier-nilfs Title: Probleme espace disque et systeme de fichier nilfs Authors: djraffon Date: 2011年06月10日T17:11:24+02:00 Tags: selinux Score: -2 J'ai ma partition racine qui est formatée en nilfs2 et je n'arrive pas à paramétrer le daemon nilfs_cleanerd pour qu'il fasse le menage de maniere transparente. Sur le systeme de fichier, l'espace disque utilisé n'arrete pas d'augmenter alors que je n'installe rien sur le disque. D'autre part je n'arrive pas a localiser ou cette espace est utiliser car j'ai une difference de 3,5 Go entre les commandes df et du. Voici ce que me renvoi la commande df: ```bash # df -h Filesystem Size Used Avail Use% Mounted on /dev/mmcblk3p6 13G 6.2G 6.2G 50% / none 187M 724K 187M 1% /dev none 187M 600K 187M 1% /dev/shm none 187M 84K 187M 1% /var/run none 187M 0 187M 0% /var/lock /dev/mmcblk3p2 388M 8.1M 380M 3% /media/df-9879-0800200c /dev/mmcblk3p1 283M 242M 41M 86% /media/system /dev/mmcblk3p3 2.0M 2.0M 0 100% /media/df-9879-0800200c_ ``` Voici ce que me renvoi la commande du: ```bash # du -am --max-depth=1 / |sort -n du: cannot access `/L4T/proc/16526/task/16526/fd/4': No such file or directory du: cannot access `/L4T/proc/16526/task/16526/fdinfo/4': No such file or directory du: cannot access `/L4T/proc/16526/fd/4': No such file or directory du: cannot access `/L4T/proc/16526/fdinfo/4': No such file or directory du: cannot access `/L4T/proc/16533': No such file or directory du: cannot access `/proc/16526/task/16526/fd/4': No such file or directory du: cannot access `/proc/16526/task/16526/fdinfo/4': No such file or directory du: cannot access `/proc/16526/fd/4': No such file or directory du: cannot access `/proc/16526/fdinfo/4': No such file or directory du: cannot access `/home/slon/.gvfs': Permission denied 0 /.nilfs 0 /proc 0 /sys 1 /data 1 /lost+found 1 /mnt 1 /opt 1 /root 1 /selinux 1 /srv 1 /system 1 /tmp 2 /dev 6 /bin 10 /sbin 18 /etc 34 /boot 34 /home 242 /media 257 /var 337 /L4T 366 /lib 1405 /usr 2707 / ``` J'arrive pourtant a utiliser l'outil nilfs pour supprimer les "check point", par exemple: ```bash rmcp -f /dev/mmcblkp6 ..14250 ``` ci joint, la liste des snapshot & check point via lscp: ```bash # lscp CNO DATE TIME MODE FLG NBLKINC ICNT 13034 2011年06月09日 18:43:49 ss - 24 119699 14251 2011年06月10日 16:30:10 cp - 26 119803 14252 2011年06月10日 16:30:10 cp - 23 119803 14253 2011年06月10日 16:30:15 cp - 27 119802 14254 2011年06月10日 16:30:24 cp - 31 119802 14255 2011年06月10日 16:30:52 cp - 17 119802 14256 2011年06月10日 16:31:05 cp - 17 119802 14257 2011年06月10日 16:31:19 cp - 26 119802 ``` D'autre part, voici mon fichier de configuration /etc/nilfs_cleanerd.conf ```bash # cat /etc/nilfs_cleanerd.conf # nilfs_cleanerd.conf - configuration file of NILFS cleaner daemon. # # This file contains GC parameters that are loaded when cleaner gets # started. You can force them to be reloaded by sending a HUP signal # to the cleaner process. # # Each parameter is declared with a keyword-value pair or a directive # with no argument. Lines beginning with "#" are ignored. For # details, see the man page of nilfs_cleanerd.conf(5). # Protection period in second. protection_period 1 # Minimum number of clean segments # 0 = continuous cleaning #> 0 = pause cleaning until less segments are available min_clean_segments 5% # Maximum number of clean segments max_clean_segments 90% # The argument of min_clean_segments and max_clean_segments can be # followed by a percent sign (%) or one of the following # multiplicative suffixes: K 1024, MB 1000*1000, M 1024*1024, GB # 1000*1000*1000, G 1024*1024*1024, and so on for T, P, E. # # If the argument is followed by "%", it represents a disk capacity # ratio. # Clean segment check interval in seconds clean_check_interval 10 # Segment selection policy. # In NILFS version 2.0.0, only the timestamp policy is supported. selection_policy timestamp # timestamp in ascend order # The maximum number of segments to be cleaned at a time. nsegments_per_clean 5 # The maximum number of segments to be cleaned at a time # if clean segments < min_clean_segments mc_nsegments_per_clean 10 # Cleaning interval in seconds. cleaning_interval 5 # Cleaning interval in seconds # if clean segments < min_clean_segments mc_cleaning_interval 1 # Retry interval in seconds. retry_interval 60 # Use mmap when reading segments if supported. use_mmap # Log priority. # Supported priorities are emerg, alert, crit, err, warning, notice, info, and # debug. log_priority info ``` Si quelqu'un peut m'aider...

AltStyle によって変換されたページ (->オリジナル) /