Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 77054 - GRP upgrade to now fubared Ext3fs root partition. Claimed 17TB used, system became unuseable.
Summary: GRP upgrade to now fubared Ext3fs root partition. Claimed 17TB used, system ...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-07 11:51 UTC by Daniel Lamblin
Modified: 2005-01-07 13:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Lamblin 2005-01-07 11:51:37 UTC
I installed GRP 2004.3-r1 on a PII-400 with 10gb hd.
after installing firefox and some bin packages, I synced portage, emerged new portage and updated the world.  The process stopped 3 times but resumed the first time, resumed skipping firefox (bug 77081), and then failed during gaim claiming internal gcc errors; here the filesystem became full, then fell out from under me.

Reproducible: Didn't try
Steps to Reproduce:
1.install grp 2004.3-r1 on PII with bin packages
2.emerge sync; emerge portage; emerge world;
3.resume a few times
4.eventually the file system messes up....

Actual Results:  
> I'm having some kind of emerge problem that triggers code asking me to 
report this to you. It may be my problem alone though.
> 
> checking for machine/endian.h... no
> checking arpa/nameser_compat.h usability... no
> checking arpa/nameser_compat.h presence... yes
> configure: WARNING: arpa/nameser_compat.h: present but cannot be compiled
> configure: WARNING: arpa/nameser_compat.h: check for missing prerequisite 
headers?
> configure: WARNING: arpa/nameser_compat.h: see the Autoconf documentation
> configure: WARNING: arpa/nameser_compat.h: section "Present But Cannot Be 
Compiled"
> configure: WARNING: arpa/nameser_compat.h: proceeding with the 
preprocessor's result
> configure: WARNING: arpa/nameser_compat.h: in the future, the compiler will 
take precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> [...]
> checking paths.h presence... yes
> configure: WARNING: paths.h: present but cannot be compiled
> configure: WARNING: paths.h: check for missing prerequisite headers?
> configure: WARNING: paths.h: see the Autoconf documentation
> configure: WARNING: paths.h: section "Present But Cannot Be Compiled"
> configure: WARNING: paths.h: proceeding with the preprocessor's result
> configure: WARNING: paths.h: in the future, the compiler will take precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for paths.h... yes
> checking sgtty.h usability... no
> checking sgtty.h presence... yes
> configure: WARNING: sgtty.h: present but cannot be compiled
> configure: WARNING: sgtty.h: check for missing prerequisite headers?
> configure: WARNING: sgtty.h: see the Autoconf documentation
> configure: WARNING: sgtty.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sgtty.h: proceeding with the preprocessor's result
> configure: WARNING: sgtty.h: in the future, the compiler will take precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for sgtty.h... yes
> checking stdarg.h usability... no
> checking stdarg.h presence... yes
> configure: WARNING: stdarg.h: present but cannot be compiled
> configure: WARNING: stdarg.h: check for missing prerequisite headers?
> configure: WARNING: stdarg.h: see the Autoconf documentation
> configure: WARNING: stdarg.h: section "Present But Cannot Be Compiled"
> configure: WARNING: stdarg.h: proceeding with the preprocessor's result
> configure: WARNING: stdarg.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for stdarg.h... yes
> checking sys/cdefs.h usability... no
> checking sys/cdefs.h presence... yes
> configure: WARNING: sys/cdefs.h: present but cannot be compiled
> configure: WARNING: sys/cdefs.h: check for missing prerequisite headers?
> configure: WARNING: sys/cdefs.h: see the Autoconf documentation
> configure: WARNING: sys/cdefs.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sys/cdefs.h: proceeding with the preprocessor's result
> configure: WARNING: sys/cdefs.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for sys/cdefs.h... yes
> checking sys/file.h usability... no
> checking sys/file.h presence... yes
> configure: WARNING: sys/file.h: present but cannot be compiled
> configure: WARNING: sys/file.h: check for missing prerequisite headers?
> configure: WARNING: sys/file.h: see the Autoconf documentation
> configure: WARNING: sys/file.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sys/file.h: proceeding with the preprocessor's result
> configure: WARNING: sys/file.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for sys/file.h... yes
> checking sys/filio.h usability... no
> checking sys/filio.h presence... no
> checking for sys/filio.h... no
> checking sys/ioctl.h usability... no
> checking sys/ioctl.h presence... yes
> configure: WARNING: sys/ioctl.h: present but cannot be compiled
> configure: WARNING: sys/ioctl.h: check for missing prerequisite headers?
> configure: WARNING: sys/ioctl.h: see the Autoconf documentation
> configure: WARNING: sys/ioctl.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sys/ioctl.h: proceeding with the preprocessor's result
> configure: WARNING: sys/ioctl.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for sys/ioctl.h... yes
> checking sys/msgbuf.h usability... no
> checking sys/msgbuf.h presence... no
> checking for sys/msgbuf.h... no
> checking sys/select.h usability... no
> checking sys/select.h presence... yes
> configure: WARNING: sys/select.h: present but cannot be compiled
> configure: WARNING: sys/select.h: check for missing prerequisite headers?
> configure: WARNING: sys/select.h: see the Autoconf documentation
> configure: WARNING: sys/select.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sys/select.h: proceeding with the preprocessor's result
> configure: WARNING: sys/select.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for sys/select.h... yes
> checking sys/uio.h usability... no
> checking sys/uio.h presence... yes
> configure: WARNING: sys/uio.h: present but cannot be compiled
> configure: WARNING: sys/uio.h: check for missing prerequisite headers?
> configure: WARNING: sys/uio.h: see the Autoconf documentation
> configure: WARNING: sys/uio.h: section "Present But Cannot Be Compiled"
> configure: WARNING: sys/uio.h: proceeding with the preprocessor's result
> configure: WARNING: sys/uio.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for sys/uio.h... yes
> checking for sys/utsname.h... (cached) yes
> checking for sys/wait.h... (cached) yes
> checking termios.h usability... no
> checking termios.h presence... yes
> configure: WARNING: termios.h: present but cannot be compiled
> configure: WARNING: termios.h: check for missing prerequisite headers?
> configure: WARNING: termios.h: see the Autoconf documentation
> configure: WARNING: termios.h: section "Present But Cannot Be Compiled"
> configure: WARNING: termios.h: proceeding with the preprocessor's result
> configure: WARNING: termios.h: in the future, the compiler will take 
precedence
> configure: WARNING: ## ----------------------------------------------- ##
> configure: WARNING: ## Report this to gaim-devel@lists.sourceforge.net ##
> configure: WARNING: ## ----------------------------------------------- ##
> checking for termios.h... yes
> checking for struct tm.tm_zone... cat: write error: No space left on device
> 
> [1]+ Stopped emerge --resume --skipfirst
> tux root # df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/hda3 9321616 3554072 5294032 41% /
> /dev/hda1 38856 4734 32116 13% /boot
> none 127968 0 127968 0% /dev/shm
> 

[AFTER REPORTING THIS BUG TO GAIM, I:
 did another df, to find suddenly 101% used, with incorrect # of blocks
 # emerge clean
 key files could not be accessed
 I did a `du -k /usr/tmp/portage` thinking to delete files
and got this output:
du: cannot access `./binutils-2.14.90.0.8-r1/.ICE-unix/cross-gcc-3.3.4-
r1.tar.bz
[repeats more than 2000 times]
du: cannot access `./binutils-2.14.90.0.8-r1/.ICE-unix/cross-gcc-3.3.4-
r1.tar.bz
du: cannot access `./binutils-2.14.90.0.8-r1/.ICE-unix/cross-gcc-3.3.4-
r1.tar.bz
4       ./binutils-2.14.90.0.8-r1/.ICE-unix/cross-gcc-3.3.4-
r1.tar.bz2/dep/usr/p
du: cannot access `./binutils-2.14.90.0.8-r1/.ICE-unix/cross-gcc-3.3.4-
r1.tar.bz

tux portage # rm /root/packages-i686-2004.3.iso
tux portage # du -ks .
8       .
tux portage # du -k .
8       .
tux portage # ls
tux portage # pwd
/var/tmp/portage
tux portage # cd ..
tux tmp # ls
tux tmp # cd portage
tux portage # ls
tux portage # ls -l
total 0
tux portage # cd ..
tux tmp # ls
tux tmp # ls -l
total 0
[turn on console to see tons of I/O errors still happening]
tux tmp # reboot
-bash: reboot: command not found
tux tmp # df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda3            17179719972 17179719172       800 100% /
/dev/hda1                38856      4734     32116  13% /boot
none                    127968         0    127968   0% /dev/shm
tux tmp # /bin/shutdow
-bash: /bin/shutdow: No such file or directory
tux tmp # /bin/shutdown
-bash: /bin/shutdown: No such file or directory
tux tmp # ps -ax
-bash: /bin/ps: No such file or directory
tux tmp #
tux tmp # logout

[
could not reboot; hard reset; system kernel panicked mounting root;
I had built ext2fs and ext3fs in the kernel 2.4.26-gentoo-r9
boot live cd e2fsck /dev/hda3
lots of unlinked, orphaned, bad refcount inodes, some tagged compressed, but 
filesystem is not compressed.
new df shows 3543260 of 9321616
haven't tried the 'recovered' system, afraid of data loss.
]

Expected Results:  
reasonable usage on my root partition. not sudden fullness. not bad flags set.

see emerge info in bug 77018
Comment 1 Chris Gianelloni (RETIRED) gentoo-dev 2005-01-07 12:09:00 UTC
Have you tried running memtest86 from the LiveCD?  It really sounds like you're having hardware failures, especially with your other bug.
Comment 2 Daniel Lamblin 2005-01-07 12:39:50 UTC
yes, I did run the complete set of tests twice (it loops on its own) before installing.  I have run them again now, they seem fine too.
I even took the step to check from bad blocks during the format.
with -c -c to do it slower, and left it going over night, installing the next day.  I got sick of the stage1 build though and reformatted without -c and did a stage3 plus the GRP packages mounted through -o loop; then I did the rest of what I described above; being an emerge --sync etc. etc.
Comment 3 Daniel Lamblin 2005-01-07 13:32:05 UTC
okay... it's memory;
seems some went bad recently
the previous post's 'have run' should read 'ran to 90%'
and 'seem fine' should read 'seems okay till now'

at Pass 99% Test 97% Test #7 I get 18 errors;
I don't know how to read them:
tst pass failing addr          good     bad      errbits  count  chan
7   0    000005102894 - 81.1Mb ffffffff ffdfffff 00200000 1
...
7   0    00000531a894 - 83.6Mb ffffffff ffdfffff 00200000 1

Anyway, you can mark all those as NOT A BUG then I guess.