Re: bad file descriptor when mounting an ext2fs.

2008-06-10 Thread Gonzalo Nemmi
On Tuesday 10 June 2008 07:37:56 anhnmncb wrote:
 Hi, list,
 Recently, I encounter a very annoying issue, when I try to
 mount an ext2fs filesystem in laptop disk, after mounted it without
 any errors, I can't access it, ls /mnt/da0s3 says bad file
 descriptor. In that disk, also has msdos and ufs fs, but they
 work well.
 I tried reformat whole disk, and fsck.ext2 -f that ext2fs
 slice, nothing works at all.
 But my a local disk has ext2fs too, it can be mounted and used
 well, don't know why?

The same thing happens in here too ..
The same question It has also been posted in this list on Friday 09 May 2008 
14:40:06 by Isaac Mushinsky and me, but nobody answered ...
On FreeBSD 7.0 i386 and Linux i386 in here, I get either get a 'Bad file 
descriptor' for directory /linux' or 

$ mount -t etx2fs /dev/ad0s7 /linux
$ ls /linux 
No such file or directory

I've got all of my music, pdfs, pictures and on a ext3 and I only need to 
mount it in order to get FreeBSD's Amarok access to my music collection.

If somebody has solution or a pointer to a solution or whatever may help on 
this matter, I would greatly appreciate his/hers reply :)

Blessings
-- 
Gonzalo Nemmi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: bad file descriptor

2003-06-19 Thread Sunil Sunder Raj
Hi,
1) First get the inode no of the file
ls -li #pico29506#
2) find . -inum inode no -delete

Regards
SSR

From: Jaime [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: bad file descriptor
Date: Tue, 17 Jun 2003 09:06:10 -0400 (EDT)
Can anyone explain this?  It looks like I can't delete a given
file.  This file has been causing weird errors with just about everything,
including tar, rm, ls -l, etc.  It resides on a vinum RAID-5 array, which
is the only strange thing I can think of about it.
zeus# ls
#pico29506# .login  .shrc   
cdtashirt.jpg
.addressbook.login_conf 
.spamassassin   cdtashirtstitch.jpg
.addressbook.lu .mail_aliases   December 
2002 Newsletter.docs   dead.letter
.aspell.en.prepl.mailrc Documents   
mail
.aspell.en.pws  .pinerc 
Lawrence.JPGmbox
.aspell.english.prepl   .profileOctober 
2002 Newsletter.doc public_html
.aspell.english.pws .qmail.backup.from.cyrusOctober 
2002 Newsletter.doc.
.cshrc  .rhosts acker
zeus# rm #pico29506#
rm: #pico29506#: Bad file descriptor
zeus# whoami
root

Thanks in advance,
Jaime
To affect the quality of the day, that is the highest of arts.
 - Henry David Thoreau, _Where_I_Live_
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]
_
Chill out. Win a Himalayan holiday! 
http://server1.msn.co.in/sp03/summerfun/index.asp

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: bad file descriptor

2003-06-17 Thread heikki soerum
On Tue, 17 Jun 2003 09:06:10 -0400 (EDT)
Jaime [EMAIL PROTECTED] wrote:
   Can anyone explain this?  It looks like I can't delete a given
 file.  This file has been causing weird errors with just about
 everything, including tar, rm, ls -l, etc.  It resides on a vinum
 RAID-5 array, which is the only strange thing I can think of about it.
 
 zeus# ls
 #pico29506# .login  .shrc 
  cdtashirt.jpg
 .addressbook.login_conf
 .spamassassin   cdtashirtstitch.jpg.addressbook.lu
 .mail_aliases   December 2002
 Newsletter.docs   dead.letter
 .aspell.en.prepl.mailrc
 Documents   mail.aspell.en.pws 
 .pinerc Lawrence.JPG   
 mbox.aspell.english.prepl   .profile   
 October 2002 Newsletter.doc public_html.aspell.english.pws
 .qmail.backup.from.cyrusOctober 2002 Newsletter.doc.
 .cshrc  .rhosts acker
 zeus# rm #pico29506#
 rm: #pico29506#: Bad file descriptor
 zeus# whoami
 root

# is usually an special character, I usually delete such files with
Midnight Commander (mc shell), another possibility might be to not use
 but rather use an \ backslash before every special character.
I'm not guaranteeing that it would work though. :/

Heikki S.


-- 
If people say that here and there someone has been taken away and
maltreated,
I can only reply: You can't make an omelette without breaking eggs.
-- Hermann Goering
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: bad file descriptor

2003-06-17 Thread Bill Moran
Jaime wrote:
Can anyone explain this?  It looks like I can't delete a given
file.  This file has been causing weird errors with just about everything,
including tar, rm, ls -l, etc.  It resides on a vinum RAID-5 array, which
is the only strange thing I can think of about it.
zeus# ls
#pico29506# .login  .shrc  
 cdtashirt.jpg
.addressbook.login_conf .spamassassin  
 cdtashirtstitch.jpg
.addressbook.lu .mail_aliases   December 2002 
Newsletter.docs   dead.letter
.aspell.en.prepl.mailrc Documents  
 mail
.aspell.en.pws  .pinerc Lawrence.JPG   
 mbox
.aspell.english.prepl   .profileOctober 2002 
Newsletter.doc public_html
.aspell.english.pws .qmail.backup.from.cyrusOctober 2002 
Newsletter.doc.
.cshrc  .rhosts acker
zeus# rm #pico29506#
rm: #pico29506#: Bad file descriptor
zeus# whoami
root
That looks like a recovery file from the pico editor.

It's unlikely, but possible that your system crashed during a pico
editing session and left this file behind with a broken file
descriptor.  If such is the case, fsck might be able to fix it.
Try unmounting the filesystem (or booting into single user mode
if you must) and running 'fsck -f'.  Once it's finished and you've
rebooted the system, see if you can then delete the file.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: bad file descriptor

2003-06-17 Thread Jaime
On Tue, 17 Jun 2003, heikki soerum wrote:
  zeus# rm #pico29506#
  rm: #pico29506#: Bad file descriptor
  zeus# whoami
  root

 # is usually an special character, I usually delete such files with
 Midnight Commander (mc shell), another possibility might be to not use
  but rather use an \ backslash before every special character.

I tried that first.  That didn't work, either.  :(

Jaime
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: bad file descriptor

2003-06-17 Thread Dan Nelson
In the last episode (Jun 17), Jaime said:
 On Tue, 17 Jun 2003, heikki soerum wrote:
   zeus# rm #pico29506#
   rm: #pico29506#: Bad file descriptor
   zeus# whoami
   root
 
  # is usually an special character, I usually delete such files with
  Midnight Commander (mc shell), another possibility might be to not use
   but rather use an \ backslash before every special character.
 
   I tried that first.  That didn't work, either.  :(

Bad file descriptor when trying to access a file usually means
filesystem corruption.  A fsck run should delete it, and if it doesn't
you can use the clri command to zap the inode (dismount the filesystem
first) then run fsck.

-- 
Dan Nelson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]