Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 May 1997 19:15:25 +0000
From:      "Riley J. McIntire" <chaos@mail.tgci.com>
To:        questions@FreeBSD.ORG
Subject:   (Fwd) (Fwd) File descriptors-do I have Bad Breath?
Message-ID:  <199705130243.TAA00297@train.tgci.com>

next in thread | raw e-mail | index | archive | help
Ok, I know when I'm beat!  Must be the way I comb my hair!

------- Forwarded Message Follows -------
From:          "Riley J. McIntire" <chaos@mail.tgci.com>
To:            freebsd-fs@FreeBSD.ORG
Date:          Sun, 11 May 1997 12:17:16 +0000
Subject:       (Fwd) File descriptors-do I have Bad Breath?
Reply-to:      chaos@tgci.com
Priority:      normal

Apologies if this is off-topic for freebsd-fs, but I either have very 
bad breath or am asking silly questions that don't deserve to be 
answered on Questions.

Could someone take a look at my questions and at least tell me which 
manual RTFM refers to?  :)

------- Forwarded Message Follows -------
From:          Self <chaos>
To:            questions@FreeBSD.ORG
Subject:       File descriptors
Reply-to:      chaos@tgci.com
Date:          Sat, 10 May 1997 13:27:28

I'm getting some bad file descriptor errors that prevented me from 
compiling a new kernal (I'm new...), and got some help here about 
that. 

But I'm not clear about what causes bad file descriptors or even 
what they are/do.

I've searched  the docs, man hier, man fd and am still not clear.  Do 
they indicate the state a file is in?  Open, writable, locked?  What 
constitutes a bad one?  Is it caused by bad hardware?  Disks?  
Controllers?

I'm had stuff like this on more that one occasion:

find: /usr/include/machine: Bad file descriptor
find: /usr/src/gnu/usr.bin/cc/cc_int/loop.c: Bad file descriptor
find: /usr/src/gnu/usr.bin/cc/cc_int/obstack.c: Bad file descriptor
etc

Last time I had to use clri and some other stuff to fix it.  fsck 
doesn't take care of it.

I am going to replace the IDE 1.2GB Maxtor with a Seagate scsi for 
this low volume webserver( and move it from 2.1.7 to 2.2.1--a good 
idea???). 

Will this fix the cause?  Is a bad disk causing this?  I haven't done 
a low-level format, but plan on it later.  Should/will this show up 
anything?

Could someone explain or point me to some documentation on this?

Ciao,

Riley





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705130243.TAA00297>