From nobody@FreeBSD.ORG Mon Apr 19 06:21:47 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id E5E9E14A09; Mon, 19 Apr 1999 06:21:46 -0700 (PDT)
Message-Id: <19990419132146.E5E9E14A09@hub.freebsd.org>
Date: Mon, 19 Apr 1999 06:21:46 -0700 (PDT)
From: billik@sun.uniag.sk
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: Power fail versus Fsck changed my life.
X-Send-Pr-Version: www-1.0

>Number:         11216
>Category:       misc
>Synopsis:       Power fail versus Fsck changed my life.
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 19 06:20:01 PDT 1999
>Closed-Date:    Fri Nov 12 20:17:36 PST 1999
>Last-Modified:  Fri Nov 12 20:18:19 PST 1999
>Originator:     steve
>Release:        3.1-STABLE
>Organization:
>Environment:
FreeBSD s2fvs.uniag.sk 3.1-STABLE FreeBSD 3.1-STABLE #2: Fri Apr  9 12:21:44 GMT 1999     root@s2fvs.uniag.sk:/usr/src/sys/compile/steve  i386

>Description:
After some power/cable fail, i could not boot my machine.
I booted from 3.1 CDROM, ran fixit.
I runned fsck -y /dev/wd0s3* where is my disc and partition.
Well, boot, ...

missing files:
/etc/defaults/rc.conf

missing/directories:
/root/bin

problem area was /root

!!! THERE IS A COPY OF .. IS .^N  (probably 'dot'+'\014')
HOW CAN I FIX IT?

===== example

 15:16  (0) /root ls -lia
total 88
18860 drwxr-xr-x  12 root  wheel   1024 Apr 19 14:52 .
    2 drwxr-xr-x  20 root  wheel    512 Apr 19 12:22 .?
...
 15:16  (0) /root ls -lia .?/root
total 88
18860 drwxr-xr-x  12 root  wheel   1024 Apr 19 14:52 .
    2 drwxr-xr-x  20 root  wheel    512 Apr 19 12:22 .?

=== example

filnamees were strange UpPerCASeD, directory /root/bin was missing,
but I've found it in /lost+found.
Contents of some files was changed!
instead #!/usr/bin/perl was something like #?psr/bin?pe?l 
...

Note: Opened files were not hurted (I think). 

>How-To-Repeat:
Cut hdd cable.
I had this problem before, but conseqences wer not so large like this.
>Fix:
backup files or die.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: billf 
State-Changed-When: Fri Nov 12 20:17:36 PST 1999 
State-Changed-Why:  
This 'critical' PR doesn't make any sense and lacks any point. 
The submitter is encouraged not to submit PRs while under  
the influence of controlled substanced. 

On a side note, I don't know how many operating systems are 
out there that can recorver from ripping the hard drive cable 
while a drive is operational and transfering. 
>Unformatted:
