* New dpkg panic.
@ 2004-12-06 15:31 mjt
2004-12-06 23:23 ` mjt
0 siblings, 1 reply; 2+ messages in thread
From: mjt @ 2004-12-06 15:31 UTC (permalink / raw)
To: reiserfs-list
Hello
How ironic; dpkg broke again..
The kernel in question is 2.6.9, with reiser4-for-2.6.9-2:
I noticed it first when my kernel, basically -cko3 with reiser4 replaced
with the new version, hung when I tried to install iconbar of enlightenment
on my Debian box, with x.org taken from Ubuntu.
It hung on trying to get the list of files for xorg-common, and with
debugging it panicked.
I did an mv on the file and tried to reinstall xorg-common, but it didn't
help. It had a file called xorg-common.list-new which I tried to open
with less but that process died as well. (Uninterruptible Sleep D+)
I have the logs here:
http://mjt.nysv.org/reiser/2004.12.06.forensics/
In the first file I had renamed the list file and cat on that triggered
the panic, after which I rebooted just fine.
In the second file I did dpkg -i three times (my comments are there,
and I didn't write the entire file name of xorg-common)
The third file is me fooling around and addiong comments to the netconsole
output as I go along until the system panicked and needed a power-button
boot.
What I'm puzzled about is why this comes for different programs?
Is my physical fs on the disk broken?
I'd appreciate a prompt answer, so I can fsck my computer as fast
as possible if that's needed...
Spatsibo and thanks!
--
mjt
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: New dpkg panic.
2004-12-06 15:31 New dpkg panic mjt
@ 2004-12-06 23:23 ` mjt
0 siblings, 0 replies; 2+ messages in thread
From: mjt @ 2004-12-06 23:23 UTC (permalink / raw)
To: reiserfs-list
On Mon, Dec 06, 2004 at 05:31:16PM +0200, Markus Törnqvist wrote:
>
>I'd appreciate a prompt answer, so I can fsck my computer as fast
>as possible if that's needed...
Figured the Namesys guys weren't available so I took a metadata
pack and did an fsck and the fs was corrupted.
I can't really see why; but in light of this new information, is it
possible the panics were caused by a broken fs?
I uploaded the metadata and the fsck log at the aforementioned URL.
Hope this is worth anything to anyone; I'm just glad it works..
PS.
Is there a known reason which might cause such corruptions?
I am pretty sure I haven't had to do any unclean shutdowns, but I
probably wouldn't remember if I had, if there were no immediate effects :)
But those should be pretty well survived, yes?
Well, thanks anyway :)
--
mjt
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-12-06 23:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-06 15:31 New dpkg panic mjt
2004-12-06 23:23 ` mjt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.