Summary: | after doing an emerge the disk usage is 100 percent, after rebooting it is normal, but all settings in my home dir were deleted | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Manuel Schulze <mani-soft> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | x86-kernel |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
my kernel config
my kernel config emerge debug output |
Description
Manuel Schulze
2003-08-15 13:46:17 UTC
what is 'normal' ? also, please post kernel information Created attachment 16146 [details]
my kernel config
gentoo-sources-2.4.20-r6
Created attachment 16147 [details]
my kernel config
gentoo-sources-2.4.20-r6
sorry, added the config two times (there was an error at the first try, so i thought it was not submitted properly) normale is a disk usage of 30% which is before the error and after the reboot So... What were you emerging? Where did it stop? What processes were running? Is it repeatable? Do you know what the problem is? What were you emerging? abiword, but it happened with other packages earlier, too Where did it stop? it ran fine What processes were running? the programmes i wrote earlier and the standard linux stuff (syslog-ng, dcron, xfs, X, gdm, some gnome-terminals, nautilus) Is it repeatable? no Do you know what the problem is? no ;) it happened again i watched a dvd in xine (xchat was also opened) Aug 17 20:50:12 Manuel smb_trans2_request: result=-104, setting invalid Aug 17 20:50:12 Manuel smb_retry: successful, new pid=1342, generation=3 Aug 17 21:06:21 Manuel (mani-1268): Could not write saved state file '/home/mani/.gconfd/saved_state.tmp' fd: 10: No space left on device Aug 17 21:18:40 Manuel (mani-1268): Failed to log removal of listener to logfile (most likely harmless, may result in a notification weirdly reappearing): Failed: Failed to log removal of listener to gconfd logfile; might erroneously re-add the listener if gconfd exits or shuts down (No space left on device) this is the last output of /var/log/lastlog please paste #mount #df /etc/fstab /etc/mtab mount: /dev/hda5 on / type ext3 (rw,noatime) none on /dev type devfs (rw) none on /proc type proc (rw) /dev/hda1 on /mnt/windows type ntfs (rw,umask=000) /dev/hdb1 on /mnt/backup type vfat (rw,umask=000) none on /mnt/cdrom type supermount (ro,dev=/dev/hdc,fs=iso9660,--,umask=000) none on /dev/shm type tmpfs (rw) none on /proc/bus/usb type usbfs (rw) df: Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda5 19765692 5113600 13648032 28% / /dev/hda1 57681348 34353648 23327700 60% /mnt/windows /dev/hdb1 19999136 106400 19892736 1% /mnt/backup none 257628 0 257628 0% /dev/shm fstab: (relevant entries) /dev/hda1 /mnt/windows ntfs defaults,umask=000 0 0 /dev/hda5 / ext3 noatime 0 1 /dev/hda6 none swap sw 0 0 /dev/hdb1 /mnt/backup vfat defaults,umask=000 0 0 none /mnt/cdrom supermount dev=/dev/hdc,fs=iso9660,--,ro,umask=000 0 0 # NOTE: The next line is critical for boot! proc /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 mtab: /dev/hda5 / ext3 rw,noatime 0 0 none /dev devfs rw 0 0 none /proc proc rw 0 0 /dev/hda1 /mnt/windows ntfs rw,umask=000 0 0 /dev/hdb1 /mnt/backup vfat rw,umask=000 0 0 none /mnt/cdrom supermount ro,dev=/dev/hdc,fs=iso9660,--,umask=000 0 0 none /dev/shm tmpfs rw 0 0 none /proc/bus/usb usbfs rw 0 0 Since this both occurs on different filesystems [thus eliminating kernel bugs which may be to blame for this...] and your system doesn't go nuts and hang and applications still run as the temp files still have room to propagate, this looks a lot like gconf/gnome-vfs going horribly wrong... the "no space left on device" message is telling, don't you think? how is your diskspace? my disk usage doesn't jump from 28% to exactly 100% with 0B left while i'm browsing... Can you please try a vanilla kernel and see if you get the same result? Also, please run "fsck" on all your partitions from a BootCD/something to make sure they are not corrupted or anything... Could you upgrade to the latest version of any Gnome-related libraries and see if you still get this error? i use the most recent ones already Can you please do an emerge --debug of something and send back the log? Created attachment 16733 [details]
emerge debug output
emerge superadduser --debug
That debug log looks OK, and I can't see any problems with it. Did the disk usage jump after that happened? If so, can you merge something like 'gtkdiskfree' and see if there any horrid amounts of temporary files? Can you try this with a vanilla kernel? it didn't jump i'm using a vinalla kernel for two days now and the problem didn't occur yet (which does not mean it has gone) if it happens again, i'll check with gtkdiskfree for temporary files AFAIK it got fixed, could you try this again with current gentoo sources? Reopen if it still appears. |