>> On 25-Nov-98 h-to-he wrote:
>> > Hi all,
>> > When I fsck or e2fsck -c my h/d, there's message :
>> > " deleted inode 45344, has zero dtime , Fix?"
>> > "block bitmap differences : -2608 -2609"
>> > "free block count wrong" "Inode bitmap difference: -45344 fixed,..etc
>> > And then after that, for the second time , I repeat fsck and I had the
same
>> > messages.
>> >
>> > Could anyone explain to me,..:
>> > 1. what is "has zero dtime"? My h/d is new, does my h/d have bad
sector?
>> > 2. Is there utility in linux like "surface scan" (in Winblows) for
checking
>> > "bad sector"?
>
>zero dtime means that the file was not closed properly, possable causes,
>computer shutdown in the wrong manner, power failure maybe, or someone hit
>the reset button.
>
>>
>> You can check for bad blocks on your hard disk using the appropriately
named
>> "badblocks" utility. It features a write-read test, but doing such a test
will
>> destroy all content on the disk/partition.
>
>h-to-be says he is using "e2fsck -c" which will run "badblocks"
automaticly,
>what h-to-he must do is use "e2fsck -p" which will tell e2fsck to repair
the
>filesystem if needed.
>
>e2fsck runs in interactive mode as default.
>
>Another fine thing to know when using ANY program which plays around with
>your disk and we HAVE not read the manual page is that some options WILL
>erase data without even asking you or in some extream cases telling you,
>one such option is the "-w" with badblocks.
>
>Now i would imagen e2fsck -c -p -L blocks.file would check for badblaocks
>write found badblocks addresses to the file blocks.file and do any repairs
>without asking. Normaly i would only use the -p option myself.
>
>man e2fsck
>man fsck
>man badblocks
>
>>
>> I'm sorry I can't help you with the error. Perhapes someone with more
>> experience debugging ext2 file system could help.
>
>Judging by the degree of error messages reported by e2fsck i would
definatly
>say, h-to-be simply turned of his coumputer without shuting down his system
>first.
>
No...of course ..I "shutdown -h now" before I turn off my comp or "reboot"
What I mean that when I finish e2fsck -c or fsck...then I reboot the machine
again ..there is error message (same erorr)
