bad file descriptor

bad file descriptor

[shantanu]

Hello all,
      i am facing a problem on my Red Hat Linux 6.2 machine. When i
boot in my Linux box it boot properly till it reaches the stage
where it says "Press I for interactive setup"
>From there it starts giving me errors like this : -
Mounting proc file system dup2 : Bad File Descriptor      [FAILED]
Configuring kernel parameters dup2 : Bad File Descriptor      [FAILED]
Loading default keymap/etc/rc.d/rc.sysinit : /dev/null : read only
file system
Activating swap partition dup2 : Bad File Descriptor      [FAILED]
Seting hostname localhost.localdomain : Bad File Descriptor      [FAILED]
Checking root filesystem : Bad File Descriptor      [FAILED]

An error occured during file system check
For maintance mode give password [ctrl-d for normal setup]


when I give root password i can log in as single user and it gives
this message the moment I log in:

bash: /dev/null :Read only file system
kcd : cannot create file /root/.kcd.newdir
Broken pipe.

When i press ctrl-D for normal login the machine reboots.
I tried running fsck, e2fsck, checked for bad blocks and made force
checking too. still the problem is not solved.
This system was running perfectly for 6-7 months.
Please help.
thanks in advance and waiting for the reply.
-- 
Best regards,
 shantanu                          mailto:shantanu@mail.vu

Bad File descriptor

[Josh Konkol]

I'm running Suse8.0 with a 10 Gb ext3 root partition.  I'm having problems 
accessing my modem using sendpage.  The reason I'm posting to this group is 
I don't think this is a modem problem, I'm afraid it's a file system 
corruption problem.

Whenever I try to access the modem I get the following error in 
/var/log/messages:

Jun  9 09:40:14 nagios sendpage[5423]: Modem 'sportster': could not start 
Device::Serial port: Bad file descriptor

Can anyone confirm or deny this is a file system problem, or better yet do 
any of you Linux Guru's out there have any suggestions on how to fix this 
problem ?

TIA

Josh

Re: Bad File descriptor

[Bryan Henderson]

>...I'm afraid it's a file system corruption problem.
>
>Whenever I try to access the modem I get the following error in
>/var/log/messages:
>
>Jun  9 09:40:14 nagios sendpage[5423]: Modem 'sportster': could not start
>Device::Serial port: Bad file descriptor
>
>Can anyone confirm or deny this is a file system problem...

"Bad file descriptor" is unlikely to be a filesystem corruption problem per
se.  It's used for a variety of program errors that are specific to a
particular file descriptor.  E.g. no such file descriptor, file descriptor
is defined for reading and you're trying to write, file descriptor is for
the wrong type of file for the attempted operation.

Sadly, 'sendpage' is being rather terse with its error information --
there's no indication of what file it is trying to use.  Still, if you
could figure out what device special file name it associates with the modem
'Sportster', you could look at it with 'ls' and ensure that it looks like a
serial port device special file and try to use it with some simpler program
such as 'minicom' to isolate the problem.