Re. I always thought checking the partitions was a waste of time, but I must say that fsck did here a good job :
Code:
root@1[mnt]# fsck /dev/hda7
fsck 1.39-WIP (10-Dec-2005)
e2fsck 1.39-WIP (10-Dec-2005)
/var has been mounted 31 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'dhclient.pid' in /run (127489) has deleted/unused inode 127492. Clear<y>? yes
Entry 'crond.pid' in /run (127489) has deleted/unused inode 127496. Clear<y>? yes
Entry 'Xprt_0.pid' in /run (127489) has deleted/unused inode 127502. Clear<y>? yes
Entry 'cvpnd.pid' in /run (127489) has deleted/unused inode 127500. Clear<y>? yes
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -266240
Fix<y>? yes
Free blocks count wrong for group #8 (32260, counted=32261).
Fix<y>? yes
Free blocks count wrong (510398, counted=510399).
Fix<y>? yes
Free inodes count wrong for group #8 (15931, counted=15929).
Fix<y>? yes
Free inodes count wrong (362684, counted=362682).
Fix<y>? yes
/var: ***** FILE SYSTEM WAS MODIFIED *****
/var: 3846/366528 files (6.8% non-contiguous), 222558/732957 blocks
Now I don't expercience issue with "ghost files" anymore.
Quote:
Originally Posted by halvy
panics are *usually* caused by bad kernels, missing initrd (image file), or bad dev setups.
|
Yep. In fact I don't know what happend. Yesterday I worked as a normal user (not root) and did not perform any task such as adding a piece of hardware or modifying a config file. The next time I could not boot my comp: boot freeze while entering runlevel 2. I could boot as a single user, though. When I shut down the box, I got hundreds of error messages - which one cannot understand. Examples:
Code:
EIP is at do_page_fault+0xd6/0x6bf
eax: dfa40000 ebx:00000000 ecx:0000007b edx:ffffff7b esi:00030001
edi:0000000d ebp:0000000b esp: dfa417c8
ds: 007b es:007b ss:0008
Unable to handle kernel paging request at virtual address ffffffef
printing eip:
c0114fe6
*pde=00002067
*pte=00000000
Recursive die() failure, output suppressed
<0> Kernel panic - not syncing: Fatal exception in interrupt
Code:
inode hda2: 96697 at df6aa440: mode 120777, nlink 1, next 0
I rebooted, and rebooted, and rebooted - always the same problem. But after around ten reboots all worked.
That's mysterious for me. So far I found the kernel rock solid - never had a kernel panic. Then a problem occurs, though I did not change anything on my box. Then it disappeared... Strange...