Re: dselect/apt & fsck
Here's the output of 'dpkg -l sysvinit':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii sysvinit 999 sysvinit dummy package for the Hurd.
Oh, the drives are all under 1GB. For that matter, if the drive gets trashed testing
things I have a spare just like it so it's not a big deal. :)
'vmstat' output. Mem usage is high as I was running e2fsck.static at the time.
I usually run at 0-10MB of swap used. Haven't checked while running X, though.
pagesize: 4K
size: 28M
free: 6.24M
active: 5.47M
inactive: 8.88M
wired: 7.44M
zero filled: 4.7G
reactivated: 350M
pageins: 841M
pageouts: 910M
page faults: 6686547
cow faults: 649203
memobj hit ratio: 93%
swap size: 91.5M
swap free: 53.6M
I tried reproducing this error several times to no effect. As I was about to
shrug and declare it mystically fixed, it happened again.
I was logged in and using dselect from another machine. This is what showed
on the screen directly attached to the Hurd machine:
memory_object_data_request(0x0, 0x0, 0x43000, 0x1000, 0x3) failed, 268435459
... And a few seconds later, a warning that the /dev/hd0s2 filesystem
wasn't unmounted cleanly. 'mount' showed it to be suddenly mounted read
only. I was able to do several apt-get install's before this happened. It
was only running dselect a couple times as root that it popped up. Seems
more frequent under dselect for some reason. The error I got on the screen
running dselect was:
/dev/fd/4: line 54: 9741 Bus error $APTGET $OPTS "$APT_OPTO"
"$APT_OPT1" dselect-upgrade
After that was a small paragraph from dselect telling me it noted the error
and was going to try to configure what was installed (nothing). I hit enter
to continue. It said installation returned error 100. I quit out of dselect
and started work cleaning the filesystem. Here's a log of how that went.
Script started on Mon Apr 1 06:31:33 2002
root@pandora:~# sync
root@pandora:~# mount
mount: /etc/fstab: Warning: duplicate entry for mount point swap (/dev/hd1s3)
device:hd1s1 on / type ext2fs.static (rw,sync=5)
/dev/hd1s2 on /home type ext2 (rw,sync=5)
/dev/hd0s2 on /opt type ext2 (ro,sync=5)
root@pandora:~# settrans -g /opt
root@pandora:~# showtrans /opt
root@pandora:~# e2fsck.static -cy /dev/hd0s2
e2fsck 1.25 (20-Sep-2001)
root@pandora:~# e2fsck.static -cy /dev/hd0s2
< checks for bad blocks... No error messages, cut for readability >
Pass 1: Checking inodes, blocks, and sizes
Inode 8130 has illegal block(s). Clear? yes
Illegal block #-1 (2566813404) in inode 8130. CLEARED.
Illegal block #524 (4294967295) in inode 8130. CLEARED.
Illegal block #525 (4294967295) in inode 8130. CLEARED.
Illegal block #526 (4294967295) in inode 8130. CLEARED.
Illegal block #527 (4294967295) in inode 8130. CLEARED.
Illegal block #528 (4294967295) in inode 8130. CLEARED.
Illegal block #529 (4294967295) in inode 8130. CLEARED.
Illegal block #530 (4294967295) in inode 8130. CLEARED.
Illegal block #531 (4294967295) in inode 8130. CLEARED.
Illegal block #532 (4294967295) in inode 8130. CLEARED.
Illegal block #533 (4294967295) in inode 8130. CLEARED.
Too many illegal blocks in inode 8130.
Clear inode? yes
Restarting e2fsck from the beginning...
Note: the script died here. The illegal blocks were in
/var/cache/apt/pkgcache.bin, which was erased. It asked a couple other
questions but none of them seemed unusual for a filesystem that was
unmounted cleanly. I'll try to catch those errors next time.
Thanks,
Erik
--
To UNSUBSCRIBE, email to debian-hurd-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: