[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#25355: marked as done (corrupted fs after upgrade)



Your message dated Tue, 11 May 1999 07:15:52 -0700
with message-id <v04204e02b35dbedd995a@[206.163.71.146]>
and subject line Fixed or no longer applicable.
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(administrator, Debian bugs database)

Received: (at submit) by bugs.debian.org; 3 Aug 1998 16:03:40 +0000
Received: (qmail 16682 invoked from network); 3 Aug 1998 16:03:39 -0000
Received: from pink.ics.muni.cz (root@147.251.2.32)
  by debian.novare.net with SMTP; 3 Aug 1998 16:03:39 -0000
Received: from pink.ics.muni.cz (jara@localhost [127.0.0.1])
	by pink.ics.muni.cz (8.8.8/8.8.8/Debian/GNU) with ESMTP id SAA00510
	for <submit@bugs.debian.org>; Mon, 3 Aug 1998 18:03:35 +0200
Message-Id: <199808031603.SAA00510@pink.ics.muni.cz>
X-Mailer: exmh version 2.0.2 2/24/98 (debian) 
To: submit@bugs.debian.org
Subject: corrupted fs after upgrade
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 03 Aug 1998 18:03:35 +0200
From: Jaroslav Mechacek <jara@pink.ics.muni.cz>


Package: libc6


I had serious problems when upgrading Debian. After upgrade of about
10 - 20 packages, the root file system was always damaged.

I did some tests and found this:


dpkg -i libc6_2.0.7t-1.deb
shutdown -r +0
fsck -f /dev/hda1

produced 

Parallelizing fsck version 1.10 (24-Apr-97)
e2fsck 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 22755 has zero dtime.  Fix<y>? yes

Deleted inode 66002 has zero dtime.  Fix<y>? yes

Deleted inode 66003 has zero dtime.  Fix<y>? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Fix summary information<y>?

Block bitmap differences: -91702 -91703 -91704 -91705 -91706 -91707 -91708 
-91709 -91710 -91711 -9171
2 -91713 -266327 -266328 -266329 -266330 -266331 -266332 -266333

.
.
.

67103 -267104 -267105 -267106 -267107 -267108 -267109 -267110 -267111 -267112 
-267113 -267114 -267115
 -267116 -267117 -267118 -267119 -267120 -267121 -267122 -267123 -267124 
-267125 -267126 -267127 -267
128.  FIXED
Free blocks count wrong for group 11 (5070, counted=5082).  FIXED
Free blocks count wrong for group 32 (1896, counted=2698).  FIXED
Free blocks count wrong (395258, counted=396072).  FIXED
Inode bitmap differences: -22755 -66002 -66003.  FIXED
Free inodes count wrong for group #11 (1729, counted=1730).  FIXED
Free inodes count wrong for group #32 (1830, counted=1832).  FIXED
Free inodes count wrong (216885, counted=216888).  FIXED

/dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****


I tried  "telinit u" 
(http://www.debian.org/Lists-Archives/debian-user-9807/msg03265.html)
after dpkg -i ....
and everything was OK. No file system damage.


I'd like to note, that a week or two ago, a sequence of updates and reboots 
caused
a total disaster on my root partition. 



----------------

Debian  2.0 ,    kernel 2.0.35





Reply to: