Nautilus

Size of contents in volume reported is incorrect

Bug #666033 reported by Alex Engelmann on 2010-10-24

This bug report is a duplicate of: Bug #585472: File System Properties reports 128 TB of use. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Nautilus	New	Medium	gnome-bugs #629394
	nautilus (Ubuntu)	Triaged	Low	Unassigned

Bug Description

Binary package hint: nautilus

This is my first bug report, so I'll follow the format shown below.

1) I'm using Ubuntu 10.10, the amd64 version
2) The problem is in nautilus version 1:2.32.0-0ubuntu1
3) Size of volume contents should be 129 GB
4) Size of volume contents is reported as 129 TB

The free space is correctly reported as 828.1GB. This problem happens repeatedly, so it's not a one-time glitch. I'm sure fixing it is trivial, but my programming experience is limited...

-Alex

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Oct 24 13:18:45 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: nautilus

Tags:

Revision history for this message

Alex Engelmann (alex-engelmann) wrote on 2010-10-24:

A screenshot of the problem. Edit (287.5 KiB, image/png)
Dependencies.txt Edit (5.1 KiB, text/plain; charset="utf-8")
GConfNonDefault.txt Edit (419 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (85.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (798 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (24.0 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (348 bytes, text/plain; charset="utf-8")

Revision history for this message

Alex Engelmann (alex-engelmann) wrote on 2010-10-25:

I thought 129GB seemed excessive, as I only recently set up this system. As it turns out, the size of the volume contents is NOT supposed to be 129GB, so it's a genuine error and not just a typo. According to the system monitor, I'm only using 26.5GiB, which sounds about right.

-Alex

summary:

- Size of contents in volume reported is incorrect, should be GB not TB.
+ Size of contents in volume reported is incorrect

Revision history for this message

Omer Akram (om26er) wrote on 2010-10-25:

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=633090

Changed in nautilus (Ubuntu):
importance:	Undecided → Low
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2010-10-25

Changed in nautilus:
importance:	Unknown → Medium
status:	Unknown → New

Omer Akram (om26er) on 2010-11-13

Changed in nautilus:
importance:	Medium → Unknown
status:	New → Unknown

Bug Watch Updater (bug-watch-updater) on 2010-11-13

Changed in nautilus:
importance:	Unknown → Medium
status:	Unknown → New

Revision history for this message

Evan Huus (eapache) wrote on 2010-11-16:

Not a bug in nautilus. The problem exists somewhere else.

Thanks to a comment upstream, I tracked the problem down to the file /proc/kcore. This file alone is reported as 128TB, even by the 'ls' command.

According to:
http://www.unixguide.net/linux/faq/04.16.shtml
The size of this file should be equal to the amount of memory in your system.

Does that make this a kernel bug?

Revision history for this message

Evan Huus (eapache) wrote on 2010-11-16:

Not even a kernel bug. According to:
http://www.novell.com/support/viewContent.do?externalId=7004153

/proc/kcore is 128TB on all 64-bit systems, because that is the maximum amount of memory that the kernel can address.

So the fix here is really to simply ignore this file when calculating disk usage in nautilus. More correctly, it should ignore all of /proc, since these files don't actually take up any disk space: they are virtual.