4.2M /sbin
696K /dev
4.0K /srv
11G /backup
176M /var
4.0K /opt
6.4M /boot
4.2M /etc
68M /lib
12K /media
16K /lost+found
623M /usr
0 /sys
4.0K /selinux
4.0K /mnt
80K /home
0 /tmp
24K /root
du: cannot access `/proc/18935/task/18935/fd/4': No such file or directory
du: cannot access `/proc/18935/task/18935/fdinfo/4': No such file or
directory
du: cannot access `/proc/18935/fd/4': No such file or directory
du: cannot access `/proc/18935/fdinfo/4': No such file or directory
0 /proc
44G /documents
336G /maxtor
4.1M /bin
391G /
391G total
lsof doesn't show any files greater than 5MB in size.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
01-27-2010, 10:26 AM
Marc Olive
Root filesystem full; faubackup problem?
El Wednesday 27 January 2010 12:20:28 Tim Beauregard va escriure:
> Marc Olive wrote:
> > Maybe you copied /document files to /documents without being hdb1
> > monuted? Try to umount /documents and see if there are still all files.
>
> tim@server:~$ umount /documents
> tim@server:~$ ls -l /documents/
> total 0
>
> As expected?
No, there aren't the files, the problem was not the one I was pointing to.
Mount again "documents" and continue searching a solution.
--
Marc Olivé
Grup Blau
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
?
(Don't forget to remount /dev/hdb1 and /dev/sda1 ;-)
--
Regards,
Jörg-Volker.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
01-27-2010, 04:06 PM
"James Wu"
Root filesystem full; faubackup problem?
I wouldn't dismiss what Marc was onto. If you do the math, 44G in /documents + 11G in the rest of / == 55G, seems to be a bit more than coincidence. I know you already tried ls -l /documents/ after you umounted but just for curiosity's sake, I wonder what happens when you do:
umount /documents
du -sh /documents
-----Original Message-----
From: Marc Olive [mailto:marc.olive@grupblau.com]
Sent: January 27, 2010 6:26 AM
To: debian-user@lists.debian.org
Subject: Re: Root filesystem full; faubackup problem?
El Wednesday 27 January 2010 12:20:28 Tim Beauregard va escriure:
> Marc Olive wrote:
> > Maybe you copied /document files to /documents without being hdb1
> > monuted? Try to umount /documents and see if there are still all files.
>
> tim@server:~$ umount /documents
> tim@server:~$ ls -l /documents/
> total 0
>
> As expected?
No, there aren't the files, the problem was not the one I was pointing to.
Mount again "documents" and continue searching a solution.
--
Marc Olivé
Grup Blau
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
01-27-2010, 07:40 PM
Tim Beauregard
Root filesystem full; faubackup problem?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James Wu wrote:
> I wouldn't dismiss what Marc was onto. If you do the math, 44G in
> /documents + 11G in the rest of / == 55G, seems to be a bit more than
> coincidence. I know you already tried ls -l /documents/ after you
> umounted but just for curiosity's sake, I wonder what happens when you do:
>
> umount /documents
> du -sh /documents
du -sh /documents/
4.0K /documents/
I agree with you about 44+11. The mystery if this is the origin of my
problem, is that we are talking about two separate drives (/dev/hdb1 +
/dev/hda1).
My backup strategy involves two Maxtor external hard drives, one being
connected for six months and then swapped with the second which has been
stored off site. Somehow the non-connected Maxtor data has been saved
on /dev/hda1.
My easy solution is to umount /maxtor, and delete all the old backups.
I wonder, maybe faubackup can't cope with disappearing data...?
Thanks for any input.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
01-28-2010, 04:33 AM
bruno
Root filesystem full; faubackup problem?
Tim Beauregard wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
James Wu wrote:
I wouldn't dismiss what Marc was onto. If you do the math, 44G in
/documents + 11G in the rest of / == 55G, seems to be a bit more than
coincidence. I know you already tried ls -l /documents/ after you
umounted but just for curiosity's sake, I wonder what happens when you do:
umount /documents
du -sh /documents
du -sh /documents/
4.0K /documents/
I agree with you about 44+11. The mystery if this is the origin of my
problem, is that we are talking about two separate drives (/dev/hdb1 +
/dev/hda1).
My backup strategy involves two Maxtor external hard drives, one being
connected for six months and then swapped with the second which has been
stored off site. Somehow the non-connected Maxtor data has been saved
on /dev/hda1.
My easy solution is to umount /maxtor, and delete all the old backups.
I wonder, maybe faubackup can't cope with disappearing data...?
Thanks for any input.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Maybe it is due to the way faubackup works. In the man pages it states :
BUGS
You need a filesystem with stable device id and inode number so that
faubackup can correctly find your files again. This may be violated by
some remote filesystems, for example Samba.
Maybe swapping drives falls into this categorie too.
Bruno
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Root filesystem full; faubackup problem?
