Date: Wed, 24 Dec 1997 14:52:21 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: John Frader <nat@mylanders.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Bad file descriptor? Message-ID: <Pine.BSF.3.96.971224145033.10003O-100000@localhost> In-Reply-To: <Pine.BSF.3.95q.971223105421.4634B-100000@mylanders.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 23 Dec 1997, John Frader wrote: > Thanks for the info. > > What would have caused it to become corrupted? Disk or system crash. > On Mon, 22 Dec 1997, Doug White wrote: > > > On Mon, 22 Dec 1997, John Frader wrote: > > > > > Below is what I started getting in the system security messages. > > > Could anyone tell me what this means? If I do a ls in /dev I don't see ch0 > > > but if I do a ls -l, I get the same thing /dev/ch0: Bad file descriptor > > > > > > checking setuid files and devices: > > > find: /dev/ch0: Bad file descriptor > > > > Your /dev/ch0 file is corrupted. If you don't use the SCSI tape changer, > > you can simply remove the file. If you do, then remove /dev/ch0 then run > > `/dev/MAKEDEV ch0'. Since you can't rm it (from your other msg), you may have to use ls -i to find the file inode and clri to manually remove it, then run fsck to kick it out to /lost+found. That is a tricky and potentially dangerous procedure however. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971224145033.10003O-100000>