[i965gm] Perhaps Xorg not closing files, system reports full HD

[Saúl Romero]

Binary package hint: xorg

Hi. I opened this thread in Ubuntu forums with no luck at all. Hope someone can give me a clue of what happens.

http://ubuntuforums.org/showthread.php?t=1683746

Recently, gnome has been warning me about low disk space, always less than 1.5GiGs.

The problem is, baobab (disk usage analyzer) tells me that there are something like 50GiG free. I am sure that I have the free space ( I can write big files ) but the system keeps reporting low disk space. Even
Code:
df -h
looks wrong:

Code:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext4 221G 209G 638M 100% /
none devtmpfs 2.0G 272K 2.0G 1% /dev
none tmpfs 2.0G 1.9M 2.0G 1% /dev/shm
none tmpfs 2.0G 328K 2.0G 1% /var/run
none tmpfs 2.0G 0 2.0G 0% /var/lock
none debugfs 221G 209G 638M 100% /var/lib/ureadahead/debugfs
Wandering in some other thread, someone pointed out that some program may be deleting files ... but not closing them, and the offending program can be fount with
Code:
sudo lsof -s | grep DEL | sort -rnk 7,7
,which gives a wall of results like these
Code:
Xorg 1334 root DEL REG 0,4 8573 /drm mm object
Xorg 1334 root DEL REG 0,4 8572 /drm mm object
Xorg 1334 root DEL REG 0,4 8560 /drm mm object
Xorg 1334 root DEL REG 0,4 8559 /drm mm object
Xorg 1334 root DEL REG 0,4 8558 /drm mm object
Xorg 1334 root DEL REG 0,4 8557 /drm mm object
Xorg 1334 root DEL REG 0,4 8556 /drm mm object
Perhaps Xorg is having a very bad behavior?? What can I do to force it close the files , or whatever else that can give me back the hard disk space ... working is unpractical since most applications (gnome apps) think that there is no space left on the device.

My sistem is Ubuntu 10.10 64bit, with all the upgrades until today (proposed updates enabled)
XORG INFO

X.Org X Server 1.9.0
Release Date: 2010-08-20
X Protocol Version 11, Revision 0

Thanks in advance.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-26.46-generic 2.6.35.10
Uname: Linux 2.6.35-26-generic x86_64
Architecture: amd64
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: Off
 modes: 1280x800
 edid-base64: AP///////wBMo0E3AAAAAAARAQOAHRJ4CoHVlFdSiichUFQAAAABAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAHrMQAAAZAAAADwAAAAAAAAAAACOHAmQAAAAA/gBTQU1TVU5HCiAgICAgAAAA/gBMVE4xMzNBVDA3RzAxAIY=
DRM.card0.VGA.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x768 800x600 800x600 848x480 640x480
 edid-base64:
Date: Wed Feb 9 18:57:13 2011
DkmsStatus:
 vboxhost, 4.0.2, 2.6.35-26-generic, x86_64: installed
 vboxhost, 4.0.2, 2.6.35-25-generic, x86_64: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: TOSHIBA Satellite U405
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-26-generic root=UUID=3c11c350-4b00-49bd-acb0-6dbfce81cb80 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 07/12/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V3.00
dmi.board.name: Satellite U405
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV3.00:bd07/12/2008:svnTOSHIBA:pnSatelliteU405:pvrPSU40U-02M014:rvnTOSHIBA:rnSatelliteU405:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U405
dmi.product.version: PSU40U-02M014
dmi.sys.vendor: TOSHIBA
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-26-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:ff50]

[Saúl Romero (spacetree)]

Anyone with the same problem? It thats the case, please tell me some workaround so i can have that disk space. I really need it, thanks!

[bugbot (bugbot)]

Hey Saúl,

Thanks for your interest in Ubuntu.

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Saúl Romero (spacetree)]

Hi!

    Thanks for the attention. Currently, I have not been experiencing
the problem (I switched laptop) but I would like to test in Natty, the
laptop has the same graphics card. Just waiting for the end of the month
to install in my laptop.
> Hey Saúl,
>
>
> Thanks for your interest in Ubuntu.
>
> Thanks for testing maverick during its development period.
> Unfortunately it looks like this bug report didn't get attention during
> the maverick development period. But I see there's not been more
> comments on the bug since the release, which makes me wonder if this is
> still an issue for you?
>
> If you've not seen this issue since maverick's release yourself, it may
> have been solved by kernel or X or other updates that occurred late in
> the release; if so, would you mind please closing the bug for us? Go to
> the URL mentioned in this bug report, click the yellow icon(s) in the
> status column and set to 'Fix Released'.
>
> If you no longer have the hardware needed to reproduce the problem, or
> otherwise feel the bug no longer needs tracked in Launchpad, you can set
> the status to 'Invalid'.
>
> If you are the original reporter and still have this issue, just reply
> to this email saying so. (Or set the bug status to Confirmed.) If you
> are able to re-test this against 11.04 Natty Narwhal (our current
> development focus) and find the issue still affects Natty, please also
> run 'apport-collect <bug-number>' while running natty, which will add
> fresh logs and debug data, and flag it for the Ubuntu-X development team
> to look at.
>

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.