gvfs reports root partition 100% full
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simplebackup (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: gvfs-fuse
This is a major problem since it prevents any operation that wants to store to the filesystem, including /tmp. gvfs seems to have decided that one of my network drives is in my root partition. That makes it think the root partition is full. (it isn't, really.)
A backup, made with Simple Backup, is in /mnt/mediavault
I'm running, 8.04. gvfs-fuse 0.2.3-0ubuntu5
This is similar to, but not the same as these bugs: https:/
https:/
How can I wake gvfs up to the fact that 2.2GB are NOT on my root partition, but somewhere else entirely?!
Changed in gvfs: | |
status: | New → Confirmed |
This is what finally worked to get my hard drive back:
All done as root:
umount gvfs-fuse-daemon
Change ownership of backup file generated by SimpleBackup on network drive, and move to another location.
Change group of that network directory from "1000" to root.
remove that directory and all its subdirectories (#rm -r /mnt/network- drive/backup) It had no visible or hidden subdirs, but an ordinary rmdir command kept saying it was not empty.
On my computer (not the network drive), remove .gvfs both in my user home dir, and in root's home directory.
exit root. reboot.
The gnome devs really need to get to work on this issue. A filesystem that can make your computer next to nonfunctional is not a minor bug.