This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.
The error codes of the file management subsystem include the following:
Error Message
Operation not permitted
Possible Causes
The caller does not have the permission to access the URI or path.
Solution
Check whether the caller cannot use the URI shared by another application. For details, see access control mechanisms of the system.
Check whether the permission is obtained by Picker. The permission obtained by Picker is temporary. For details, see System Pickers.
Check whether the URI is a concatenated path, which has no permission by default.
Error Message
No such file or directory
Possible Causes
The file or directory does not exist.
Solution
Check whether the file directory exists.
Error Message
No such process
Possible Causes
The process does not exist.
Solution
Check whether the process is killed unexpectedly.
Check whether the service related to the process has started.
Error Message
Interrupted system call
Possible Causes
The system call is interrupted by another thread.
Solution
Check the multi-thread code logic.
Invoke the system call again.
Error Message
I/O error
Possible Causes
The I/O request is invalid.
Solution
Initiate the I/O request again.
Error Message
No such device or address
Possible Causes
The device information or address is incorrect.
Solution
Check that the device information or address is correct.
Error Message
Arg list too long
Possible Causes
The parameter list is too long.
Solution
Reduce the number of parameters.
Error Message
Bad file descriptor
Possible Causes
Solution
Error Message
No child processes
Possible Causes
The child process cannot be created.
Solution
Check the maximum number of processes in the system.
Error Message
Out of memory
Possible Causes
A memory overflow occurs.
Solution
Check the memory overhead.
Control the memory overhead.
Error Message
Permission denied
Possible Causes
The operation is intercepted by DAC or SELinux.
The file sandbox path is incorrect.
Solution
Check the UGO permission of the file.
Check the kernel log for AVC log information. If yes,visit HUAWEI Developers > Support and submit a ticket online.
Check whether the file path is a sandbox path. The File Management system does not allow operations on files outside the sandbox directory.
Error Message
Bad address
Possible Causes
The address is incorrect.
Solution
Check that the address is correct.
Error Message
Device or resource busy
Possible Causes
The requested resource is unavailable.
Solution
Request the resource again.
Error Message
File exists
Possible Causes
The file to be created already exists.
Solution
Check whether the file path is correct.
Error Message
Cross-device link
Possible Causes
The link between devices is incorrect.
Solution
Check the devices and create the link correctly.
Error Message
No such device
Possible Causes
The device is not identified.
Solution
Check the connection to the target device.
Error Message
Not a directory
Possible Causes
The specified directory is invalid.
Solution
Check that the specified directory is correct.
Error Message
Is a directory
Possible Causes
The specified object is a directory.
Solution
Check that the specified data is correct.
Error Message
Invalid argument
Possible Causes
The input parameter is invalid.
Solution
Check that the input parameters are valid.
Error Message
File table overflow
Possible Causes
The number of file descriptors opened has reached the limit.
Solution
Close the file descriptors that are no longer required.
Error Message
Too many open files
Possible Causes
The number of files opened has reached the limit.
Solution
Close the files that are not required.
Error Message
Text file busy
Possible Causes
The executable file of the program is in use.
Solution
Close the program that is being debugged.
Error Message
File too large
Possible Causes
The file size exceeds the limit.
Solution
Check whether the file size exceeds the limit.
Error Message
No space left on device
Possible Causes
The device storage space is insufficient.
Solution
Clear the space of the device.
Error Message
Illegal seek
Possible Causes
Seek is used in pipe or FIFO.
Solution
Check the use of seek().
Error Message
Read-only file system
Possible Causes
The file system allows read operations only.
Solution
Check whether the file is read-only.
Error Message
Too many links
Possible Causes
The number of links to the file has reached the limit.
Solution
Delete the links that are no longer required.
Error Message
Resource deadlock would occur
Possible Causes
Resource deadlock occurs.
Solution
Terminate the deadlock process.
Error Message
Filename too Long
Possible Causes
The length of the path or file name exceeds the limit.
Solution
Modify the path or file name.
Error Message
Function not implemented
Possible Causes
The function is not supported by the system.
Solution
Check the system version and update the system if required.
Error Message
Directory not empty
Possible Causes
The specified directory is not empty.
Solution
Check the directory.
Ensure that the directory is empty.
Error Message
Too many symbolic links encountered
Possible Causes
There are too many symbolic links.
Solution
Delete unnecessary symbol links.
Error Message
Operation would block
Possible Causes
The operation is blocked.
Solution
Perform the operation again.
Error Message
Invalid request descriptor
Possible Causes
The requested file descriptor is invalid.
Solution
Check that the file descriptor is valid.
Error Message
Device not a stream
Possible Causes
The device pointed to by the file descriptor is not a character stream device.
Solution
Check whether the file descriptor points to a stream.
Error Message
No data available
Possible Causes
The required data is not available.
Solution
Request the data again.
Error Message
Value too large for defined data type
Possible Causes
The specified value is out of the range defined for the data type.
Solution
Modify the data type.
Error Message
File descriptor in bad state
Possible Causes
The file descriptor is corrupted.
Solution
Check that the file descriptor is valid.
Error Message
Interrupted system call should be restarted
Possible Causes
The system call is interrupted.
Solution
Invoke the system call again.
Error Message
Quota exceeded
Possible Causes
The storage space is insufficient.
Solution
Clear disk space.
Error Message
Unknown error
Possible Causes
Internal error
Solution
Call the API again.
Restart the service.
Error Message
No record locks available
Possible Causes
System resources are insufficient.
Solution
Wait until a lock is released and try again.
Error Message
Network is unreachable
Possible Causes
A network error occurs.
Solution
Check the network status.
Error Message
Connection failed
Possible Causes
The device is abnormal, or Wi-Fi or Bluetooth is unavailable.
Solution
Check that the device is in normal status.
Check that Wi-Fi and Bluetooth are available.
Error Message
Software caused connection abort
Possible Causes
The device goes offline, or the Wi-Fi or Bluetooth is disconnected.
Solution
Check that the device is in normal status.
Check that Wi-Fi and Bluetooth are available.
Error Message
Invalid file name
Possible Causes
The file name contains invalid characters.
Solution
Modify the file name.
Error Message
Invalid URI
Possible Causes
The URI is invalid.
Solution
Use the obtained URI.
Error Message
Invalid file name extension
Possible Causes
The file name extension is incorrect.
Solution
Modify the file name extension.
Error Message
File already in the recycle bin
Possible Causes
The file is moved to the Recycle Bin.
Solution
Check whether the file is in the Recycle Bin.
Error Message
System inner fail
Possible Causes
An unidentified error occurs in the system.
Solution
Clear the background or restart the device.
Error Message
Member is not a valid PhotoKey
Possible Causes
The input string is not a member name of a class or interface.
Solution
Ensure that the input string is the member name of the class or interface.
Error Message
IPC error
Possible Causes
The called service does not exist.
Solution
Check whether the service is started.
Error Message
File system not supported
Possible Causes
The file system is not supported.
Solution
Use a supported file system.
Error Message
Mount failed
Possible Causes
The mount command fails.
Solution
Remove the card and run the mount command again.
Error Message
Unmount failed
Possible Causes
The device does not respond.
Solution
Check whether the file is being used. If yes, kill the thread that uses the file.
Error Message
Incorrect volume state
Possible Causes
The volume state is incorrect.
Solution
Check whether the current volume state is correct.
Error Message
Failed to create the drectory or node
Possible Causes
The directory or node to be created already exists.
Solution
Check whether the directory or node to be created already exists.
Error Message
Failed to delete the drectory or node
Possible Causes
The specified directory or node has been deleted.
Solution
Check whether the specified directory or node exists.
Error Message
No such object
Possible Causes
The specified volume ID is incorrect.
The specified bundle name is incorrect.
Solution
Check whether the specified volume exists.
Check whether the specified bundle name exists.
Error Message
User ID out of range
Possible Causes
The specified user ID is incorrect.
Solution
Check that the user ID is correct.
Error Message
IPC error
Possible Causes
The server service does not exist.
The extension mechanism is abnormal.
Solution
Check that the server service exists.
Error Message
Invalid URI
Possible Causes
The URI is invalid.
Solution
Check that the URI is in correct format.
Error Message
Failed to obtain the server ability information
Possible Causes
The BMS interface is abnormal.
Solution
Check for basic system capability errors.
Error Message
Incorrect result returned by js-server
Possible Causes
The data returned by the server is incorrect.
Solution
Check the data returned by the server.
Error Message
Failed to register Notify
Possible Causes
The server service does not exist.
The extension mechanism is abnormal.
Solution
Check that the server service exists.
Error Message
Failed to unregister Notify
Possible Causes
The server service does not exist.
The extension mechanism is abnormal.
Solution
Check that the server service exists.
Error Message
Failed to initialize the Notify agent
Possible Causes
The specified Notify agent has not been registered.
Solution
Check whether the specified Notify agent is registered.