From owner-freebsd-questions  Mon Nov 20 16:50:33 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA01719
          for questions-outgoing; Mon, 20 Nov 1995 16:50:33 -0800
Received: from bubba.tribe.com ([205.184.207.7])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA01713
          for <freebsd-questions@freebsd.org>; Mon, 20 Nov 1995 16:50:30 -0800
Received: (from archie@localhost) by bubba.tribe.com (8.6.12/8.6.12) id QAA00362; Mon, 20 Nov 1995 16:49:55 -0800
From: Archie Cobbs <archie@tribe.com>
Message-Id: <199511210049.QAA00362@bubba.tribe.com>
Subject: lost+found?
To: freebsd-questions@freebsd.org
Date: Mon, 20 Nov 1995 16:49:54 -0800 (PST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 3217      
Sender: owner-questions@freebsd.org
Precedence: bulk


Hello,

Running on 2.1.0-951104-SNAP, I have this equipment:

    bt0: Bt946C/ 0-PCI/EISA/VLB(32bit) bus
    bt0: reading board settings, busmastering, int=11
    bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs
    bt0: targ 0 sync rate=10.00MB/s(100ns), offset=08
    bt0: targ 6 sync rate=10.00MB/s(100ns), offset=08
    bt0: Using Strict Round robin scheme
    bt0 at 0x330 irq 11 on isa
    bt0 waiting for scsi devices to settle
    (bt0:0:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2
    sd0(bt0:0:0): Direct-Access 1042MB (2134305 512 byte sectors)
    (bt0:4:0): "CHINON CD-ROM CDS-535 Q20" type 5 removable SCSI 2
    cd0(bt0:4:0): CD-ROM 
    cd0(bt0:4:0): NOT READY asc:3a,0 Medium not present
    can't get the size
    (bt0:6:0): "QUANTUM MAVERICK 540S 0901" type 0 fixed SCSI 2
    sd1(bt0:6:0): Direct-Access 516MB (1057758 512 byte sectors)

Unfortunately, this happened when I tried to reboot:

    reboot: rebooted by root
    syslogd: exiting on signal 15
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 26008 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 24401 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 24403 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 2036 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 24401 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 26008 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 24399 failure
    /kernel: vnode_pager_input: I/O read error
    /kernel: vm_fault: pager input (probably hardware) error, PID 24402 failure
    /kernel: 
    /kernel: syncing disks... 11 11 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 giving up

As a result, on the next restart this happened (for lots of files):

    /dev/rsd0s1f: UNREF FILE I=8013  OWNER=1000 MODE=100664
    /dev/rsd0s1f: SIZE=119 MTIME=Nov 20 15:13 1995  (CLEARED)

As I understand it, this means there was a file found for which there
was no directory entry, and that file got sent into the void (please
correct me if I'm wrong). A couple of questions:

    1. Is there a known bug that might be causing the I/O read error,
       or is my hard disk dying on me? By the way, a similar thing
       happened on another machine (ASUS 486DX2/66-SP3G with onboard
       NCR 53c810 SCSI, Conner 1.0Gig disk) the other day (same O/S
       version).

    2. What ever happened to "lost+found"? Do I need to do anything
       special to create it (special inode number, etc)? How come it's
       not created by the normal install process?  Or is there another
       directory somewhere serving the same purpose?

Thanks,
-Archie
_______________________________________________________________________________
Archie L. Cobbs, archie@tribe.com  *  Tribe Computer Works http://www.tribe.com