That's me again. Some days after I installed LM8.1 I started
experiencing sme problems with my filesystem. Let me explain.
Basically I cannot access some directories/files... it happens
mostly with Eterm configuration files, and since I installed Eterm
0-9.1, it might have something to do with it... though I can't see how.
I would use tune2fs to force a check in the next reboot, and I
would get the following :
****************************
Nov 13 11:44:46 pinguim fsck: /dev/hdc5 was not cleanly unmounted, check
forced.
Nov 13 11:44:48 pinguim fsck: /dev/hdc5:
Nov 13 11:44:48 pinguim fsck: Inode 7603, i_blocks is 2096, should be
2056. FIXED.
Nov 13 11:44:51 pinguim fsck: /dev/hdc5:
Nov 13 11:44:51 pinguim fsck: Inode 39769, i_blocks is 64, should be 8.
FIXED.
Nov 13 11:44:54 pinguim fsck: /dev/hdc5:
Nov 13 11:44:54 pinguim fsck: Deleted inode 71974 has zero dtime. FIXED.
Nov 13 11:45:27 pinguim fsck: /dev/hdc5: Duplicate or bad block in use!
Nov 13 11:45:27 pinguim fsck: /dev/hdc5: Duplicate blocks found...
invoking duplicate block passes.
Nov 13 11:45:27 pinguim fsck: Pass 1B: Rescan for duplicate/bad blocks
Nov 13 11:45:27 pinguim fsck: /dev/hdc5:
Nov 13 11:45:27 pinguim fsck: Duplicate/bad block(s) in inode
263738:/dev/hdc5: 545471/dev/hdc5:
Nov 13 11:45:27 pinguim fsck: /dev/hdc5:
Nov 13 11:45:27 pinguim fsck: Pass 1C: Scan directories for inodes with
dup blocks.
Nov 13 11:46:42 pinguim fsck: /dev/hdc5:
Nov 13 11:46:42 pinguim fsck: Pass 1D: Reconciling duplicate blocks
Nov 13 11:46:42 pinguim fsck: /dev/hdc5:
Nov 13 11:46:43 pinguim fsck: (There are 1 inodes containing
duplicate/bad blocks.)
Nov 13 11:46:43 pinguim fsck: /dev/hdc5: File
/usr/src/linux-2.4.8/drivers/net/3c515.c (inode #263738, mod time Tue
Jul 17 22:53:55 2001)
Nov 13 11:46:43 pinguim fsck: has 1 duplicate block(s), shared with 0
file(s):
Nov 13 11:46:43 pinguim fsck: /dev/hdc5: Duplicated blocks already
reassigned or cloned.
Nov 13 11:46:43 pinguim fsck: /dev/hdc5:
Nov 13 11:46:43 pinguim fsck: /lost+found not found. CREATED.
Nov 13 11:46:43 pinguim fsck: /dev/hdc5: 146454/305824 files (0.2%
non-contiguous), 517775/610462 blocks
Nov 13 14:27:06 pinguim fsck: /dev/hdc5: clean, 147153/305824 files,
519491/610462 blocks
**************************
Nov 14 17:38:32 pinguim fsck: was not cleanly unmounted, check forced.
Nov 14 17:38:37 pinguim fsck: /dev/hdc5:
Nov 14 17:38:37 pinguim fsck: Inode 39769, i_blocks is 64, should be 8.
FIXED.
Nov 14 17:39:11 pinguim fsck: /dev/hdc5: Duplicate or bad block in use!
Nov 14 17:39:11 pinguim fsck: /dev/hdc5: Duplicate blocks found...
invoking duplicate block passes.
Nov 14 17:39:11 pinguim fsck: Pass 1B: Rescan for duplicate/bad blocks
Nov 14 17:39:12 pinguim fsck: /dev/hdc5: Duplicate/bad block(s) in inode
263738:/dev/hdc5: 545471/dev/hdc5:
Nov 14 17:39:12 pinguim fsck: /dev/hdc5:
Nov 14 17:39:12 pinguim fsck: Pass 1C: Scan directories for inodes with
dup blocks.
Nov 14 17:39:57 pinguim fsck: /dev/hdc5: Pass 1D: Reconciling duplicate
blocks
Nov 14 17:39:59 pinguim fsck: /dev/hdc5: (There are 1 inodes containing
duplicate/bad blocks.)
Nov 14 17:39:59 pinguim fsck: /dev/hdc5: File
/usr/src/linux-2.4.8/drivers/net/3c515.c (inode #263738, mod time Tue
Jul 17 22:53:55 2001)
Nov 14 17:39:59 pinguim fsck: has 1 duplicate block(s), shared with 0
file(s):
Nov 14 17:39:59 pinguim fsck: /dev/hdc5: Duplicated blocks already
reassigned or cloned.
Nov 14 17:40:00 pinguim fsck: /dev/hdc5: 147873/305824 files (0.2%
non-contiguous), 523176/610462 blocks
********************************
Note that I got the same error twice, refering to inode 263738... in
fact it happened more than two times. After the fsck, everything would
ran fine. I suspect that my fs wasn't being unmounted the right way,
since it looked like it would shutdown too quickly before these things
ocurred.
Well- I was already interested in switching to ext3, and I thought it
would help me to solve that problem. I converted the fs to ext3, and
added a ramdisk to load the ext3 module at boot... which brings in
another oddity, I didnt manage to re-compile the modules of Mandrake
kernel. But I guess I should write a third e-mail to deal with that...
But the problem also happened with ext3. when I forced the check,
everything would work fine, but the check gave me no error msgs.
It might be some hardware problem; I have an A7V133 Asus board, so it
might be a symptom of one the infamous VIA bugs. But these things never
happened with LM8.0. I also expected fsck to correct the problem the
first time it appeared...
Any help on how to correct this will be greatly apprecciated...
Please should someone reply to this also include a cc to my e-mail, as
well as the list's.
Jeferson Lopes Zacco aka wooky
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
