Bonjour,
J’ai deux partitions : root et home sur mon disque dur. Sur root j’avais dimensionné 10 Go. Mais en utilisant backup-manager j’obtenais des messages d’erreur indiquant "plus de place sur le périphérique". Or sur mon disque dur externe il restait beaucoup de place libre, j’ai compris que c’était un problème avec les fichiers temporaires…
J’ai donc cherché les fichiers qui occupaient le plus de place sur root mais je n’ai rien vraiment trouvé concernant l’activité de backup-manager. J’ai tout de meme effacé les fichiers temporaires dans /tmp, c’est le dossier utilisé aussi par backup-manager. J’ai aussi effacé de nombreux packages.
Mais ce n’était pas suffisant. Alors comme j’utilise lvm j’ai redimensionné ma partition root avec 20 Go. Je relance backup-manager et me voilà à nouveau avec une partition root saturée, 20 Go occupé sans plus aucune place libre !!!
la commande du ci-dessous n’indique un résultat global que sur 5 Go. Pourtant ma partition root / utilise 20 Go. Je ne comprends pas cet affichage. Avec baobab c’est aussi compliqué. Baobab indique une partition root dans les préférences /dev/mapper/gelinux-root de 20 Go, puis dans le résultat je ne vois que des dossiers sous / avec un total pour / d’environ 5 Go… Où sont passés les 15 Go restants de / ?
Ci dessous mon fichier de configuratin pour backup-manager. Il est lancé par la commande :
sudo backup-manager -v -c /etc/backup-manager-full.conf
[code]# Backup Manager Configuration File
* This configuration file is divided into sections.
The ‘global’ section is mandatory, every keys defined in
this section are inherited in the other sections.
* There is one section per “backup method”, you have to
fill the section of the chosen method.
##############################################################
##############################################################
Repository - everything about where archives are
#############################################################
Where to store the archives
export BM_REPOSITORY_ROOT="/media/gelinp/DDEXTERNE/BACKUP-MANAGER"
Where to place temporary files
export BM_TEMP_DIR="/tmp"
For security reasons, the archive repository and the generated
archives will be readable/writable by a given user/group.
This is recommended to set this to true.
export BM_REPOSITORY_SECURE=“true”
The repository will be readable/writable only by a specific
user:group pair if BM_REPOSITORY_SECURE is set to true.
export BM_REPOSITORY_USER="gelinp"
export BM_REPOSITORY_GROUP=“root”
You can also choose the permission to set the repository, default
is 770, pay attention to what you do there!
export BM_REPOSITORY_CHMOD=“770”
##############################################################
Archives - let’s focus on the precious tarballs…
##############################################################
Each archive generated will be chmoded for security reasons
(BM_REPOSITORY_SECURE should be enabled for this).
export BM_ARCHIVE_CHMOD=“660”
Number of days we have to keep an archive (Time To Live)
export BM_ARCHIVE_TTL=“5”
Do you want to purge only the top-level directory or all
directories under BM_REPOSITORY_ROOT?
export BM_REPOSITORY_RECURSIVEPURGE=“false”
Do you want to replace duplicates by symlinks?
(archive-DAY is a duplicate of archive-(DAY - 1) if they
are both the same according to MD5 hashes).
export BM_ARCHIVE_PURGEDUPS=“true”
Prefix of every archive on that box (default is HOSTNAME)
export BM_ARCHIVE_PREFIX="$HOSTNAME"
Should we purge only archives built with $BM_ARCHIVE_PREFIX
export BM_ARCHIVE_STRICTPURGE=“true”
You may want to nice the commands run for archive-creation
(Recommanded for desktop users.)
Choose a nice level from -20 (most favorable scheduling) to 19 (least favorable).
export BM_ARCHIVE_NICE_LEVEL=“10”
The backup method to use.
Available methods are:
- tarball
- tarball-incremental
- mysql
- pgsql
- svn
- pipe
- none
If you don’t want to use any backup method (you don’t want to
build archives) then choose “none”
export BM_ARCHIVE_METHOD=“tarball mysql”
##############################################################
Encryption - because you cannot trust the place your
archives are
##############################################################
If you want to encrypt your archives locally, Backup Manager
can use GPG while building the archive (so the archive is never
written to the disk without being encrypted.
Note: this feature is only possible with the following archive types:
tar, tar.gz, tar.bz2
Uncomment the following line if you want to enable encryption
available method: gpg
export BM_ENCRYPTION_METHOD=“false”
The encryption will be made using a GPG ID
Examples:
export BM_ENCRYPTION_RECIPIENT=""
export BM_ENCRYPTION_RECIPIENT=""
export BM_ENCRYPTION_RECIPIENT=""
##############################################################
Section “TARBALL”
- Backup method: tarball
#############################################################
Archive filename format
long : host-full-path-to-folder.tar.gz
short : parentfolder.tar.gz
export BM_TARBALL_NAMEFORMAT=“long”
Type of archives
Available types are:
tar, tar.gz, tar.bz2, tar.lz, dar, zip.
Make sure to satisfy the appropriate dependencies
(bzip2, dar, lzma, …).
export BM_TARBALL_FILETYPE=“tar.gz”
You can choose to build archives remotely over SSH.
You will then need to fill the BM_UPLOAD_SSH variables
(BM_UPLOAD_SSH_HOSTS, BM_UPLOAD_SSH_USER, BM_UPLOAD_SSH_KEY).
If this boolean is set to true, archive will be saved locally (in
BM_REPOSITORY_ROOT but will be built by the remote host).
Thus, BM_TARBALL_DIRECTORIES will be used to backup remote directories.
Those archive will be prefixed with the remote host name.
export BM_TARBALL_OVER_SSH=“false”
Do you want to dereference the files pointed by symlinks ?
enter true or false (true can lead to huge archives, be careful).
export BM_TARBALL_DUMPSYMLINKS=“false”
Targets to backup
You can use two different variables for defining the targets of
your backups, either a simple space-separated list (BM_TARBALL_DIRECTORIES)
or an array (BM_TARBALL_TARGETS[]).
Use the first one for simple path that doesn’t contain spaces in their name.
Use the former if you want to specify paths to backups with spaces.
It’s recommanded to use BM_TARBALL_TARGETS[] though.
Warning! You must not use both variables at the same time.
NOTE: The Debian package will only update BM_TARBALL_DIRECTORIES
Paths without spaces in their name:
export BM_TARBALL_DIRECTORIES="/etc /home /var/www"
If one or more of the targets contain a space, use the array:
declare -a BM_TARBALL_TARGETS
BM_TARBALL_TARGETS[0]="/etc"
BM_TARBALL_TARGETS[1]="/boot"
export BM_TARBALL_TARGETS
Files to exclude when generating tarballs, you can put absolute
or relative paths, Bash wildcards are possible.
export BM_TARBALL_BLACKLIST="/var/archives"
With the “dar” filetype, you can choose a maximum slice limit.
export BM_TARBALL_SLICESIZE=“1000M”
Extra options to append to the tarball generation
(take care to what you do; this will be silently added to the
command line.)
export BM_TARBALL_EXTRA_OPTIONS=""
##############################################################
The tarball-incremental method uses the same keys as the
tarball method, plus two others.
#############################################################
Which frequency to use for the master tarball?
possible values: weekly, monthly
export BM_TARBALLINC_MASTERDATETYPE=“weekly”
Number of the day, in the BM_TARBALLINC_MASTERDATETYPE frequency
when master tarballs should be made
export BM_TARBALLINC_MASTERDATEVALUE=“1”
Examples: you want to make master tarballs every friday:
BM_TARBALLINC_MASTERDATETYPE=“weekly”
BM_TARBALLINC_MASTERDATEVALUE=“5”
Or every first day of the month:
BM_TARBALLINC_MASTERDATETYPE=“monthly”
BM_TARBALLINC_MASTERDATEVALUE=“1”
##############################################################
Backup method: MYSQL
#############################################################
This method is dedicated to MySQL databases.
You should not use the tarball method for backing up database
directories or you may have corrupted archives.
Enter here the list of databases to backup.
Wildcard: ALL (will dump all the databases in one archive)
export BM_MYSQL_DATABASES=“ALL”
The best way to produce MySQL dump is done by using the “–opt” switch
of mysqldump. This make the dump directly usable with mysql (add the drop table
statements), lock the tables during the dump and other things.
This is recommended for full-clean-safe backups, but needs a
privileged user (for the lock permissions).
export BM_MYSQL_SAFEDUMPS=“true”
The user who is allowed to read every databases filled in BM_MYSQL_DATABASES
export BM_MYSQL_ADMINLOGIN=“root”
its password
export BM_MYSQL_ADMINPASS=“x68dde5r”
the host where the database is
export BM_MYSQL_HOST=“localhost”
the port where MySQL listen to on the host
export BM_MYSQL_PORT=“3306”
which compression format to use? (gzip or bzip2)
export BM_MYSQL_FILETYPE=“gzip”
Extra options to append to mysqldump
(take care to what you do; this will be silently added to the
command line.)
export BM_MYSQL_EXTRA_OPTIONS=""
##############################################################
Backup method: PostgreSQL
#############################################################
This method is dedicated to PostgreSQL databases.
You should not use the tarball method for backing up database
directories or you may have corrupted archives.
Enter here the list of databases to backup.
Wildcard: ALL (will dump all the databases in one archive)
export BM_PGSQL_DATABASES=“ALL”
The user who is allowed to read every databases filled in BM_PGSQL_DATABASES
export BM_PGSQL_ADMINLOGIN=“root”
its password
export BM_PGSQL_ADMINPASS=""
the host where the database is
export BM_PGSQL_HOST=“localhost”
the port where PostgreSQL listen to on the host
export BM_PGSQL_PORT=“5432”
which compression format to use? (gzip or bzip2)
export BM_PGSQL_FILETYPE=“bzip2”
Extra options to append to pg_dump
(take care to what you do; this will be silently added to the
command line.)
export BM_PGSQL_EXTRA_OPTIONS=""
##############################################################
Backup method: svn
#############################################################
Absolute paths to the svn repositories to archive
export BM_SVN_REPOSITORIES=""
You can compress the resulting XML files
Supported compressor are: bzip2 and gzip
export BM_SVN_COMPRESSWITH=“bzip2”
##############################################################
Backup method: pipe
#############################################################
The “pipe” method is a generic way of making archive.
Its concept is simple, for every kind of archive you want
to make, you give: a command which will send output on stdout,
a name, a file type and optionnaly, a compressor.
Be careful, this feature uses arrays!
declare -a BM_PIPE_COMMAND
declare -a BM_PIPE_NAME
declare -a BM_PIPE_FILETYPE
declare -a BM_PIPE_COMPRESS
You can virtually implement whatever backup scenario you like
with this method.
The resulting archives will be named like this:
$BM_ARCHIVE_PREFIX-$BM_PIPE_NAME.$DATE.$BM_PIPE_FILETYPE
If you specified a BM_PIPE_COMPRESS option, the resulting filename
will change as expected (eg, .gz if “gzip”).
Here are a couple of examples for using this method:
Archive a remote MySQL database through SSH:
BM_PIPE_COMMAND[0]=“ssh host -c “mysqldump -ufoo -pbar base””
BM_PIPE_NAME[0]=“base”
BM_PIPE_FILETYPE[0]=“sql”
BM_PIPE_COMPRESS[0]=“gzip”
This will make somthing like: localhost-base.20050421.sql.gz
Archive a specific directory, on a remote server through SSH:
BM_PIPE_COMMAND[0]=“ssh host -c “tar -c -z /home/user””
BM_PIPE_NAME[0]=“host.home.user”
BM_PIPE_FILETYPE[0]=“tar.gz”
BM_PIPE_COMPRESS[0]=""
This will make somthing like: localhost-host.home.user.20050421.tar.gz
export BM_PIPE_COMMAND
export BM_PIPE_NAME
export BM_PIPE_FILETYPE
export BM_PIPE_COMPRESS
##############################################################
Section “UPLOAD”
You can upload archives to remote hosts with different
methods.
#############################################################
Which method to use for uploading archives, you can put
multiple methods here.
Available methods:
- scp
- ssh-gpg
- ftp
- rsync
- s3
- none
If you don’t want to use any upload method (you don’t want to
upload files to remote hosts) then choose “none”
export BM_UPLOAD_METHOD=“none”
where to upload (global to all methods. Not required to be set for S3)
export BM_UPLOAD_HOSTS=""
Where to put archives on the remote hosts (global)
export BM_UPLOAD_DESTINATION="/var/archives/uploads"
Uncomment the ‘export …’ line below to activate the uploaded archives
database.
Using the database will avoid extraneous uploads to remote hosts in the
case of running more than one backup-manager jobs per day (such as when
you are using different configuration files for different parts of your
filesystem).
Note that when you upload to multiple hosts, a single succesfull upload
will mark the archive as uploaded. Thus upload errors to specific hosts
will have to be resolved manually.
You can specify any filename, but it is recommended to keep the database
inside the archive repository. The variable’s value has been preset to
that.
#export BM_UPLOADED_ARCHIVES=${BM_REPOSITORY_ROOT}/${BM_ARCHIVE_PREFIX}-uploaded.list
##############################################################
The SSH method
#############################################################
the user to use for the SSH connections/transfers
export BM_UPLOAD_SSH_USER=“bmngr”
The private key to use for opening the connection
export BM_UPLOAD_SSH_KEY=""
specific ssh hosts
export BM_UPLOAD_SSH_HOSTS=""
port to use for SSH connections (leave blank for default one)
export BM_UPLOAD_SSH_PORT=""
destination for ssh uploads (overrides BM_UPLOAD_DESTINATION)
export BM_UPLOAD_SSH_DESTINATION=""
purge archives on remote hosts before uploading?
export BM_UPLOAD_SSH_PURGE=“true”
If you set BM_UPLOAD_SSH_PURGE, you can specify a time to live
for archives uploaded with SSH.
This can let you use different ttl’s locally and remotely
By default, BM_ARCHIVE_TTL will be used.
export BM_UPLOAD_SSH_TTL=""
##############################################################
The SSH-GPG method
The ssh-gpg method uses the same configuration keys as the
ssh method, plus one other
#############################################################
The gpg public key used for encryption, this can be a short
or long key id, or a descriptive name. See gpg man page for
all possibilities how to specify a key.
export BM_UPLOAD_SSHGPG_RECIPIENT=""
##############################################################
The FTP method
#############################################################
Use FTP secured transfers (FTP over TLS)
User, password and data will be uploaded encrypted with SSL.
Passive mode will be automaticaly activated
export BM_UPLOAD_FTP_SECURE=“false”
Do you want to use FTP passive mode?
This is mandatory for NATed/firewalled environments
export BM_UPLOAD_FTP_PASSIVE=“true”
Test the FTP connection before starting archives upload.
This will enable BM to try sending a 2MB test file before
sending any archive
export BM_UPLOAD_FTP_TEST=“false”
the user to use for the FTP connections/transfers
export BM_UPLOAD_FTP_USER=""
the FTP user’s password
export BM_UPLOAD_FTP_PASSWORD=""
FTP specific remote hosts
export BM_UPLOAD_FTP_HOSTS=""
purge archives on remote hosts before uploading?
export BM_UPLOAD_FTP_PURGE=“true”
You can specify a time to live for archives uploaded with FTP
This can let you use different ttl’s locally and remotely
By default, BM_ARCHIVE_TTL will be used.
export BM_UPLOAD_FTP_TTL=""
destination for FTP uploads (overrides BM_UPLOAD_DESTINATION)
export BM_UPLOAD_FTP_DESTINATION=""
##############################################################
The S3 method
#############################################################
The Amazon S3 method requires that you secure an S3
account. See http://aws.amazon.com
The bucket to upload to. This bucket must be dedicated to backup-manager
export BM_UPLOAD_S3_DESTINATION=""
the S3 access key provided to you
export BM_UPLOAD_S3_ACCESS_KEY=""
the S3 secret key provided to you
export BM_UPLOAD_S3_SECRET_KEY=""
purge archives on remote hosts before uploading?
export BM_UPLOAD_S3_PURGE=“false”
##############################################################
The RSYNC method
#############################################################
Which directories should be backuped with rsync
export BM_UPLOAD_RSYNC_DIRECTORIES=""
Destination for rsync uploads (overrides BM_UPLOAD_DESTINATION)
export BM_UPLOAD_RSYNC_DESTINATION=""
The list of remote hosts, if you want to enable the upload
system, just put some remote hosts here (fqdn or IPs)
Leave it empty if you want to use the hosts that are defined in
BM_UPLOAD_HOSTS
export BM_UPLOAD_RSYNC_HOSTS=""
Do you want to dereference the files pointed by symlinks?
enter true or false (true can lead to huge archives, be careful).
export BM_UPLOAD_RSYNC_DUMPSYMLINKS=“false”
##############################################################
Section “BURNING”
- Automatic CDR/CDRW/DVDR burning
#############################################################
the method of burning archives from the list :
- DVD : burn archives on a DVD medium
(that doesn’t need formatting, like DVD+RW).
- DVD-RW : blank the DVD medium and burn archives
(recommanded for DVD-RW media).
- CDRW : blank the CDRW and burn the whole
ARCHIVES_REPOSITORY or only
the generated archives.
- CDR : burn the whole ARCHIVES_REPOSITORY or
only the generated archives.
- none : disable the burning system
Note that if backup-manager is run from interactive prompt you
will be asked to insert disc(s) when needed
export BM_BURNING_METHOD=“none”
When the CD is burnt, it is possible to check every file’s
MD5 checksum to see if the CD is not corrupted.
export BM_BURNING_CHKMD5=“false”
The device to use for mounting the cdrom
export BM_BURNING_DEVICE="/dev/cdrom"
You can force cdrecord to use a specific device
Fill in the full path to the device to use or even
e.g. BM_BURNING_DEVFORCED="/dev/cdrom"
If none specified, the default cdrecord device will be used.
export BM_BURNING_DEVFORCED=""
By default backup-manager will make Joliet media (using the mkisofs switches
: “-R -J”). You can change these if you want to use non-Joliet disc images.
Change this only if you know what you’re doing. Refer to mkisofs(8) for
details.
export BM_BURNING_ISO_FLAGS="-R -J"
enter here the max size of your media
(usal sizes are 4200 for DVD media and 700 or 800 for CDR media)
export BM_BURNING_MAXSIZE=“650”
##############################################################
Advanced settings, use this with care.
#############################################################
Every output made can be sent to syslog
set this to “true” or “false”
export BM_LOGGER=“true”
Which level of messages do you want to log to syslog?
possible values are : debug,info,warning,error
export BM_LOGGER_LEVEL=“debug”
You can choose which facility to use
export BM_LOGGER_FACILITY=“user”
Enter here some shell script.
It will be executed before the first action of backup-manager.
export BM_PRE_BACKUP_COMMAND=""
Enter here some shell script.
It will be executed after the last action of backup-manager.
export BM_POST_BACKUP_COMMAND=""
[/code]
Voici la commande du pour lister la taille des dossiers de la partition root de 20 Go. Notez que seulement 5Go (5082618 Ko) sont totalisés dans la commande qui s’applique sur /. Je ne comprends pas pourquoi !
gelinp@gelinux:/#du --exclude='/home*' --exclude='/media*' --max-depth=2 | sort -n -r
5082618 .
4180876 ./usr
1857672 ./usr/share
1741488 ./usr/lib
646032 ./var
432132 ./usr/bin
226068 ./var/www
223628 ./var/lib
188812 ./lib
167960 ./lib/modules
159308 ./var/cache
72196 ./usr/include
42116 ./usr/src
36030 ./boot
34752 ./usr/sbin
16896 ./var/log
16636 ./lib/i386-linux-gnu
12972 ./var/tmp
11508 ./sbin
9204 ./etc
7772 ./bin
6972 ./var/backups
2135 ./boot/grub
1516 ./lib/udev
1484 ./root
1064 ./lib/xtables
1008 ./etc/ssl
836 ./run
780 ./root/.rpmdb
552 ./run/udev
520 ./etc/X11
480 ./root/.kde
472 ./etc/apache2
416 ./etc/init.d
404 ./usr/local
336 ./etc/sane.d
312 ./etc/acpi
308 ./lib/live
304 ./etc/exim4
228 ./etc/ImageMagick
208 ./lib/terminfo
200 ./etc/bash_completion.d
184 ./etc/fonts
172 ./etc/ssh
172 ./etc/php5
172 ./etc/default
172 ./etc/dbus-1
168 ./var/spool
156 ./etc/java-6-openjdk
148 ./lib/systemd
144 ./lib/firmware
136 ./etc/console-setup
124 ./etc/java
120 ./etc/wicd
120 ./etc/apt
112 ./usr/games
104 ./etc/texmf
104 ./etc/pam.d
104 ./etc/cups
96 ./etc/xdg
96 ./etc/speech-dispatcher
92 ./root/.synaptic
84 ./etc/ppp
80 ./run/shm
72 ./etc/sgml
72 ./etc/network
72 ./etc/logrotate.d
68 ./etc/xml
68 ./etc/kde4
68 ./etc/initramfs-tools
68 ./etc/cron.daily
60 ./etc/grub.d
56 ./run/kdm
56 ./etc/lvm
52 ./etc/security
52 ./etc/polkit-1
48 ./lib/security
48 ./etc/init
44 ./lib/init
44 ./etc/wpa_supplicant
44 ./etc/phpmyadmin
44 ./etc/logcheck
40 ./etc/vga
40 ./etc/PackageKit
40 ./etc/alternatives
36 ./etc/NetworkManager
36 ./etc/ghostscript
36 ./etc/dhcp
32 ./etc/vpnc
32 ./etc/kernel
32 ./etc/iproute2
32 ./etc/emacs
32 ./etc/bluetooth
28 ./etc/udev
28 ./etc/turboprint
28 ./etc/dpkg
24 ./run/samba
24 ./lib/lsb
24 ./lib/crda
24 ./etc/vlc
24 ./etc/pulse
24 ./etc/mysql
24 ./etc/Muttrc.d
24 ./etc/mplayer
24 ./etc/menu-methods
24 ./etc/gconf
24 ./etc/avahi
20 ./tmp
20 ./root/.local
20 ./root/.config
20 ./root/.antidote
20 ./etc/subversion
20 ./etc/skel
20 ./etc/samba
20 ./etc/pm
20 ./etc/modprobe.d
20 ./etc/libreoffice
20 ./etc/cron.weekly
20 ./etc/ConsoleKit
16 ./root/.gconf
16 ./root/.aptitude
16 ./lost+found
16 ./lib/hdparm
16 ./etc/timidity
16 ./etc/systemd
16 ./etc/perl
16 ./etc/openal
16 ./etc/lirc
16 ./etc/ld.so.conf.d
16 ./etc/foomatic
16 ./etc/dirmngr
16 ./etc/cupshelpers
16 ./etc/cron.monthly
16 ./etc/cron.d
16 ./etc/chatscripts
16 ./etc/blends
16 ./etc/apm
12 ./run/cups
12 ./root/.dbus
12 ./lib/modprobe.d
12 ./etc/wildmidi
12 ./etc/w3m
12 ./etc/vim
12 ./etc/ufw
12 ./etc/resolvconf
12 ./etc/request-key.d
12 ./etc/pkcs11
12 ./etc/obex-data-server
12 ./etc/live
12 ./etc/listaller
12 ./etc/libpaper.d
12 ./etc/libnl-3
12 ./etc/insserv.conf.d
12 ./etc/groff
12 ./etc/dhcp3
12 ./etc/dbconfig-common
12 ./etc/console-tools
12 ./etc/ca-certificates
12 ./etc/akonadi
12 ./boot/lost+found
8 ./var/mail
8 ./run/console
8 ./root/.uim.d
8 ./etc/UPower
8 ./etc/terminfo
8 ./etc/sysctl.d
8 ./etc/sudoers.d
8 ./etc/snmp
8 ./etc/selinux
8 ./etc/rcS.d
8 ./etc/rc6.d
8 ./etc/rc5.d
8 ./etc/rc4.d
8 ./etc/rc3.d
8 ./etc/rc2.d
8 ./etc/rc1.d
8 ./etc/rc0.d
8 ./etc/python2.7
8 ./etc/python2.6
8 ./etc/python
8 ./etc/purple
8 ./etc/profile.d
8 ./etc/pcmcia
8 ./etc/openvpn
8 ./etc/menu
8 ./etc/ldap
8 ./etc/javascript-common
8 ./etc/.java
8 ./etc/insserv
8 ./etc/ifplugd
8 ./etc/icedtea-web
8 ./etc/hp
8 ./etc/gtk-3.0
8 ./etc/gtk-2.0
8 ./etc/gdb
8 ./etc/esound
8 ./etc/dictionaries-common
8 ./etc/cron.hourly
8 ./etc/calendar
4 ./var/opt
4 ./var/local
4 ./tmp/pulse-KkUqzvGptuBM
4 ./tmp/ksocket-gelinp
4 ./tmp/kde-kdm
4 ./srv
4 ./selinux
4 ./run/xauth
4 ./run/wicd
4 ./run/timidity
4 ./run/network
4 ./run/exim4
4 ./run/dbus
4 ./run/ConsoleKit
4 ./run/avahi-daemon
4 ./.pulse
4 ./opt
4 ./mnt
4 ./etc/usb_modeswitch.d
4 ./etc/update-notifier
4 ./etc/sensors.d
4 ./etc/rsyslog.d
4 ./etc/opt
4 ./etc/ODBCDataSources
4 ./etc/fstab.d
0 ./tmp/.X11-unix
0 ./tmp/.winbindd
0 ./tmp/ssh-gwBpWWajHkIm
0 ./tmp/pulse-PKdhtXMmr18n
0 ./tmp/ksocket-kdm
0 ./tmp/kde-gelinp
0 ./tmp/.ICE-unix
0 ./tmp/gpg-Li88A8
0 ./tmp/akonadi-gelinp.6ptEc3
0 ./sys/power
0 ./sys/module
0 ./sys/kernel
0 ./sys/hypervisor
0 ./sys/fs
0 ./sys/firmware
0 ./sys/devices
0 ./sys/dev
0 ./sys/class
0 ./sys/bus
0 ./sys/block
0 ./sys
0 ./run/xdmctl
0 ./run/udisks
0 ./run/sshd
0 ./run/sendsigs.omit.d
0 ./run/rpcbind
0 ./run/pm-utils
0 ./run/mount
0 ./run/lock
0 ./run/lirc
0 ./run/initramfs
0 ./run/dirmngr
0 ./run/apache2
0 ./proc/tty
0 ./proc/sysvipc
0 ./proc/sys
0 ./proc/irq
0 ./proc/fs
0 ./proc/driver
0 ./proc/dri
0 ./proc/bus
0 ./proc/asound
0 ./proc/acpi
0 ./proc/8
0 ./proc/796
0 ./proc/794
0 ./proc/7
0 ./proc/6657
0 ./proc/6656
0 ./proc/6627
0 ./proc/6559
0 ./proc/6554
0 ./proc/6531
0 ./proc/6492
0 ./proc/6482
0 ./proc/6433
0 ./proc/6405
0 ./proc/6403
0 ./proc/6
0 ./proc/567
0 ./proc/550
0 ./proc/546
0 ./proc/531
0 ./proc/5153
0 ./proc/5152
0 ./proc/515
0 ./proc/514
0 ./proc/5138
0 ./proc/5120
0 ./proc/5119
0 ./proc/5116
0 ./proc/5106
0 ./proc/5087
0 ./proc/503
0 ./proc/475
0 ./proc/474
0 ./proc/4193
0 ./proc/4159
0 ./proc/4150
0 ./proc/4120
0 ./proc/4010
0 ./proc/4003
0 ./proc/3989
0 ./proc/3985
0 ./proc/3984
0 ./proc/3982
0 ./proc/3978
0 ./proc/3960
0 ./proc/3958
0 ./proc/3957
0 ./proc/3954
0 ./proc/3948
0 ./proc/3939
0 ./proc/3938
0 ./proc/3933
0 ./proc/3926
0 ./proc/3901
0 ./proc/3899
0 ./proc/3895
0 ./proc/3791
0 ./proc/3770
0 ./proc/3766
0 ./proc/3759
0 ./proc/3748
0 ./proc/3747
0 ./proc/3727
0 ./proc/3723
0 ./proc/3720
0 ./proc/3716
0 ./proc/3714
0 ./proc/3712
0 ./proc/3711
0 ./proc/3683
0 ./proc/3662
0 ./proc/3639
0 ./proc/3638
0 ./proc/3635
0 ./proc/3634
0 ./proc/3622
0 ./proc/354
0 ./proc/3533
0 ./proc/3509
0 ./proc/3506
0 ./proc/3505
0 ./proc/3504
0 ./proc/3503
0 ./proc/3502
0 ./proc/3501
0 ./proc/3472
0 ./proc/3471
0 ./proc/3395
0 ./proc/3366
0 ./proc/3341
0 ./proc/3323
0 ./proc/3297
0 ./proc/3272
0 ./proc/3246
0 ./proc/3
0 ./proc/2919
0 ./proc/2901
0 ./proc/2894
0 ./proc/2859
0 ./proc/2855
0 ./proc/2851
0 ./proc/2825
0 ./proc/2804
0 ./proc/27
0 ./proc/2660
0 ./proc/2659
0 ./proc/2658
0 ./proc/2657
0 ./proc/2656
0 ./proc/2635
0 ./proc/26
0 ./proc/2598
0 ./proc/2595
0 ./proc/2594
0 ./proc/2572
0 ./proc/2550
0 ./proc/2528
0 ./proc/25
0 ./proc/2479
0 ./proc/2443
0 ./proc/24
0 ./proc/2372
0 ./proc/2354
0 ./proc/2337
0 ./proc/2336
0 ./proc/2312
0 ./proc/23
0 ./proc/2296
0 ./proc/2251
0 ./proc/22
0 ./proc/21
0 ./proc/207
0 ./proc/206
0 ./proc/20
0 ./proc/2
0 ./proc/1926
0 ./proc/1919
0 ./proc/1915
0 ./proc/191
0 ./proc/1908
0 ./proc/19
0 ./proc/1874
0 ./proc/18
0 ./proc/17
0 ./proc/16
0 ./proc/1542
0 ./proc/1541
0 ./proc/15
0 ./proc/148
0 ./proc/147
0 ./proc/14
0 ./proc/133
0 ./proc/13
0 ./proc/120
0 ./proc/12
0 ./proc/118
0 ./proc/114
0 ./proc/103
0 ./proc/10
0 ./proc/1
0 ./proc
0 ./dev/snd
0 ./dev/pts
0 ./dev/net
0 ./dev/mapper
0 ./dev/input
0 ./dev/gelinux
0 ./dev/dri
0 ./dev/disk
0 ./dev/cpu
0 ./dev/char
0 ./dev/bus
0 ./dev/bsg
0 ./dev/block
0 ./devEnfin lorsque je recherche des fichiers de plus de 50 Mo j’ai une courte liste qui se termine par des messages d’erreurs dans le dossier /proc… :
gelinp@gelinux:/$ sudo find / -type d \( -name media -o -name home \) -prune -o -size +50M -print
/usr/share/icons/oxygen/icon-theme.cache
/run/shm/pulse-shm-3249531890
/run/shm/pulse-shm-4135341107
/run/shm/pulse-shm-2823021223
/run/shm/pulse-shm-2069654137
/proc/kcore
find: "/proc/11645/task/11645/fd/5": Aucun fichier ou dossier de ce type
find: "/proc/11645/task/11645/fdinfo/5": Aucun fichier ou dossier de ce type
find: "/proc/11645/fd/5": Aucun fichier ou dossier de ce type
find: "/proc/11645/fdinfo/5": Aucun fichier ou dossier de ce type
/sys/devices/pci0000:00/0000:00:02.0/resource2
/sys/devices/pci0000:00/0000:00:02.0/resource2_wc
J’ai essayé de lancer la commande de réparation de partition : e2fsck -f /dev/gelinux/root. Mais comme il manque de la place elle refuse de se lancer…
Je vous remercie pour votre aide !
