Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Oct 2005 09:06:54 -0000
From:      "John" <micp07@dsl.pipex.com>
To:        <freebsd-questions@freebsd.org>
Subject:   RE: UNEXPECTED INCONSISTENCY - fsck
Message-ID:  <000001c5dd31$46bcc700$0b00000a@Discovery>
In-Reply-To: <20051029211255.GB13247@math.jussieu.fr>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
>>  
>> There was recently a power outage in the area, which lasted longer 
>> than the UPS did.

...

>> ** Phase 4 - Check Reference Counts
>> BAD/DUP FILE I=3219136 OWNER=13273856 MODE=103210
>> SIZE=57005967061714584 MTIME=Jun  3 16:08 1970 CLEAR? [yn] yes
>> 
>> pid 22 (fsck), uid 0: exited on signal 11 Segmentation fault #
>
>And what's happend if you reboot and do this again ?

This happens every time I reboot, same messages, if I just do a fsck (no -y)
and answer no to this Clear? question, I get a second, similar  BAD/DUP FILE
I= 3219137 ...

A yes this time results in the Segmentation fault again, a no tells me the
file system is still dirty, and to run fsck again.
I suspect that the drive itself is now damaged.

>> It is FreeBSD 3.4, 2 * 17GB HITACHI SCSI Drives and 128MB RAM.
>
>Woouuahh....that's old ;-))

I know, but time and resources have prevented an update so far (not to
mention my even more out of date knowledge), I resisted the urge to update
until I could do things properly. 

>Regards.
>--
>Albert SHIH
>Universite de Paris 7 (Denis DIDEROT)
>U.F.R. de Mathematiques.
>Heure local/Local time:
>Sat Oct 29 23:11:05 CEST 2005


Unfortunately, I was not involved with the initial construction and
configuration of this system, it just falls to me to get it working again.
Looks like it may now be time to do that upgrade. 

John






Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000001c5dd31$46bcc700$0b00000a>