Error Bad File Descriptor
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About error bad file descriptor utorrent Us Learn more about Stack Overflow the company Business Learn more about hiring
Bad File Descriptor Apr Socket Accept
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join
Bad File Descriptor Error In C
the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Bad file descriptor up vote
Bad File Descriptor Python
11 down vote favorite 1 I'm learning about file descriptors and I wrote this code: #include
Software Troubleshooting and Assistance Applications "VLC can't open the file, bad file descriptor, unable to read MRL" Custom Search Join the PC bad file descriptor mac homebuilding revolution! Read the all-new, FREE 200-page online guide: How to bad file descriptor perl Build Your Own PC! NOTE: Using robot software to mass-download the site degrades the server and is bad file descriptor bash prohibited. See here for more. Find The PC Guide helpful? Please consider a donation to The PC Guide Tip Jar. Visa/MC/Paypal accepted. If this is your http://stackoverflow.com/questions/6245477/bad-file-descriptor first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: "VLC can't open the file, http://www.pcguide.com/vb/showthread.php?88664-quot-VLC-can-t-open-the-file-bad-file-descriptor-unable-to-read-MRL-quot bad file descriptor, unable to read MRL" Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… 06-29-2013,11:42 PM #1 VLC_noob View Profile View Forum Posts View Blog Entries View Articles New Member - Welcome! Join Date Jun 2013 Posts 1 "VLC can't open the file, bad file descriptor, unable to read MRL" Hello all! This is my first ever post on this forum, as you can probably tell. So far, this forum has been extremely easy to use and well polished. Anyway, my issue! I have a VLC playlist that I have been building up for the past year or so; it has over 200 songs. In the past 2 months though, I have been unable to open it. Here is the error log for one of my songs: File reading failed: VLC could not open the file "C:\Users\Nino\Desktop\Drifting Soundtracks\Alex Clare - Too Close (OFFICIAL VIDEO).mp4". (Bad file descriptor) Your input can't be opened: VLC is unable to open the MRL 'file:///C:/Users/Nino/Desktop/Drifting%20Soundtracks/Alex%20Clare%20-%20Too%20Close%20%28OFFICIAL%20VIDEO%29.mp4'. Check the log for details. I
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us http://unix.stackexchange.com/questions/115467/getting-bad-file-descriptor-error-during-tar Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it http://www.justskins.com/forums/dup-2-bad-file-143994.html works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Getting “Bad file descriptor” error during tar up vote 1 down vote favorite I'm trying to tar a dir with this command "tar bad file -cpSWf myfile.tar workdir; gzip myfile.tar", but I get this error for some of the files in workdir dir. tar: my/sub/dir/file1.oa: Cannot seek to 1536: Bad file descriptor I run the same command on other dir and there's no such error. Is it because the .oa files are corrupted, or the disk is failing? Is this a common issue when using tar? Is there any way to repair this error? linux tar share|improve this question asked Feb 17 '14 at 2:53 user11496 1641618 That's probably the detection bad file descriptor of sparseness that causes it. –Stéphane Chazelas Feb 17 '14 at 7:19 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted Questions Is it because the .oa files are corrupted, or the disk is failing? Is this a common issue when using tar? Is there any way to repair this error? It isn't really relevant whether this issue is typical or not (I've not encountered it before), I'd start by attempting to tar up a single file and see if can't isolate the issue a bit more, and also repeat it. $ tar -cpSWf somefile.tar my/sub/dir/file1.oa Also as an aside, you can save yourself a step and tar and compress all at once: $ tar zcpSWf somefile.tar.gz ... I would also look to take out the SW switches temporarily to see if that has any impact on your ability to tar these problematic files too. If these errors are a warning that there are bad sectors on the HDD you might need to run an fsck or use a tool such as HDAT2 to attempt to repair any damaged sectors. This repair work may still leave the .oa file in a corrupted state, however. share|improve this answer answered Feb 17 '14 at 3:22 slm♦ 165k40302472 Thanks slm. If I remove "SW", there is no error. I also find that by copying the workdir to another partition on the disk and run tar with the same "-cpSWf" option, the command works without any error. –user11496 Feb 18 '14 at 7:33 add a comme
Bad File Descriptor...Whuzzat mean? - Linux Setup, Configuration & Administration I'm running Red Hat 7.2 (I think, kernel 2.4.7-10 according to uname -a) on my home computer. I had trouble deleting a cd.iso image on my last good boot. I shut it down normally this morning. This afternoon when I tried to reboot it instead of rebooting I got a bunch of error messages ending with dup 2: Bad File Descriptor. I then was dropped into a repair mode where I had to enter the root password, or Cntl D to continue. I entered the root password, did an fsck (which didn't work). When I exited the machine attempted to ... Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode September 12th,11:26 PM #1 Dup 2: Bad File Descriptor...Whuzzat mean? I'm running Red Hat 7.2 (I think, kernel 2.4.7-10 according to uname -a) on my home computer. I had trouble deleting a cd.iso image on my last good boot. I shut it down normally this morning. This afternoon when I tried to reboot it instead of rebooting I got a bunch of error messages ending with dup 2: Bad File Descriptor. I then was dropped into a repair mode where I had to enter the root password, or Cntl D to continue. I entered the root password, did an fsck (which didn't work). When I exited the machine attempted to reboot, whereupon I started the whole thing over again. Does anyone know what this means and what I should do about it? If I haven't included pertinent information I can look again once I get home. Any help would be appreciated. Mike Michael Guest September 13th,01:59 AM #2 Re: Dup 2: Bad File Descriptor...Whuzzat mean? Thanks for the quick answer. I'll give this a try. Mike Mauriat wrote: > [url]http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=9358n4%243bl%241%40nnrp1.deja.com[/url] > > -- > > Mauriat > ---------------------------- > Remove 'NOSPAM' to email me. Michael Guest September 13th,02:48 AM #3 Re: Dup 2: Bad File Descriptor...Whuzzat mean? Michael wrote: > I'm running Red Hat 7.2 (I think, kernel 2.4.7-10 according to uname -a) > on my home computer. I had trouble deleting a cd.iso image on my last > good boot. I shut it down normally this morning. This afternoon when I > tried to reboot it instead of rebooting I got a bunch of error messages > ending with dup 2: Bad File Descriptor. I then was dropped into a repair > mode where I had to enter the root password, or Cntl D to continue. I > entered the root password, did an fsck (which didn't work). When I > exited the machine attempted to reboot, whereupon I started the whole > thing over again. Does