• 11

A PHP Error was encountered

Severity: Notice

Message: Undefined index: userid

Filename: views/question.php

Line Number: 191


File: /home/prodcxja/public_html/questions/application/views/question.php
Line: 191
Function: _error_handler

File: /home/prodcxja/public_html/questions/application/controllers/Questions.php
Line: 433
Function: view

File: /home/prodcxja/public_html/questions/index.php
Line: 315
Function: require_once

name Punditsdkoslkdosdkoskdo

open failed: EBUSY (Device or resource busy)

I have a strange error in my App.

In my app it is possible to download a zipFile, read the content as what it is and also delete it. Its doesn't matter what exactly it is.

Problem: Only on the Motorola Xoom (version 4.0.4) I can download the file, unzip it, I can read the data and I can delete everything. But if I try to Download the file again and while it unzip the file and copy the files to SD-Card it crashes with the error EBUSY (Device or resource busy).

  1. Why is it working only the first time?
  2. What means that error?
  3. Why i get this error only on the Xoom?

I can't find any solution for that. On all other devices it works fine, no errors or problems.


07-18 12:27:46.774: E/PrepareMagTask(10057): IOException
07-18 12:27:46.774: E/PrepareMagTask(10057): java.io.FileNotFoundException: /mnt/sdcard/Android/data/com.xxxxxx.android/files/content/23760/emag.db: open failed: EBUSY (Device or resource busy)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at libcore.io.IoBridge.open(IoBridge.java:406)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.io.FileOutputStream.<init>(FileOutputStream.java:88)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.io.FileOutputStream.<init>(FileOutputStream.java:73)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at com.xxxxx.android.util.io.ZipHelper.uncompressEntry(ZipHelper.java:35)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at com.xxxxx.android.task.PrepareMagTask.doInBackground(PrepareMagTask.java:271)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at com.xxxxx.android.task.PrepareMagTask.doInBackground(PrepareMagTask.java:1)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at android.os.AsyncTask$2.call(AsyncTask.java:264)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.util.concurrent.FutureTask.run(FutureTask.java:137)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at java.lang.Thread.run(Thread.java:856)
07-18 12:27:46.774: E/PrepareMagTask(10057): Caused by: libcore.io.ErrnoException: open failed: EBUSY (Device or resource busy)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at libcore.io.Posix.open(Native Method)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
07-18 12:27:46.774: E/PrepareMagTask(10057):    at libcore.io.IoBridge.open(IoBridge.java:390)
07-18 12:27:46.774: E/PrepareMagTask(10057):    ... 11 more

It crashes at line 35 in my ZipHelper class:

FileHelper.copy(zipFile.getInputStream(entry), new FileOutputStream(outputFile), modify);

getInputStream(entry) ... and I really dont know why?

Is there a method to wait for the device or recourse, when it is busy? This is happened every time I try to unzip the file, the app tries it 5 time (Downloading -> Unzip) and it crashes every time.

EDIT: We found out, its not only the Xoom. We also have the error with the Asus Transformer with the version 4.0.4

I have a big Answer!! The Problem comes from the Android System or/and the FAT32 system. I can not explain how the system gets the error, it has something to do with deleting files and the FAT32 System.

But the solution is really easy: Before you delete a Directory or File: rename it!

Code to rename:

final File to = new File(file.getAbsolutePath() + System.currentTimeMillis());

That's it, if you rename the folder or file before you delete it, there is no chance for the system to try to open an existing file again or an open file which you want to save again (or something like this).

  • 77
Reply Report
      • 1
    • @Mirko any ideas of a workaround when something gets deleted through another app? (ie. users that are deleting files from their system through a file manager app)
    • this solution is just to delete known files (of the app). If someone deletes files with a different app you cant do anything, just save files in the private disc space of your app
    • Combined with the answer from caopeng below, I've messed around with this and it looks like the sdcard process, owned by user media_rw, has a link to a deleted file which is locking everything up. Anyone have any better idea why this would happen than bad reboots / unexpected power loss in the middle of writing? Rename-before-delete sounds like a hack :(
      • 1
    • There is no reason, just to use the full path of this file, i think its also possible to use getPath(). No warranty :)

This issue may be cause by

  • two or more process reference the same file

  • file was deleted,but the reference not be killed

However,deleted it,only one reference was killed,or one or more process reference this file also

you can step by step:

before you delete the file you should

  • adb shell lsof | grep "com.xxxxxx.android"

The file you have been opened,and which process reference the file which you opened. also,this command ,show us the process id


  • adb shell ls -al /proc/%d/fd

Surprise waiting for you, O(?_?)O

good luck!

  • 6
Reply Report

It seems to be a lingering filesystem lock. I fixed it without touching my code, I think it was by unplugging my USB cable and re-plugging it in.

  • 2
Reply Report

I noticed this error in Sony Xperia when file in the directory not closed after writing some content in to it and I am trying to access(modify/delete) the directory.

Make sure to close the file properly. Make sure no program is accessing your files. Then you wont come across this error.

If you are unsure that any program might be accessing your directory, be sure to delete(/close) all the files in the directory before deleting the directory.

adb reboot is one option to close opened files. But that is not a good option to do so.

  • 0
Reply Report

I understand that this is an old issue, and was originally reported specific to a XOOM, but if the OP had an open FileOutputStream that was not properly closed, i.e. via a Finally block, then that is likely what is causing the resource to be held when attempting to reference it later... even if the physical file was actually deleted.

  • 0
Reply Report

The message rm: could not remove directory (code EBUSY), means that some app or process is using the directory.

For me, this usually means AndroidStudio, Webstorm, or another IDE is open. If you have an IDE open, closing it can free up the process to remove the folder. After closing, just run the removal again.

  • 0
Reply Report