Debian bug report logs - #510
system crashes and filesystem corruption with 0.93R3

Package: 0.93R3; Reported by: Bill Mitchell <mitchell@mdd.comm.mot.com>; 115 days old.

Message received at debian-bugs:

From mdd.comm.mot.com!mitchell Sat Feb 25 08:01:59 1995
Return-Path: <mitchell@mdd.comm.mot.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0riOwQ-00047vC; Sat, 25 Feb 95 08:01 PST
Received: from motgate.mot.com by pixar.com with SMTP id AA14838
  (5.65c/IDA-1.4.4 for <debian-bugs@pixar.com>); Sat, 25 Feb 1995 08:02:37 -0800
Received: from pobox.mot.com by motgate.mot.com with SMTP (5.67b/IDA-1.4.4/MOT-3.1 for <debian-bugs@pixar.com>)
          id AA18163; Sat, 25 Feb 1995 10:01:57 -0600
Received: from mdd.comm.mot.com (mdisea.mdd.comm.mot.com) by pobox.mot.com with SMTP (5.67b/IDA-1.4.4/MOT-3.1 for <debian-bugs@pixar.com>)
          id AA14018; Sat, 25 Feb 1995 10:01:55 -0600
Received: from bb29c.mdd.comm.mot.com by mdd.comm.mot.com (4.1/SMI-4.1)
	id AA18317; Sat, 25 Feb 95 08:01:54 PST
Received: by bb29c.mdd.comm.mot.com (4.1/SMI-4.1)
	id AA15369; Sat, 25 Feb 95 08:01:51 PST
Date: Sat, 25 Feb 1995 08:01:50 -0800 (PST)
From: Bill Mitchell <mitchell@mdd.comm.mot.com>
X-Sender: mitchell@bb29c
To: debian-bugs@pixar.com
Subject: system crashes and filesystem corruption with 0.93R3
Message-Id: <Pine.SUN.3.90.950225074348.15354A-100000@bb29c>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


PACKAGE:  0.93R3

I haven't localized this at all, but I've now seen it on two
separate systems having very different configurations, but both
systems running 0.93R3.

Yesterday, I reported that dpkg had removed libc and crippled
my system.  The crippled system was a fact.  The assignment of
responsibility to dpkg was an assumption, since I'd been working
with some of the less commonly used dpkg options trying to
install/update/configure/remove/etc. a bunch of packages which
included libc.  The effect of the crippled system was that
nothing would run, and I got complaints about not being able
to load shared libraries.  Shutdown wouldn't run, so I did
a reset-switch reboot and reinstalled teh system from scratch.

Last night, while trying to put together a less-2.78-1 package
on a different 0.93R3 system, I was getting wierd and inconsistant
build failures.  On getting back to it this morning, I got even
wierder failures, then this system stopped working with complaints
about not being able to load shared libraries.  I couldn't even run
shutdown, so I did a reset-switch reboot.  Suspecting filesystem
damage, I booted my maintenance partition and ran fsck on the 0.93R3 
partition from there.  "fsck -a ..." reported deleting several 
Inodes with zero link count, and setting dtime on one Inode with zero 
dtime, then said: "Duplicate or bad blocks in use", and "UNEXPECTED
INCONSISTANCY; RUN fsck MANUALLY."  These messages are repeated 
each time fsck is run manually.  This is with "Parallelizing
fsck version 0.5a (5-Apr-94)".

That's all I know.  I'll reload 0.93R3 from scratch now.

mitchell@mdd.comm.mot.com (Bill Mitchell)

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Bill Mitchell <mitchell@mdd.comm.mot.com>
Subject: Bug#510: Acknowledgement (was: system crashes and filesystem corruption with 0.93R3)
In-Reply-To: <Pine.SUN.3.90.950225074348.15354A-100000@bb29c>
References: <Pine.SUN.3.90.950225074348.15354A-100000@bb29c>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#510" or "Re: Bug#510" so that
we can identify it as relating to the same problem.

Please do not to reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent to debian-devel@pixar.com:

Subject: Bug#510: system crashes and filesystem corruption with 0.93R3
Reply-To: Bill Mitchell <mitchell@mdd.comm.mot.com>, debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: Bill Mitchell <mitchell@mdd.comm.mot.com>
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Sat, 25 Feb 1995 16:18:03 GMT
Resent-Message-ID: <debian-bugs-handler.510.022516031016089@pixar.com>
Date: Sat, 25 Feb 1995 08:01:50 -0800 (PST)
From: Bill Mitchell <mitchell@mdd.comm.mot.com>
To: debian-bugs@pixar.com
Message-Id: <Pine.SUN.3.90.950225074348.15354A-100000@bb29c>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

PACKAGE: 0.93R3

I haven't localized this at all, but I've now seen it on two
separate systems having very different configurations, but both
systems running 0.93R3.

Yesterday, I reported that dpkg had removed libc and crippled
my system.  The crippled system was a fact.  The assignment of
responsibility to dpkg was an assumption, since I'd been working
with some of the less commonly used dpkg options trying to
install/update/configure/remove/etc. a bunch of packages which
included libc.  The effect of the crippled system was that
nothing would run, and I got complaints about not being able
to load shared libraries.  Shutdown wouldn't run, so I did
a reset-switch reboot and reinstalled teh system from scratch.

Last night, while trying to put together a less-2.78-1 package
on a different 0.93R3 system, I was getting wierd and inconsistant
build failures.  On getting back to it this morning, I got even
wierder failures, then this system stopped working with complaints
about not being able to load shared libraries.  I couldn't even run
shutdown, so I did a reset-switch reboot.  Suspecting filesystem
damage, I booted my maintenance partition and ran fsck on the 0.93R3
partition from there.  "fsck -a ..." reported deleting several
Inodes with zero link count, and setting dtime on one Inode with zero
dtime, then said: "Duplicate or bad blocks in use", and "UNEXPECTED
INCONSISTANCY; RUN fsck MANUALLY."  These messages are repeated
each time fsck is run manually.  This is with "Parallelizing
fsck version 0.5a (5-Apr-94)".

That's all I know.  I'll reload 0.93R3 from scratch now.

mitchell@mdd.comm.mot.com (Bill Mitchell)

Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism

This page last modified 06:43:02 GMT Wed 21 Jun

Debian bug report logs - #510 system crashes and filesystem corruption with 0.93R3

Message received at debian-bugs:

Message sent:

Message sent to debian-devel@pixar.com:

Debian bug report logs - #510
system crashes and filesystem corruption with 0.93R3