I came across the same problem after accidentally starting the backup
without having the backup media mounted. Finding the tricky space is
tricky since you have to unmount some devices in order to see the
missing files. For example, I backup on an external hard drive mounted
at /media/sdb1. The
Was a solution found for this?
The last report was some months ago.
I am using 8.10 intrepid.
I am getting what appears to be this issue.
I had 16 GB allocated to my / partition.
Home and swap are seperate.
A few days ago I was unable to do anything requiring root access and also
things like
Reading some posts here and seeing some of you pointing the finger at
sbackup. I'm having the same problem and I DO NOT use sbackup and never
have.
I've installed Hardy Heron three times in the last 18 hours and keep
running into the same problem with my partition filling up and then not
being
I too use Simple Backup, but I'm not sure the problem is as Jan Rybka
says. In my case, it's not just background jobs without notices. gvfs-
fuse-daemon thinks the root partition is full, and even rebooting
doesn't help (so not just a matter of restarting the service). Since
the partition is
I've found the solution but it's really stupid and some kind tricky.
Background of problem
The thing is that I have an backup system (Simple Backup) that runs in
background and doesn't show it's presence, so I didn't know that it was
running. The backup was suppose to store about 4-5 GB of data
** Attachment added: What I see in Baobab (windows and media are mounted from
other partitions)
http://launchpadlibrarian.net/13426693/Wykorzystanie1.png
--
Root partition usage reaches 100% without reason
https://bugs.launchpad.net/bugs/217389
You received this bug notification because you
(I didn't see this option earlier)
Screen from System monitor.
** Attachment added: System monitor
http://launchpadlibrarian.net/13426719/Wykorzystanie2.png
--
Root partition usage reaches 100% without reason
https://bugs.launchpad.net/bugs/217389
You received this bug notification because