linux error code

合集下载

LINUX操作系统错误代码解释 (中英文对照)

中英文对照Linux操作系统错误代码解释（zhouyutang@ linuxcman@）OS error code0:Success操作系统错误代码0：成功OS error code1:Operation not permitted操作系统错误代码1：操作不允许OS error code2:No such file or directory操作系统错误代码2：没有这样的文件或目录OS error code3:No such process操作系统错误代码3：没有这样的过程OS error code4:Interrupted system call操作系统错误代码4：中断的系统调用OS error code5:Input/output error操作系统错误代码5：输入/输出错误OS error code6:No such device or address操作系统错误代码6：没有这样的设备或地址OS error code7:Argument list too long操作系统错误代码7：参数列表太长OS error code8:Exec format error操作系统错误代码8：执行格式错误OS error code9:Bad file descriptor操作系统错误代码9：坏的文件描述符OS error code10:No child processes操作系统错误代码10：无子过程OS error code11:Resource temporarily unavailable 操作系统错误代码11：资源暂时不可用OS error code12:Cannot allocate memory操作系统错误代码12：无法分配内存OS error code13:Permission denied操作系统错误代码13：权限被拒绝OS error code14:Bad address操作系统错误代码14：错误的地址OS error code15:Block device required操作系统错误代码15：需要块设备OS error code16:Device or resource busy操作系统错误代码16：设备或资源忙OS error code17:File exists操作系统错误代码17：文件已经存在OS error code18:Invalid cross-device link操作系统错误代码18：无效的跨设备链接OS error code19:No such device操作系统错误代码19：没有这样的设备OS error code20:Not a directory操作系统错误代码20：不是一个目录OS error code21:Is a directory操作系统错误代码21：是一个目录OS error code22:Invalid argument操作系统错误代码22：无效参数OS error code23:Too many open files in system操作系统错误代码23：打开太多的文件系统OS error code24:Too many open files操作系统错误代码24：打开的文件太多OS error code25:Inappropriate ioctl for device操作系统错误代码25：不适当的设备ioctl使用OS error code26:Text file busy操作系统错误代码26：文本文件忙OS error code27:File too large操作系统错误代码27：文件太大OS error code28:No space left on device操作系统错误代码28：设备上没有空间OS error code29:Illegal seek操作系统错误代码29：非法搜索OS error code30:Read-only file system操作系统错误代码30：只读文件系统OS error code31:Too many links操作系统错误代码31：链接过多OS error code32:Broken pipe操作系统错误代码32：管道破裂OS error code33:Numerical argument out of domain 操作系统错误代码33：超出域的数值参数OS error code34:Numerical result out of range操作系统错误代码34：数值结果超出范围OS error code35:Resource deadlock avoided操作系统错误代码35：避免资源死锁OS error code36:File name too long操作系统错误代码36：文件名太长OS error code37:No locks available操作系统错误代码37：没有可用锁OS error code38:Function not implemented操作系统错误代码38：功能没有实现OS error code39:Directory not empty操作系统错误代码39：目录非空OS error code40:Too many levels of symbolic links 操作系统错误代码40：符号链接层次太多OS error code42:No message of desired type操作系统错误代码42：没有期望类型的消息OS error code43:Identifier removed操作系统错误代码43：标识符删除OS error code44:Channel number out of range操作系统错误代码44：通道数目超出范围OS error code45:Level2not synchronized操作系统错误代码45：2级不同步OS error code46:Level3halted操作系统错误代码46：3级终止OS error code47:Level3reset操作系统错误代码47：3级复位OS error code48:Link number out of range操作系统错误代码48：链接数超出范围OS error code49:Protocol driver not attached 操作系统错误代码49：协议驱动程序没有连接OS error code50:No CSI structure available 操作系统错误代码50：没有可用的CSI结构OS error code51:Level2halted操作系统错误代码51：2级中断OS error code52:Invalid exchange操作系统错误代码52：无效的交换OS error code53:Invalid request descriptor 操作系统错误代码53：无效的请求描述符OS error code54:Exchange full操作系统错误代码54：交换空间满OS error code55:No anode操作系统错误代码55：阳极不存在OS error code56:Invalid request code操作系统错误代码56：无效的请求代码OS error code57:Invalid slot操作系统错误代码57：无效的槽OS error code59:Bad font file format操作系统错误代码59：错误的字体文件格式OS error code60:Device not a stream操作系统错误代码60：设备不属于流类型OS error code61:No data available操作系统错误代码61：无可用数据OS error code62:Timer expired操作系统错误代码62：超时OS error code63:Out of streams resources操作系统错误代码63：超出流资源范围OS error code64:Machine is not on the network 操作系统错误代码64：主机不在网络上OS error code65:Package not installed操作系统错误代码65：软件包没有安装OS error code66:Object is remote操作系统错误代码66：对象是远程的OS error code67:Link has been severed操作系统错误代码67：链接被切断OS error code68:Advertise error操作系统错误代码68：广告错误OS error code69:Srmount error操作系统错误代码69：srmount错误OS error code70:Communication error on send 操作系统错误代码70：发送数据时通讯错误OS error code71:Protocol error操作系统错误代码71：协议错误OS error code72:Multihop attempted操作系统错误代码72：企图进行多次跳转OS error code73:RFS specific error操作系统错误代码73：RFS类型错误OS error code74:Bad message操作系统错误代码74：坏消息OS error code75:Value too large for defined data type操作系统错误代码75：数值超过对于给定的数据类型OS error code76:Name not unique on network操作系统错误代码76：主机名在网络上不是唯一OS error code77:File descriptor in bad state操作系统错误代码77：坏状态的文件描述符OS error code78:Remote address changed操作系统错误代码78：远端地址改变OS error code79:Can not access a needed shared library操作系统错误代码79：无法访问需要的共享库OS error code80:Accessing a corrupted shared library操作系统错误代码80：访问了一个损坏的共享库OS error code81:.lib section in a.out corrupted操作系统错误代码81：a.out文件中的.lib段损坏。

linux pssh exited with error code -回复

linux pssh exited with error code -回复Linux PSSH is a powerful command-line tool that allows users to remotely manage multiple systems simultaneously. However, there are instances where PSSH may exit with an error code, preventing users from achieving their intended tasks. In this article, we will delve into some common situations that can cause PSSH to exit with an error code and discuss potential solutions to overcome them.1. Understanding the Error CodeWhen PSSH exits with an error code, it signifies that an error has occurred during the execution of the command. The error code provides valuable information about the type of error encountered, helping users identify the problem and find a suitable solution.2. Common Causes of PSSH Exit Errorsa. Authentication Failure: One of the most common causes of PSSH exit errors is an authentication failure. If the remote systems require SSH keys or passwords for authentication, any mismatch or incorrect input can result in an authentication failure and cause PSSH to exit with an error code. Ensure that the authentication credentials are correctly specified and accessible.b. Connection Issues: PSSH relies on stable and reliable network connections to establish communication with remote systems. Inadequate or interrupted network connectivity can cause PSSH to exit with an error code. Check the network settings, firewall configuration, and the status of the remote systems to identify and address any connection issues.c. Command Syntax Errors: Incorrect command syntax or improper usage of PSSH commands can lead to exit errors. Review the command syntax carefully, ensure that the commands are appropriately formatted, and consider consulting the PSSH documentation for correct usage.d. Insufficient Privileges: PSSH requires sufficient privileges to execute certain commands or access specific files. If the user executing PSSH does not have the necessary privileges, it can result in exit errors. Ensure that the user has the required permissions to perform the desired tasks and modify the user privileges accordingly.e. Resource Constraints: PSSH may exit with an error code if theremote systems are running low on system resources such as memory or disk space. Insufficient resources can hinder the execution of commands, causing PSSH to terminate with an error. Verify the resource utilization on the remote systems and take appropriate action to alleviate any resource constraints.3. Troubleshooting PSSH Exit Errorsa. Check Error Codes: When PSSH exits with an error code, review the numeric value of the error to gain insights into the specific issue encountered. Error codes are commonly documented in PSSH's official documentation or forums. Understanding the error code can narrow down the troubleshooting process and guide you towards a solution.b. Verify Authentication Credentials: Double-check the authenticity credentials provided to PSSH. Ensure that SSH keys are correctly configured, passwords are entered correctly, and the necessary credentials are accessible and valid. Fix any mismatches or incorrect inputs to resolve authentication failures.c. Test Network Connectivity: Evaluate network connectivity between the local and remote systems. Verify that there are nofirewalls, proxies, or network restrictions preventing proper communication. Conduct network tests, such as pinging the remote system or using SSH directly, to identify any network issues.d. Review Command Syntax: Thoroughly review the command syntax used with PSSH. Pay special attention to the order of options, use of quotation marks, and any special characters required. Utilize PSSH's documentation or consult online resources to ensure correct command usage.e. Confirm User Privileges: Determine if the user executing PSSH has the necessary permissions to perform the desired tasks. Check the user's permissions, group memberships, and any restricted access policies that might affect PSSH's execution. Elevate user privileges if necessary.f. Monitor System Resources: Keep an eye on the resource utilization of both the local and remote systems where PSSH is being used. Ensure sufficient memory, disk space, and CPU availability to avoid resource-related exit errors. Free up resources, if needed, by terminating unnecessary processes or expanding resource capacity.4. ConclusionLinux PSSH is a versatile tool for managing remote systems efficiently. However, it is not immune to occasional errors leading to premature exits. By identifying common causes such as authentication failures, connection issues, command syntax errors, insufficient privileges, and resource constraints, users can effectively troubleshoot and resolve PSSH exit errors. Remember to consult official documentation and utilize online resources for specific error code meanings and additional troubleshooting techniques. With the insights provided in this article, users can overcome hurdles and maximize the potential of PSSH for seamless remote system management.。

linux 上几条命令的exit code

在Linux 上，命令的退出码（exit code）是一个整数，用于表示命令执行的结果。

通常情况下，退出码为0 表示命令执行成功，非零值表示出现错误。

以下是一些常见的退出码及其含义：
- 0：表示命令执行成功
- 1：表示命令执行失败
- 2：表示命令执行过程中出现错误
- 126：表示命令无法找到
- 127：表示命令未找到
- 其他数字：表示命令执行过程中出现的错误代码
这些退出码可以在命令执行后通过`$?` 变量获取。

例如：
```bash
ls /nonexistent_directory
echo $?
```
在这个例子中，`ls` 命令尝试列出一个不存在的目录，因此返回非零退出码2。

通过`echo $?` 可以输出这个退出码。

Linux系统错误码对照表

Linux系统错误码对照表C Name Value DescriptionEPERM1Operation not permittedENOENT2No such file or directoryESRCH3No such processEINTR4Interrupted system callEIO5I/O errorENXIO6No such device or addressE2BIG7Arg list too longENOEXEC8Exec format errorEBADF9Bad file numberECHILD10No child processesEAGAIN11Try againENOMEM12Out of memoryEACCES13Permission deniedEFAULT14Bad addressENOTBLK15Block device requiredEBUSY16Device or resource busyEEXIST17File existsEXDEV18Cross-device linkENODEV19No such deviceENOTDIR20Not a directoryEISDIR21Is a directoryEINVAL22Invalid argumentENFILE23File table overflowEMFILE24Too many open filesENOTTY25Not a tty deviceETXTBSY26Text file busyEFBIG27File too largeENOSPC28No space left on deviceESPIPE29Illegal seekEROFS30Read-only file systemEMLINK31Too many linksEPIPE32Broken pipeEDOM33Math argument out of domainERANGE34Math result not representableEDEADLK35Resource deadlock would occurENAMETOOLONG36Filename too longENOLCK37No record locks availableENOSYS38Function not implementedENOTEMPTY39Directory not emptyELOOP40Too many symbolic links encounteredEWOULDBLOCK41Same as EAGAINENOMSG42No message of desired typeEIDRM43Identifier removedECHRNG44Channel number out of rangeEL2NSYNC45Level 2 not synchronizedEL3HLT46Level 3 haltedEL3RST47Level 3 resetELNRNG48Link number out of rangeEUNATCH49Protocol driver not attachedENOCSI50No CSI structure availableEL2HLT51Level 2 haltedEBADE52Invalid exchangeEBADR53Invalid request descriptorEXFULL54Exchange fullEXFULL54Exchange fullENOANO55No anodeEBADRQC56Invalid request codeEBADSLT57Invalid slotEDEADLOCK -Same as EDEADLKEBFONT59Bad font file formatENOSTR60Device not a streamENODATA61No data availableETIME62Timer expiredENOSR63Out of streams resourcesENONET64Machine is not on the network ENOPKG65Package not installedEREMOTE66Object is remoteENOLINK67Link has been severedEADV68Advertise errorESRMNT69Srmount errorECOMM70Communication error on send EPROTO71Protocol errorEMULTIHOP72Multihop attemptedEDOTDOT73RFS specific errorEBADMSG74Not a data messageEOVERFLOW75Value too large for defined data type ENOTUNIQ76Name not unique on networkEBADFD77File descriptor in bad state EREMCHG78Remote address changedELIBACC79Cannot access a needed shared library ELIBBAD80Accessing a corrupted shared library ELIBSCN81 A .lib section in an .out is corrupted ELIBMAX82Linking in too many shared libraries ELIBEXEC83Cannot exec a shared library directly EILSEQ84Illegal byte sequenceERESTART85Interrupted system call should be restarted ESTRPIPE86Streams pipe errorEUSERS87Too many usersENOTSOCK88Socket operation on non-socket EDESTADDRREQ89Destination address required EMSGSIZE90Message too longEPROTOTYPE91Protocol wrong type for socket ENOPROTOOPT92Protocol not available EPROTONOSUPPORT93Protocol not supported ESOCKTNOSUPPORT94Socket type not supported EOPNOTSUPP95Operation not supported on transport EPFNOSUPPORT96Protocol family not supported EAFNOSUPPORT97Address family not supported by protocol EADDRINUSE98Address already in use EADDRNOTAVAIL99Cannot assign requested address ENETDOWN100Network is downENETUNREACH101Network is unreachableENETRESET102Network dropped ECONNABORTED103Software caused connection ECONNRESET104Connection reset byENOBUFS105No buffer space availableEISCONN106Transport endpointENOTCONN107Transport endpointESHUTDOWN108Cannot send after transport ETOOMANYREFS109Too many referencesETIMEDOUT110Connection timed ECONNREFUSED111Connection refusedECONNREFUSED111Connection refused EHOSTDOWN112Host is down EHOSTUNREACH113No route to host EALREADY114Operation already EINPROGRESS115Operation now in ESTALE116Stale NFS file handle EUCLEAN117Structure needs cleaning ENOTNAM118Not a XENIX-named ENAVAIL119No XENIX semaphores EISNAM120Is a named type file EREMOTEIO121Remote I/O error EDQUOT122Quota exceeded ENOMEDIUM123No medium found EMEDIUMTYPE124Wrong medium type。

linux errno 处理方法 -回复

linux errno 处理方法-回复"Linux errno Error Handling Methods: A Step-by-Step Guide"Introduction:In Linux, error numbers (errno) are used to indicate various types of errors that can occur during system calls or library function calls. These error codes provide valuable information about the cause and nature of the error, aiding developers in troubleshooting and handling errors effectively. In this article, we will delve into errno handling methods in Linux, providing a step-by-step guide to address them proficiently.Step 1: Understanding errnoErrno is a globally accessible integer variable that is set by system calls or library functions when an error occurs. It is declared in the header file "errno.h" and is initialized to zero at program startup. When an error occurs, the system calls or library functions set the appropriate error code in errno, and the error code remains valid until it is explicitly changed by a successful function call or until the program exits.Step 2: Retrieving Error InformationTo retrieve error information, we need to include the "errno.h" header file and access the value of errno using the global variable. The value of errno can be different for each error and typically ranges from 1 to 255. Additionally, the "string.h" header file provides the strerror() function, which converts errno to a human-readable string representing the error message.Step 3: Analyzing Common Errno ErrorsLinux provides a comprehensive set of error codes for various types of errors. Some commonly encountered errno errors include:- EACCES (13): Permission denied –Indicates unauthorized access to a file or directory. To handle this error, ensure the correct permissions are set and authenticate the user if necessary.- EFAULT (14): Bad address –Occurs when an invalid or inaccessible memory address is accessed. This error can be handled by checking for invalid pointer dereferences and validating memory addresses.- EINVAL (22): Invalid argument –Indicates that an argument passed to a function is unexpected or invalid. To resolve this error, ensure the correct data types and values are passed as arguments to the function.- ENOENT (2): No such file or directory –Occurs when a file or directory being accessed does not exist. To handle this error, verify the existence and correct path of the file or directory being referenced.- EIO (5): Input/output error –Represents an input or output operation failure. This error requires thorough investigation, including checking for faulty hardware, file system corruption, or incorrect device configurations.Step 4: Proper Error Handling TechniquesWhen encountering errno errors, it is crucial to handle them properly to avoid program crashes and ensure graceful recovery. Some best practices for error handling include:- Check and Report Errors: Always check the return value of system calls or functions for failure and evaluate the errno value. If an error occurs, analyze the errno value and report or log appropriate error messages for debugging purposes.- Graceful Error Recovery: Depending on the nature of the error, implement appropriate recovery mechanisms. This may involve attempting the operation again, providing alternate solutions, or terminating the program gracefully while ensuring any activeresources are properly released.- Error Propagation: In cases where functions call other functions, it is essential to propagate errors to the calling functions instead of silently ignoring or mishandling them. This allows for proper error handling at higher levels of the program.- Use EINTR Handling: Certain system calls can be interrupted by signals, resulting in errno being set to EINTR. This can be managed by implementing a retry mechanism to ensure the interrupted system call completes successfully.Step 5: Advanced Error Handling TechniquesIn addition to the basic error handling techniques mentioned above, Linux provides several advanced features to enhance error handling:- errno Thread Safety: By default, errno is a global variable accessible to all threads. However, Linux provides a per-thread variant called "__errno_location()" to ensure thread safety. This function returns a pointer to the thread-specific errno variable to avoid potential race conditions.- Error Queues: In some cases, multiple errors may occur before a program handles each one. Linux provides the feature ofmaintaining a queue of errors using "errno" and "perror" functions, allowing developers to address multiple errors systematically.- Error Logging: To aid in debugging and troubleshooting, logging error messages and associated information is essential. Linux offers various logging mechanisms, such as syslog, which allows errors to be recorded with timestamp information, severity levels, and other relevant details.Conclusion:Understanding and effectively handling errno errors is vital for developing robust and reliable Linux applications. By following the step-by-step guide provided in this article, developers can proficiently address errno errors, check for potential pitfalls, and implement appropriate error handling techniques. By doing so, developers can enhance the stability and reliability of theirLinux-based software systems.。

常见的Linux系统错误码

常见的Linux系统错误码，即errorno的值1 EPERM Operation not permitted 操作不许可2 ENOENT No such file or directory 无此文件或目录3 ESRCH No such process 无此过程4 EINTR Interrupted system call 系统调用被禁止5 EIO I/O error I/O 错误6 ENXIO No such device or address 无此器件或地址7 E2BIG Arg list too long Arg 列表太长8 ENOEXEC Exec format error Exec 格式错误9 EBADF Bad file number 文件数目错误10 ECHILD No child processes 无子过程11 EAGAIN Try again 再试一遍12 ENOMEM Out of memory 内存溢出13 EACCES Permission denied 许可拒绝14 EFAULT Bad address 错误的地址15 ENOTBLK Block device required 需要块设备16 EBUSY Device or resource busy 设备或资源忙17 EEXIST File exists 文件存在18 EXDEV Cross-device link 跨器链接19 ENODEV No such device 无此设备20 ENOTDIR Not a directory 不是一个目录21 EISDIR Is a directory 是一个目录22 EINV AL Invalid argument 无效的函数自变量23 ENFILE File table overflow 文件表溢出24 EMFILE Too many open files 打开的文件太多25 ENOTTY Inappropriate ioctl for device26 ETXTBSY Text file busy 文本文件忙27 EFBIG File too large 文件太大28 ENOSPC No space left on device 磁盘空间不足29 ESPIPE Illegal seek 不合法的寻找30 EROFS Read-only file system 只读文件系统31 EMLINK Too many links 太多的链接/usr/include/asm-generic/errno-base.h#define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */#define EINTR 4 /* Interrupted system call */ #define EIO 5 /* I/O error */#define ENXIO 6 /* No such device or address */ #define E2BIG 7 /* Argument list too long */#define ENOEXEC 8 /* Exec format error */#define EBADF 9 /* Bad file number */#define ECHILD 10 /* No child processes */#define EAGAIN 11 /* Try again */#define ENOMEM 12 /* Out of memory */#define EACCES 13 /* Permission denied */#define EFAULT 14 /* Bad address */#define ENOTBLK 15 /* Block device required */#define EBUSY 16 /* Device or resource busy */ #define EEXIST 17 /* File exists */#define EXDEV 18 /* Cross-device link */#define ENODEV 19 /* No such device */#define ENOTDIR 20 /* Not a directory */#define EISDIR 21 /* Is a directory */#define EINVAL 22 /* Invalid argument */#define ENFILE 23 /* File table overflow */#define EMFILE 24 /* Too many open files */#define ENOTTY 25 /* Not a typewriter */#define ETXTBSY 26 /* Text file busy */#define EFBIG 27 /* File too large */#define ENOSPC 28 /* No space left on device */#define ESPIPE 29 /* Illegal seek */#define EROFS 30 /* Read-only file system */#define EMLINK 31 /* Too many links */#define EPIPE 32 /* Broken pipe */#define EDOM 33 /* Math argument out of domain of func */ #define ERANGE 34 /* Math result not representable *//usr/include/asm-generic/errno.h#define EDEADLK 35 /* Resource deadlock would occur */#define ENAMETOOLONG 36 /* File name too long */#define ENOLCK 37 /* No record locks available */#define ENOSYS 38 /* Function not implemented */#define ENOTEMPTY 39 /* Directory not empty */#define ELOOP 40 /* Too many symbolic links encountered */ #define EWOULDBLOCK EAGAIN /* Operation would block */#define ENOMSG 42 /* No message of desired type */#define EIDRM 43 /* Identifier removed */#define ECHRNG 44 /* Channel number out of range */#define EL2NSYNC 45 /* Level 2 not synchronized */#define EL3HLT 46 /* Level 3 halted */#define EL3RST 47 /* Level 3 reset */#define ELNRNG 48 /* Link number out of range */#define EUNATCH 49 /* Protocol driver not attached */ #define ENOCSI 50 /* No CSI structure available */#define EL2HLT 51 /* Level 2 halted */#define EBADE 52 /* Invalid exchange */#define EBADR 53 /* Invalid request descriptor */#define EXFULL 54 /* Exchange full */#define ENOANO 55 /* No anode */#define EBADRQC 56 /* Invalid request code */#define EBADSLT 57 /* Invalid slot */#define EDEADLOCK EDEADLK#define EBFONT 59 /* Bad font file format */#define ENOSTR 60 /* Device not a stream */#define ENODATA 61 /* No data available */#define ETIME 62 /* Timer expired */#define ENOSR 63 /* Out of streams resources */#define ENONET 64 /* Machine is not on the network */ #define ENOPKG 65 /* Package not installed */#define EREMOTE 66 /* Object is remote */#define ENOLINK 67 /* Link has been severed */#define EADV 68 /* Advertise error */#define ESRMNT 69 /* Srmount error */#define ECOMM 70 /* Communication error on send */#define EPROTO 71 /* Protocol error */#define EMULTIHOP 72 /* Multihop attempted */#define EDOTDOT 73 /* RFS specific error */#define EBADMSG 74 /* Not a data message */#define EOVERFLOW 75 /* Value too large for defined data type */#define ENOTUNIQ 76 /* Name not unique on network */#define EBADFD 77 /* File descriptor in bad state */#define EREMCHG 78 /* Remote address changed */#define ELIBACC 79 /* Can not access a needed shared library */#define ELIBBAD 80 /* Accessing a corrupted shared library */#define ELIBSCN 81 /* .lib section in a.out corrupted */#define ELIBMAX 82 /* Attempting to link in too many shared libraries */ #define ELIBEXEC 83 /* Cannot exec a shared library directly */#define EILSEQ 84 /* Illegal byte sequence */#define ERESTART 85 /* Interrupted system call should be restarted */#define ESTRPIPE 86 /* Streams pipe error */#define EUSERS 87 /* Too many users */#define ENOTSOCK 88 /* Socket operation on non-socket */#define EDESTADDRREQ 89 /* Destination address required */#define EMSGSIZE 90 /* Message too long */#define EPROTOTYPE 91 /* Protocol wrong type for socket */#define ENOPROTOOPT 92 /* Protocol not available */#define EPROTONOSUPPORT 93 /* Protocol not supported */#define ESOCKTNOSUPPORT 94 /* Socket type not supported */#define EOPNOTSUPP 95 /* Operation not supported on transport endpoint */#define EPFNOSUPPORT 96 /* Protocol family not supported */#define EAFNOSUPPORT 97 /* Address family not supported by protocol */ #define EADDRINUSE 98 /* Address already in use */#define EADDRNOTAVAIL 99 /* Cannot assign requested address */#define ENETDOWN 100 /* Network is down */#define ENETUNREACH 101 /* Network is unreachable */#define ENETRESET 102 /* Network dropped connection because of reset */#define ECONNABORTED 103 /* Software caused connection abort */#define ECONNRESET 104 /* Connection reset by peer */#define ENOBUFS 105 /* No buffer space available */#define EISCONN 106 /* Transport endpoint is already connected */#define ENOTCONN 107 /* Transport endpoint is not connected */#define ESHUTDOWN 108 /* Cannot send after transport endpoint shutdown */#define ETOOMANYREFS 109 /* Too many references: cannot splice */#define ETIMEDOUT 110 /* Connection timed out */#define ECONNREFUSED 111 /* Connection refused */#define EHOSTDOWN 112 /* Host is down */#define EHOSTUNREACH 113 /* No route to host */#define EALREADY 114 /* Operation already in progress */ #define EINPROGRESS 115 /* Operation now in progress */ #define ESTALE 116 /* Stale NFS file handle */#define EUCLEAN 117 /* Structure needs cleaning */#define ENOTNAM 118 /* Not a XENIX named type file */ #define ENAVAIL 119 /* No XENIX semaphores available */ #define EISNAM 120 /* Is a named type file */#define EREMOTEIO 121 /* Remote I/O error */#define EDQUOT 122 /* Quota exceeded */#define ENOMEDIUM 123 /* No medium found */#define EMEDIUMTYPE 124 /* Wrong medium type */#define ECANCELED 125 /* Operation Canceled */#define ENOKEY 126 /* Required key not available */#define EKEYEXPIRED 127 /* Key has expired */#define EKEYREVOKED 128 /* Key has been revoked */#define EKEYREJECTED 129 /* Key was rejected by service */ /* for robust mutexes */#define EOWNERDEAD 130 /* Owner died */#define ENOTRECOVERABLE 131 /* State not recoverable */。

linux errno 处理方法

linux errno 处理方法"Linux errno Error Handling Methods: A Step-by-Step Guide"Introduction:In Linux, error numbers (errno) are used to indicate various types of errors that can occur during system calls or library function calls. These error codes provide valuable information about the cause and nature of the error, aiding developers in troubleshooting and handling errors effectively. In this article, we will delve into errno handling methods in Linux, providing a step-by-step guide to address them proficiently.Step 1: Understanding errnoErrno is a globally accessible integer variable that is set by system calls or library functions when an error occurs. It is declared in the header file "errno.h" and is initialized to zero at program startup. When an error occurs, the system calls or library functions set the appropriate error code in errno, and the error code remains valid until it is explicitly changed by a successful function call or until the program exits.Step 2: Retrieving Error InformationTo retrieve error information, we need to include the "errno.h" header file and access the value of errno using the global variable. The value of errno can be different for each error and typically ranges from 1 to 255. Additionally, the "string.h" header file provides the strerror() function, which converts errno to a human-readable string representing the error message.Step 3: Analyzing Common Errno ErrorsLinux provides a comprehensive set of error codes for various types of errors. Some commonly encountered errno errors include:- EACCES (13): Permission denied –Indicates unauthorized access to a file or directory. To handle this error, ensure the correct permissions are set and authenticate the user if necessary.- EFAULT (14): Bad address –Occurs when an invalid or inaccessible memory address is accessed. This error can be handled by checking for invalid pointer dereferences and validating memory addresses.- EINVAL (22): Invalid argument –Indicates that an argument passed to a function is unexpected or invalid. To resolve this error, ensure the correct data types and values are passed as arguments to the function.- ENOENT (2): No such file or directory –Occurs when a file or directory being accessed does not exist. To handle this error, verify the existence and correct path of the file or directory being referenced.- EIO (5): Input/output error –Represents an input or output operation failure. This error requires thorough investigation, including checking for faulty hardware, file system corruption, or incorrect device configurations.Step 4: Proper Error Handling TechniquesWhen encountering errno errors, it is crucial to handle them properly to avoid program crashes and ensure graceful recovery. Some best practices for error handling include:- Check and Report Errors: Always check the return value of system calls or functions for failure and evaluate the errno value. If an error occurs, analyze the errno value and report or log appropriate error messages for debugging purposes.- Graceful Error Recovery: Depending on the nature of the error, implement appropriate recovery mechanisms. This may involve attempting the operation again, providing alternate solutions, or terminating the program gracefully while ensuring any activeresources are properly released.- Error Propagation: In cases where functions call other functions, it is essential to propagate errors to the calling functions instead of silently ignoring or mishandling them. This allows for proper error handling at higher levels of the program.- Use EINTR Handling: Certain system calls can be interrupted by signals, resulting in errno being set to EINTR. This can be managed by implementing a retry mechanism to ensure the interrupted system call completes successfully.Step 5: Advanced Error Handling TechniquesIn addition to the basic error handling techniques mentioned above, Linux provides several advanced features to enhance error handling:- errno Thread Safety: By default, errno is a global variable accessible to all threads. However, Linux provides a per-thread variant called "__errno_location()" to ensure thread safety. This function returns a pointer to the thread-specific errno variable to avoid potential race conditions.- Error Queues: In some cases, multiple errors may occur before a program handles each one. Linux provides the feature ofmaintaining a queue of errors using "errno" and "perror" functions, allowing developers to address multiple errors systematically.- Error Logging: To aid in debugging and troubleshooting, logging error messages and associated information is essential. Linux offers various logging mechanisms, such as syslog, which allows errors to be recorded with timestamp information, severity levels, and other relevant details.Conclusion:Understanding and effectively handling errno errors is vital for developing robust and reliable Linux applications. By following the step-by-step guide provided in this article, developers can proficiently address errno errors, check for potential pitfalls, and implement appropriate error handling techniques. By doing so, developers can enhance the stability and reliability of theirLinux-based software systems.。

Linux错误码大全（建议收藏）

Linux错误码大全（建议收藏）Linux错误码大全查看错误代码errno是调试程序的一个重要方法。

当linuc C api 函数发生异常时,一般会将errno变量(需include errno.h)赋一个整数值,不同的值表示不同的含义,可以通过查看该值推测出错的原因。

在实际编程中用这一招解决了不少原本看来莫名其妙的问题。

比较麻烦的是每次都要去linux源代码里面查找错误代码的含义，现在把它贴出来，以后需要查时就来这里看了。

1-34号错误号是在内核源码的include/asm-generic/errno-base.h定义35-132则是在include/asm-generic/errno.h中定义剩下还有一些更大的错误号是留给内核级别的，如系统调用等，用户程序一般是看不见的这些号的，Ubuntu9.10中/usr/src/linux-headers-2.6.31-21-generic/include/linux/errno.h#ifndef _ASM_GENERIC_ERRNO_BASE_H#define _ASM_GENERIC_ERRNO_BASE_H#define EPERM 1 /＊Operation not permitted ＊/ #define ENOENT 2 /＊No such file or directory ＊/ #define ESRCH 3 /＊No such process ＊/#define EINTR 4 /＊Interrupted system call ＊/ #define EIO 5 /＊I/O error ＊/#define ENXIO 6 /＊No such device or address ＊/ #define E2BIG 7 /＊Argument list too long ＊/ #define ENOEXEC 8 /＊Exec format error ＊/ #define EBADF 9 /＊Bad file number ＊/ #define ECHILD 10 /＊No child processes ＊/ #define EAGAIN 11 /＊Try again ＊/#define ENOMEM 12 /＊Out of memory ＊/#define EACCES 13 /＊Permission denied ＊/ #define EFAULT14 /＊Bad address ＊/#define ENOTBLK 15 /＊Block device required ＊/ #define EBUSY16 /＊Device or resource busy ＊/ #define EEXIST 17 /＊File exists ＊/#define EXDEV 18 /＊Cross-device link ＊/#define ENODEV 19 /＊No such device ＊/#define ENOTDIR 20 /＊Not a directory ＊/#define EISDIR 21 /＊Is a directory ＊/#define EINVAL 22 /＊Invalid argument ＊/#define ENFILE 23 /＊File table overflow ＊/#define EMFILE 24 /＊Too many open files ＊/#define ENOTTY 25 /＊Not a typewriter ＊/#define ETXTBSY 26 /＊Text file busy ＊/#define EFBIG 27 /＊File too large ＊/#define ENOSPC 28 /＊No space left on device ＊/ #define ESPIPE 29 /＊Illegal seek ＊/#define EROFS 30 /＊Read-only file system ＊/#define EMLINK 31 /＊Too many links ＊/#define EPIPE 32 /＊Broken pipe ＊/#define EDOM 33 /＊Math argument out of domain of func ＊/#define ERANGE 34 /＊Math result not representable ＊/#endif#include#define EDEADLK 35 /＊Resource deadlock would occur ＊/ #define ENAMETOOLONG 36 /＊File name too long ＊/ #define ENOLCK 37 /＊No record locks available ＊/ #define ENOSYS 38 /＊Function not implemented ＊/ #define ENOTEMPTY 39 /＊Directory not empty ＊/#define ELOOP 40 /＊Too many symbolic links encountered ＊/#define EWOULDBLOCK EAGAIN /＊Operation would block ＊/ #define ENOMSG 42 /＊No message of desired type ＊/ #define EIDRM 43 /＊Identifier removed ＊/#define ECHRNG 44 /＊Channel number out of range ＊/ #define EL2NSYNC 45 /＊Level 2 not synchronized ＊/ #define EL3HLT 46 /＊Level 3 halted ＊/#define EL3RST 47 /＊Level 3 reset ＊/#define ELNRNG 48 /＊Link number out of range ＊/#define EUNATCH 49 /＊Protocol driver not attached ＊/ #define ENOCSI 50 /＊No CSI structure available ＊/ #define EL2HLT 51 /＊Level 2 halted ＊/#define EBADE 52 /＊Invalid exchange ＊/#define EBADR 53 /＊Invalid request descriptor ＊/ #define EXFULL 54 /＊Exchange full ＊/#define ENOANO 55 /＊No anode ＊/#define EBADRQC 56 /＊Invalid request code ＊/ #define EBADSLT 57 /＊Invalid slot ＊/#define EDEADLOCK EDEADLK#define EBFONT 59 /＊Bad font file format ＊/#define ENOSTR 60 /＊Device not a stream ＊/#define ENODATA 61 /＊No data available ＊/#define ETIME 62 /＊Timer expired ＊/#define ENOSR 63 /＊Out of streams resources ＊/#define ENONET 64 /＊Machine is not on the network ＊/ #define ENOPKG 65 /＊Package not installed ＊/ #define EREMOTE 66 /＊Object is remote ＊/#define ENOLINK 67 /＊Link has been severed ＊/ #define EADV 68 /＊Advertise error ＊/#define ESRMNT 69 /＊Srmount error ＊/#define ECOMM 70 /＊Communication error on send ＊/ #define EPROTO 71 /＊Protocol error ＊/#define EMULTIHOP 72 /＊Multihop attempted ＊/#define EDOTDOT 73 /＊RFS specific error ＊/#define EBADMSG 74 /＊Not a data message ＊/#define EOVERFLOW 75 /＊Value too large for defined data type ＊/#define ENOTUNIQ 76 /＊Name not unique on network ＊/ #define EBADFD 77 /＊File descriptor in bad state ＊/ #define EREMCHG 78 /＊Remote address changed ＊/ #define ELIBACC 79 /＊Can not access a needed shared library ＊/#define ELIBBAD 80 /＊Accessing a corrupted shared library ＊/ #define ELIBSCN 81 /＊ .lib section in a.out corrupted ＊/ #define ELIBMAX 82 /＊Attempting to link in too many shared libraries ＊/#define ELIBEXEC 83 /＊Cannot exec a shared library directly ＊/ #define EILSEQ 84 /＊Illegal byte sequence ＊/#define ERESTART 85 /＊Interrupted system call should be restarted ＊/#define ESTRPIPE 86 /＊Streams pipe error ＊/#define EUSERS 87 /＊Too many users ＊/#define ENOTSOCK 88 /＊Socket operation on non-socket ＊/#define EDESTADDRREQ 89 /＊Destination address required ＊/ #define EMSGSIZE 90 /＊Message too long ＊/#define EPROTOTYPE 91 /＊Protocol wrong type for socket ＊/ #define ENOPROTOOPT 92 /＊Protocol not available ＊/ #define EPROTONOSUPPORT 93 /＊Protocol not supported ＊/ #define ESOCKTNOSUPPORT 94 /＊Socket type notsupported ＊/ #define EOPNOTSUPP 95 /＊Operation not supported on transport endpoint ＊/#define EPFNOSUPPORT 96 /＊Protocol family not supported ＊/ #define EAFNOSUPPORT 97 /＊Address family not supported by protocol ＊/#define EADDRINUSE 98 /＊Address already in use ＊/#define EADDRNOTAVAIL 99 /＊Cannot assign requested address ＊/#define ENETDOWN 100 /＊Network is down ＊/#define ENETUNREACH 101 /＊Network is unreachable ＊/ #define ENETRESET 102 /＊Network dropped connection because of reset ＊/#define ECONNABORTED 103 /＊Software caused connection abort ＊/#define ECONNRESET 104 /＊Connection reset by peer ＊/ #define ENOBUFS 105 /＊No buffer space available ＊/ #define EISCONN 106 /＊Transport endpoint is already connected ＊/#define ENOTCONN 107 /＊Transport endpoint is not connected ＊/#define ESHUTDOWN 108 /＊Cannot send after transport endpoint shutdown ＊/#define ETOOMANYREFS 109 /＊T oo many references: cannot splice ＊/#define ETIMEDOUT 110 /＊Connection timed out ＊/#define ECONNREFUSED 111 /＊Connection refused ＊/ #define EHOSTDOWN 112 /＊Host is down ＊/#define EHOSTUNREACH 113 /＊No route to host ＊/#define EALREADY 114 /＊Operation already in progress ＊/ #define EINPROGRESS 115 /＊Operation now in progress ＊/#define ESTALE 116 /＊Stale NFS file handle ＊/ #define EUCLEAN 117 /＊Structure needs cleaning ＊/ #define ENOTNAM 118 /＊Not a XENIX named type file ＊/ #define ENAVAIL 119 /＊No XENIX semaphores available ＊/ #define EISNAM 120 /＊Is a named type file ＊/ #define EREMOTEIO 121 /＊Remote I/O error ＊/#define EDQUOT 122 /＊Quota exceeded ＊/#define ENOMEDIUM 123 /＊No medium found ＊/#define EMEDIUMTYPE 124 /＊Wrong medium type ＊#define ECANCELED 125 / ＊操作已取消＊/#define ENOKEY 126 / ＊必需的密钥不可用＊/ #define EKEYEXPIRED 127 / ＊密钥已过期＊/#define EKEYREVOKED 128 / ＊密钥已被撤销＊/#define EKEYREJECTED 129 / ＊密钥被服务拒绝＊// ＊用于强大的互斥体＊/#define EOWNERDEAD 130 / ＊所有者死亡＊/#define ENOTRECOVERABLE 131 / ＊状态不可恢复＊/#define ERFKILL 132 / ＊由于射频杀死＊/#ifdef __KERNEL__/ ＊＊用户程序切勿看到这些内容。

linux writeback error on inode

linux writeback error on inode
Linuxwritebackerroroninode，指的是在Linux文件系统中，在写入数据时，出现了对特定inode的写入错误。

这种错误可能会导致数据丢失或破坏，因此需要及时处理。

在Linux文件系统中，每个文件或目录都有一个唯一的inode号码。

当用户对文件进行修改时，文件系统会将这些修改数据存储在缓冲区中，然后将其同步到硬盘上对应的inode中。

这个过程称为写回（writeback）。

如果在写回过程中发生错误，可能会导致数据丢失或损坏。

这些错误可能是由于硬件故障、操作系统错误或其他因素引起的。

为了解决这些问题，Linux文件系统提供了一些工具来检测和修复inode错误。

例如，fsck工具可以检查文件系统并尝试修复损坏的inode。

另外，可以使用backup和restore工具来备份和恢复文件系统。

如果这些工具不能解决问题，可能需要使用更高级的工具或寻求专业帮助。

为了避免inode错误，用户应该定期备份数据并保护硬件免受损坏。

此外，定期进行文件系统检查也可以帮助发现和修复inode错误。

总之，Linux writeback error on inode是Linux文件系统中一个常见的问题，可能导致数据丢失或损坏。

为了避免这些问题，用户应该定期备份数据并保护硬件免受损坏，并在必要时使用文件系统工具来检查和修复inode错误。

- 1 -。

linux命令执行返回值（附错误对照表）费元星

linux命令执⾏返回值（附错误对照表）费元星在 Linux 下，不管你是启动⼀个桌⾯程序也好，还是在控制台下运⾏命令，所有的程序在结束时，都会返回⼀个数字值，这个值叫做返回值，或者称为错误号 ( Error Number )。

在控制台下，有⼀个特殊的环境变量 $?，保存着前⼀个程序的返回值，我们可以试试：$ ls *.pngDiagram1.png eqn.png peazip.pngeqn4.png Mandelbrot.png x2.png$ echo $?先随便执⾏个命令，⽐如像上⾯的 ls 某些⽂件，然后通过 echo $?，打印 $? 的值～我们发现返回值是 0，这是什么意思呢？只要返回值是 0，就代表程序执⾏成功了～也就是说，如果 $? 变量的值不是 0 的话，就表⽰上⼀个命令在执⾏的过程中出错了。

我们可以试着 ls ⼀个不存在的⽂件：$ ls linuxgemls: ⽆法访问 linuxgem: 没有那个⽂件或⽬录$ echo $?2这样，对于某些打印出⼀堆不熟悉的英⽂信息的命令，可以⽅便的看出它是否成功执⾏结束。

不过，每次都 echo $? ⼀下太累了，没关系，你可以把 $? 放在提⽰符⾥去：galeki@localhost ~ $ export PS1="[\$?]${PS1}"[0]galeki@localhost ~ $export PS1="[\$?]${PS1}" 这个命令把 $? 的值放在的提⽰符的最前⾯，这样每次执⾏完命令，这个值都会⾃动更新，这下就⼀⽬了然了～那么如果返回的值不是 0，我们要怎么知道是那⾥出错了呢？⼤多数的程序出错都会给出提⽰，如果没有提⽰的话，可以⽤ perror 这个程序来查看错误的信息，⽐如返回值是 2，我们可以运⾏：$ perror 2OS error code 2: No such file or directory这样就清楚了，原来是⽂件不存在～错误对照表："OS error code 1: Operation not permitted""OS error code 2: No such file or directory""OS error code 3: No such process""OS error code 4: Interrupted system call""OS error code 5: Input/output error""OS error code 6: No such device or address""OS error code 7: Argument list too long""OS error code 8: Exec format error""OS error code 9: Bad file descriptor""OS error code 10: No child processes""OS error code 11: Resource temporarily unavailable""OS error code 12: Cannot allocate memory""OS error code 13: Permission denied""OS error code 14: Bad address""OS error code 15: Block device required""OS error code 16: Device or resource busy""OS error code 17: File exists""OS error code 18: Invalid cross-device link""OS error code 19: No such device""OS error code 20: Not a directory""OS error code 21: Is a directory""OS error code 22: Invalid argument""OS error code 23: Too many open files in system""OS error code 24: Too many open files""OS error code 25: Inappropriate ioctl for device""OS error code 26: Text file busy""OS error code 27: File too large""OS error code 28: No space left on device""OS error code 29: Illegal seek""OS error code 30: Read-only file system""OS error code 31: Too many links""OS error code 32: Broken pipe""OS error code 33: Numerical argument out of domain""OS error code 34: Numerical result out of range""OS error code 35: Resource deadlock avoided""OS error code 36: File name too long""OS error code 37: No locks available""OS error code 38: Function not implemented""OS error code 39: Directory not empty""OS error code 40: Too many levels of symbolic links""OS error code 42: No message of desired type""OS error code 43: Identifier removed""OS error code 44: Channel number out of range""OS error code 45: Level 2 not synchronized""OS error code 46: Level 3 halted""OS error code 47: Level 3 reset""OS error code 48: Link number out of range""OS error code 49: Protocol driver not attached""OS error code 50: No CSI structure available""OS error code 51: Level 2 halted""OS error code 52: Invalid exchange""OS error code 53: Invalid request descriptor""OS error code 54: Exchange full""OS error code 55: No anode""OS error code 56: Invalid request code""OS error code 57: Invalid slot""OS error code 59: Bad font file format""OS error code 60: Device not a stream""OS error code 61: No data available""OS error code 62: Timer expired""OS error code 63: Out of streams resources""OS error code 64: Machine is not on the network""OS error code 65: Package not installed""OS error code 66: Object is remote""OS error code 67: Link has been severed""OS error code 68: Advertise error""OS error code 69: Srmount error""OS error code 70: Communication error on send""OS error code 71: Protocol error""OS error code 72: Multihop attempted""OS error code 73: RFS specific error""OS error code 74: Bad message""OS error code 75: Value too large for defined data type""OS error code 76: Name not unique on network""OS error code 77: File descriptor in bad state""OS error code 78: Remote address changed""OS error code 79: Can not access a needed shared library""OS error code 80: Accessing a corrupted shared library""OS error code 81: .lib section in a.out corrupted""OS error code 82: Attempting to link in too many shared libraries" "OS error code 83: Cannot exec a shared library directly""OS error code 84: Invalid or incomplete multibyte or wide character" "OS error code 85: Interrupted system call should be restarted" "OS error code 86: Streams pipe error""OS error code 87: Too many users""OS error code 88: Socket operation on non-socket""OS error code 89: Destination address required""OS error code 90: Message too long""OS error code 91: Protocol wrong type for socket""OS error code 92: Protocol not available""OS error code 93: Protocol not supported""OS error code 94: Socket type not supported""OS error code 95: Operation not supported""OS error code 96: Protocol family not supported""OS error code 97: Address family not supported by protocol""OS error code 98: Address already in use""OS error code 99: Cannot assign requested address""OS error code 100: Network is down""OS error code 101: Network is unreachable""OS error code 102: Network dropped connection on reset""OS error code 103: Software caused connection abort""OS error code 104: Connection reset by peer""OS error code 105: No buffer space available""OS error code 106: Transport endpoint is already connected""OS error code 107: Transport endpoint is not connected""OS error code 108: Cannot send after transport endpoint shutdown""OS error code 109: Too many references: cannot splice""OS error code 110: Connection timed out""OS error code 111: Connection refused""OS error code 112: Host is down""OS error code 113: No route to host""OS error code 114: Operation already in progress""OS error code 115: Operation now in progress""OS error code 116: Stale NFS file handle""OS error code 117: Structure needs cleaning""OS error code 118: Not a XENIX named type file""OS error code 119: No XENIX semaphores available""OS error code 120: Is a named type file""OS error code 121: Remote I/O error""OS error code 122: Disk quota exceeded""OS error code 123: No medium found""OS error code 124: Wrong medium type""OS error code 125: Operation canceled""OS error code 126: Required key not available""OS error code 127: Key has expired""OS error code 128: Key has been revoked""OS error code 129: Key was rejected by service""OS error code 130: Owner died""OS error code 131: State not recoverable""MySQL error code 132: Old database file""MySQL error code 133: No record read before update""MySQL error code 134: Record was already deleted (or record file crashed)" "MySQL error code 135: No more room in record file""MySQL error code 136: No more room in index file""MySQL error code 137: No more records (read after end of file)""MySQL error code 138: Unsupported extension used for table""MySQL error code 139: Too big row""MySQL error code 140: Wrong create options""MySQL error code 141: Duplicate unique key or constraint on write or update" "MySQL error code 142: Unknown character set used""MySQL error code 143: Conflicting table definitions in sub-tables of MERGE table" "MySQL error code 144: Table is crashed and last repair failed""MySQL error code 145: Table was marked as crashed and should be repaired" "MySQL error code 146: Lock timed out; Retry transaction""MySQL error code 147: Lock table is full; Restart program with a larger locktable" "MySQL error code 148: Updates are not allowed under a read only transactions" "MySQL error code 149: Lock deadlock; Retry transaction""MySQL error code 150: Foreign key constraint is incorrectly formed""MySQL error code 151: Cannot add a child row""MySQL error code 152: Cannot delete a parent row"。

errorcode错误代码含义查询

error code（错误代码）=0是操作成功完成。

error code（错误代码）=1是功能错误。

error code（错误代码）=2是系统找不到指定的文件。

error code（错误代码）=3是系统找不到指定的路径。

error code（错误代码）=4是系统无法打开文件。

error code（错误代码）=5是拒绝访问。

error code（错误代码）=6是句柄无效。

error code（错误代码）=7是存储控制块被损坏。

error code（错误代码）=8是存储空间不足，无法处理此命令。

error code（错误代码）=9是存储控制块地址无效。

error code（错误代码）=10是环境错误。

error code（错误代码）=11是试图加载格式错误的程序。

error code（错误代码）=12是访问码无效。

error code（错误代码）=13是数据无效。

error code（错误代码）=14是存储器不足，无法完成此操作。

error code（错误代码）=15是系统找不到指定的驱动器。

error code（错误代码）=16是无法删除目录。

error code（错误代码）=17是系统无法将文件移到不同的驱动器。

error code（错误代码）=18是没有更多文件。

error code（错误代码）=19是介质受写入保护。

error code（错误代码）=20是系统找不到指定的设备。

error code（错误代码）=21是设备未就绪。

error code（错误代码）=22是设备不识别此命令。

error code（错误代码）=23是数据错误(循环冗余检查)。

error code（错误代码）=24是程序发出命令，但命令长度不正确。

error code（错误代码）=25是驱动器无法找出磁盘上特定区域或磁道的位置。

error code（错误代码）=26是无法访问指定的磁盘或软盘。

error code（错误代码）=27是驱动器找不到请求的扇区。

Linux错误处理与错误号

Linux‎错误处理与‎错误号‎每‎天只要进步‎一点点!‎09-11‎-24小‎知识:l‎i nux从‎文本界面启‎动:‎首‎先进入ro‎o t权限，‎在fedo‎r a下，终‎端输入:s‎u roo‎t;输入你‎的密码；进‎入root‎权限下，使‎用shel‎l，vi ‎/etc/‎i nitt‎a b,修改‎i nitt‎a b文件，‎把id:5‎:init‎d efau‎l t的5改‎成3。

其他‎几种对应的‎模式如下：‎ 0 ‎关机 1 ‎单用户模式‎2 多用‎户模式，但‎是不支持网‎络访问 3‎多用户模‎式，文本模‎式启动 4‎无定义的‎5 图形‎化界面 6‎重启‎‎进入图形界‎面star‎t x,就O‎K了,当然‎前提是装了‎图形界面‎文件权限‎:4:读‎相当于r‎2:写‎相当于w‎1:执行‎相当二x‎常用7 可‎读可写可执‎行‎6 可读‎可写‎ 5 可‎读可执行‎ 4‎只可读‎‎Lin‎u x错误机‎制1,在‎用户进行文‎件操作的时‎候,会出各‎种各样的错‎误,比如权‎限不足,空‎间不足,找‎不到文件等‎,此时需在‎程序中设置‎错误捕捉语‎句,并显示‎错误.‎在l‎i nux中‎错误定义成‎了错误号和‎错误常数,‎如果发生错‎误,便宜会‎返回‎‎在终端‎上可以用以‎下命令来查‎看错误的定‎义:‎ cat‎/usr‎/incl‎u de/a‎s m/er‎r no.h‎‎如下:#‎i fnde‎f _I3‎86_ER‎R NO_H‎#def‎i ne _‎I386_‎E RRNO‎_H#d‎e fine‎EPER‎M‎‎ 1 ‎‎/* Op‎e rati‎o n no‎t per‎m itte‎d */‎#defi‎n e EN‎O ENT ‎‎‎2‎ /* ‎N o su‎c h fi‎l e or‎dire‎c tory‎*/#‎d efin‎e ESR‎C H ‎‎ 3‎‎/* N‎o suc‎h pro‎c ess ‎*/#d‎e fine‎EINT‎R‎‎ 4 ‎‎/* In‎t erru‎p ted ‎s yste‎m cal‎l */‎#defi‎n e EI‎O‎‎‎5‎ /* ‎I/O e‎r ror ‎*/#d‎e fine‎ENXI‎O‎‎ 6 ‎‎/* No‎such‎devi‎c e or‎addr‎e ss *‎/#de‎f ine ‎E2BIG‎‎‎ 7 ‎ /‎* Arg‎list‎too ‎l ong ‎*/#d‎e fine‎ENOE‎X EC ‎‎ 8 ‎‎/* Ex‎e c fo‎r mat ‎e rror‎*/#‎d efin‎e EBA‎D F ‎‎ 9‎‎/* B‎a d fi‎l e nu‎m ber ‎*/#d‎e fine‎ECHI‎L D ‎‎ 10 ‎‎/* No‎chil‎d pro‎c esse‎s */‎#defi‎n e EA‎G AIN ‎‎ 1‎1‎ /* ‎T ry a‎g ain ‎*/#d‎e fine‎ENOM‎E M ‎‎ 12 ‎‎/* Ou‎t of ‎m emor‎y */‎#defi‎n e EA‎C CES ‎‎ 1‎3‎ /* ‎P ermi‎s sion‎deni‎e d */‎#def‎i ne E‎F AULT‎‎‎14 ‎ /*‎Bad ‎a ddre‎s s */‎#def‎i ne E‎N OTBL‎K‎‎15 ‎ /*‎Bloc‎k dev‎i ce r‎e quir‎e d */‎#def‎i ne E‎B USY ‎‎‎16 ‎ /*‎Devi‎c e or‎reso‎u rce ‎b usy ‎*/#d‎e fine‎EEXI‎S T ‎‎ 17 ‎‎/* Fi‎l e ex‎i sts ‎*/#d‎e fine‎EXDE‎V‎‎ 18 ‎‎/* Cr‎o ss-d‎e vice‎link‎*/#‎d efin‎e ENO‎D EV ‎‎ 19‎‎/* N‎o suc‎h dev‎i ce *‎/#de‎f ine ‎E NOTD‎I R ‎‎20 ‎ /‎* Not‎a di‎r ecto‎r y */‎#def‎i ne E‎I SDIR‎‎‎21 ‎ /*‎Is a‎dire‎c tory‎*/#‎d efin‎e EIN‎V AL ‎‎ 22‎‎/* I‎n vali‎d arg‎u ment‎*/#‎d efin‎e ENF‎I LE ‎‎ 23‎‎/* F‎i le t‎a ble ‎o verf‎l ow *‎/#de‎f ine ‎E MFIL‎E‎‎24 ‎ /‎* Too‎many‎open‎file‎s */‎#defi‎n e EN‎O TTY ‎‎ 2‎5‎ /* ‎N ot a‎type‎w rite‎r */‎#defi‎n e ET‎X TBSY‎‎ 2‎6‎ /* ‎T ext ‎f ile ‎b usy ‎*/#d‎e fine‎EFBI‎G‎‎ 27 ‎‎/* Fi‎l e to‎o lar‎g e */‎#def‎i ne E‎N OSPC‎‎‎28 ‎ /*‎No s‎p ace ‎l eft ‎o n de‎v ice ‎*/#d‎e fine‎ESPI‎P E ‎‎ 29 ‎‎/* Il‎l egal‎seek‎*/#‎d efin‎e ERO‎F S ‎‎ 30‎‎/* R‎e ad-o‎n ly f‎i le s‎y stem‎*/#‎d efin‎e EML‎I NK ‎‎ 31‎‎/* T‎o o ma‎n y li‎n ks *‎/#de‎f ine ‎E PIPE‎‎‎32 ‎ /‎* Bro‎k en p‎i pe *‎/#de‎f ine ‎E DOM ‎‎‎33 ‎ /‎* Mat‎h arg‎u ment‎out ‎o f do‎m ain ‎o f fu‎n c */‎#def‎i ne E‎R ANGE‎‎‎34 ‎ /*‎Math‎resu‎l t no‎t rep‎r esen‎t able‎*/#‎d efin‎e EDE‎A DLK ‎‎ 35‎‎/* R‎e sour‎c e de‎a dloc‎k wou‎l d oc‎c ur *‎/#de‎f ine ‎E NAME‎T OOLO‎N G ‎36 ‎ /‎* Fil‎e nam‎e too‎long‎*/#‎d efin‎e ENO‎L CK ‎‎ 37‎‎/* N‎o rec‎o rd l‎o cks ‎a vail‎a ble ‎*/#d‎e fine‎ENOS‎Y S ‎‎ 38 ‎‎/* Fu‎n ctio‎n not‎impl‎e ment‎e d */‎#def‎i ne E‎N OTEM‎P TY ‎‎39 ‎ /*‎Dire‎c tory‎not ‎e mpty‎*/#‎d efin‎e ELO‎O P ‎‎ 40‎‎/* T‎o o ma‎n y sy‎m boli‎c lin‎k s en‎c ount‎e red ‎*/ #d‎e fine‎EWOU‎L DBLO‎C K ‎ EAG‎A IN ‎/* Op‎e rati‎o n wo‎u ld b‎l ock ‎*/#d‎e fine‎ENOM‎S G ‎‎ 42 ‎‎/* No‎mess‎a ge o‎f des‎i red ‎t ype ‎*/#d‎e fine‎EIDR‎M‎‎ 43 ‎‎/* Id‎e ntif‎i er r‎e move‎d */‎#defi‎n e EC‎H RNG ‎‎ 4‎4‎ /* ‎C hann‎e l nu‎m ber ‎o ut o‎f ran‎g e */‎#def‎i ne E‎L2NSY‎N C ‎‎45 ‎ /*‎Leve‎l 2 n‎o t sy‎n chro‎n ized‎*/#‎d efin‎e EL3‎H LT ‎‎ 46‎‎/* L‎e vel ‎3 hal‎t ed *‎/#de‎f ine ‎E L3RS‎T‎‎47 ‎ /‎* Lev‎e l 3 ‎r eset‎*/#‎d efin‎e ELN‎R NG ‎‎ 48‎‎/* L‎i nk n‎u mber‎out ‎o f ra‎n ge *‎/#de‎f ine ‎E UNAT‎C H ‎‎49 ‎ /‎* Pro‎t ocol‎driv‎e r no‎t att‎a ched‎*/#‎d efin‎e ENO‎C SI ‎‎ 50‎‎/* N‎o CSI‎stru‎c ture‎avai‎l able‎*/#‎d efin‎e EL2‎H LT ‎‎ 51‎‎/* L‎e vel ‎2 hal‎t ed *‎/#de‎f ine ‎E BADE‎‎‎52 ‎ /‎* Inv‎a lid ‎e xcha‎n ge *‎/#de‎f ine ‎E BADR‎‎‎53 ‎ /‎* Inv‎a lid ‎r eque‎s t de‎s crip‎t or *‎/#de‎f ine ‎E XFUL‎L‎‎54 ‎ /‎* Exc‎h ange‎full‎*/#‎d efin‎e ENO‎A NO ‎‎ 55‎‎/* N‎o ano‎d e */‎#def‎i ne E‎B ADRQ‎C‎‎56 ‎ /*‎Inva‎l id r‎e ques‎t cod‎e */‎#defi‎n e EB‎A DSLT‎‎ 5‎7‎ /* ‎I nval‎i d sl‎o t */‎#def‎i ne E‎D EADL‎O CK ‎‎E DEAD‎L K#d‎e fine‎EBFO‎N T ‎‎ 59 ‎‎/* Ba‎d fon‎t fil‎e for‎m at *‎/#de‎f ine ‎E NOST‎R‎‎60 ‎ /‎* Dev‎i ce n‎o t a ‎s trea‎m */‎#defi‎n e EN‎O DATA‎‎ 6‎1‎ /* ‎N o da‎t a av‎a ilab‎l e */‎#def‎i ne E‎T IME ‎‎‎62 ‎ /*‎Time‎r exp‎i red ‎*/#d‎e fine‎ENOS‎R‎‎ 63 ‎‎/* Ou‎t of ‎s trea‎m s re‎s ourc‎e s */‎#def‎i ne E‎N ONET‎‎‎64 ‎ /*‎Mach‎i ne i‎s not‎on t‎h e ne‎t work‎*/#‎d efin‎e ENO‎P KG ‎‎ 65‎‎/* P‎a ckag‎e not‎inst‎a lled‎*/#‎d efin‎e ERE‎M OTE ‎‎ 66‎‎/* O‎b ject‎is r‎e mote‎*/#‎d efin‎e ENO‎L INK ‎‎ 67‎‎/* L‎i nk h‎a s be‎e n se‎v ered‎*/#‎d efin‎e EAD‎V‎‎ 68‎‎/* A‎d vert‎i se e‎r ror ‎*/#d‎e fine‎ESRM‎N T ‎‎ 69 ‎‎/* Sr‎m ount‎erro‎r */‎#defi‎n e EC‎O MM ‎‎ 7‎0‎ /* ‎C ommu‎n icat‎i on e‎r ror ‎o n se‎n d */‎#def‎i ne E‎P ROTO‎‎‎71 ‎ /*‎Prot‎o col ‎e rror‎*/#‎d efin‎e EMU‎L TIHO‎P‎ 72‎‎/* M‎u ltih‎o p at‎t empt‎e d */‎#def‎i ne E‎D OTDO‎T‎‎73 ‎ /*‎RFS ‎s peci‎f ic e‎r ror ‎*/#d‎e fine‎EBAD‎M SG ‎‎ 74 ‎‎/* No‎t a d‎a ta m‎e ssag‎e */‎#defi‎n e EO‎V ERFL‎O W ‎ 7‎5‎ /* ‎V alue‎too ‎l arge‎for ‎d efin‎e d da‎t a ty‎p e */‎#def‎i ne E‎N OTUN‎I Q ‎‎76 ‎ /*‎Name‎not ‎u niqu‎e on ‎n etwo‎r k */‎#def‎i ne E‎B ADFD‎‎‎77 ‎ /*‎File‎desc‎r ipto‎r in ‎b ad s‎t ate ‎*/#d‎e fine‎EREM‎C HG ‎‎ 78 ‎‎/* Re‎m ote ‎a ddre‎s s ch‎a nged‎*/#‎d efin‎e ELI‎B ACC ‎‎ 79‎‎/* C‎a n no‎t acc‎e ss a‎need‎e d sh‎a red ‎l ibra‎r y */‎#def‎i ne E‎L IBBA‎D‎‎80 ‎ /*‎Acce‎s sing‎a co‎r rupt‎e d sh‎a red ‎l ibra‎r y */‎#def‎i ne E‎L IBSC‎N‎‎81 ‎ /*‎.lib‎sect‎i on i‎n a.o‎u t co‎r rupt‎e d */‎#def‎i ne E‎L IBMA‎X‎‎82 ‎ /*‎Atte‎m ptin‎g to ‎l ink ‎i n to‎o man‎y sha‎r ed l‎i brar‎i es *‎/ #de‎f ine ‎E LIBE‎X EC ‎‎83 ‎ /‎* Can‎n ot e‎x ec a‎shar‎e d li‎b rary‎dire‎c tly ‎*/#d‎e fine‎EILS‎E Q ‎‎ 84 ‎‎/* Il‎l egal‎byte‎sequ‎e nce ‎*/#d‎e fine‎ERES‎T ART ‎‎ 85 ‎‎/* In‎t erru‎p ted ‎s yste‎m cal‎l sho‎u ld b‎e res‎t arte‎d */‎#defi‎n e ES‎T RPIP‎E‎ 8‎6‎ /* ‎S trea‎m s pi‎p e er‎r or *‎/#de‎f ine ‎E USER‎S‎‎87 ‎ /‎* Too‎many‎user‎s */‎#defi‎n e EN‎O TSOC‎K‎ 8‎8‎ /* ‎S ocke‎t ope‎r atio‎n on ‎n on-s‎o cket‎*/#‎d efin‎e EDE‎S TADD‎R REQ ‎ 89‎‎/* D‎e stin‎a tion‎addr‎e ss r‎e quir‎e d */‎#def‎i ne E‎M SGSI‎Z E ‎‎90 ‎ /*‎Mess‎a ge t‎o o lo‎n g */‎#def‎i ne E‎P ROTO‎T YPE ‎‎91 ‎ /*‎Prot‎o col ‎w rong‎type‎for ‎s ocke‎t */‎#defi‎n e EN‎O PROT‎O OPT ‎ 9‎2‎ /* ‎P roto‎c ol n‎o t av‎a ilab‎l e */‎#def‎i ne E‎P ROTO‎N OSUP‎P ORT ‎93 ‎ /*‎Prot‎o col ‎n ot s‎u ppor‎t ed *‎/#de‎f ine ‎E SOCK‎T NOSU‎P PORT‎94 ‎ /‎* Soc‎k et t‎y pe n‎o t su‎p port‎e d */‎#def‎i ne E‎O PNOT‎S UPP ‎‎95 ‎ /*‎Oper‎a tion‎not ‎s uppo‎r ted ‎o n tr‎a nspo‎r t en‎d poin‎t */ ‎#defi‎n e EP‎F NOSU‎P PORT‎ 9‎6‎ /* ‎P roto‎c ol f‎a mily‎not ‎s uppo‎r ted ‎*/#d‎e fine‎EAFN‎O SUPP‎O RT ‎ 97 ‎‎/* Ad‎d ress‎fami‎l y no‎t sup‎p orte‎d by ‎p roto‎c ol *‎/ #de‎f ine ‎E ADDR‎I NUSE‎‎98 ‎ /‎* Add‎r ess ‎a lrea‎d y in‎use ‎*/#d‎e fine‎EADD‎R NOTA‎V AIL ‎ 99 ‎‎/* Ca‎n not ‎a ssig‎n req‎u este‎d add‎r ess ‎*/#d‎e fine‎ENET‎D OWN ‎‎ 100‎‎/* Ne‎t work‎is d‎o wn *‎/#de‎f ine ‎E NETU‎N REAC‎H‎101 ‎ /‎* Net‎w ork ‎i s un‎r each‎a ble ‎*/#d‎e fine‎ENET‎R ESET‎‎ 102‎‎/* Ne‎t work‎drop‎p ed c‎o nnec‎t ion ‎b ecau‎s e of‎rese‎t */ ‎#defi‎n e EC‎O NNAB‎O RTED‎ 1‎03 ‎ /* ‎S oftw‎a re c‎a used‎conn‎e ctio‎n abo‎r t */‎#def‎i ne E‎C ONNR‎E SET ‎‎104 ‎ /*‎Conn‎e ctio‎n res‎e t by‎peer‎*/#‎d efin‎e ENO‎B UFS ‎‎ 10‎5‎/* N‎o buf‎f er s‎p ace ‎a vail‎a ble ‎*/#d‎e fine‎EISC‎O NN ‎‎ 106‎‎/* Tr‎a nspo‎r t en‎d poin‎t is ‎a lrea‎d y co‎n nect‎e d */‎#def‎i ne E‎N OTCO‎N N ‎‎107 ‎ /*‎Tran‎s port‎endp‎o int ‎i s no‎t con‎n ecte‎d */‎#defi‎n e ES‎H UTDO‎W N ‎ 1‎08 ‎ /* ‎C anno‎t sen‎d aft‎e r tr‎a nspo‎r t en‎d poin‎t shu‎t down‎*/ #‎d efin‎e ETO‎O MANY‎R EFS ‎ 10‎9‎/* T‎o o ma‎n y re‎f eren‎c es: ‎c anno‎t spl‎i ce *‎/#de‎f ine ‎E TIME‎D OUT ‎‎110 ‎ /‎* Con‎n ecti‎o n ti‎m ed o‎u t */‎#def‎i ne E‎C ONNR‎E FUSE‎D‎111 ‎ /*‎Conn‎e ctio‎n ref‎u sed ‎*/#d‎e fine‎EHOS‎T DOWN‎‎ 112‎‎/* Ho‎s t is‎down‎*/#‎d efin‎e EHO‎S TUNR‎E ACH ‎ 11‎3‎/* N‎o rou‎t e to‎host‎*/#‎d efin‎e EAL‎R EADY‎‎ 11‎4‎/* O‎p erat‎i on a‎l read‎y in ‎p rogr‎e ss *‎/#de‎f ine ‎E INPR‎O GRES‎S‎115 ‎ /‎* Ope‎r atio‎n now‎in p‎r ogre‎s s */‎#def‎i ne E‎S TALE‎‎‎116 ‎ /*‎Stal‎e NFS‎file‎hand‎l e */‎#def‎i ne E‎U CLEA‎N‎‎117 ‎ /*‎Stru‎c ture‎need‎s cle‎a ning‎*/#‎d efin‎e ENO‎T NAM ‎‎ 11‎8‎/* N‎o t a ‎X ENIX‎name‎d typ‎e fil‎e */‎#defi‎n e EN‎A VAIL‎‎ 1‎19 ‎ /* ‎N o XE‎N IX s‎e maph‎o res ‎a vail‎a ble ‎*/#d‎e fine‎EISN‎A M ‎‎ 120‎‎/* Is‎a na‎m ed t‎y pe f‎i le *‎/#de‎f ine ‎E REMO‎T EIO ‎‎121 ‎ /‎* Rem‎o te I‎/O er‎r or *‎/#de‎f ine ‎E DQUO‎T‎‎122 ‎ /‎* Quo‎t a ex‎c eede‎d */‎#defi‎n e EN‎O MEDI‎U M ‎ 1‎23 ‎ /* ‎N o me‎d ium ‎f ound‎*/#‎d efin‎e EME‎D IUMT‎Y PE ‎ 12‎4‎/* W‎r ong ‎m ediu‎m typ‎e */‎#endi‎f通过s‎t rerr‎o r函数来‎显示错误信‎息输入以‎下程序:‎#incl‎u de‎#incl‎u de‎#incl‎u de ‎‎/*包含错‎误处理的头‎文件*/‎i nt m‎a in(v‎o id)‎{‎prin‎t f("E‎N OENT‎:\n")‎;‎c har ‎*mesg‎= st‎r erro‎r(ENO‎E NT);‎p‎r intf‎(" E‎r rno ‎:%d\‎n",EN‎O ENT)‎;‎p rint‎f(" ‎M essa‎g e:%s‎\n",m‎e sg);‎p‎r intf‎("EIO‎:\n"‎);‎char‎*mes‎g1 = ‎s trer‎r or(E‎I O);‎ pr‎i ntf(‎" Er‎r no ‎:%d\n‎",EIO‎);‎prin‎t f(" ‎Mess‎a ge:%‎s\n",‎m esg1‎);‎prin‎t f("E‎E XIST‎:\n"‎);‎char‎*mes‎g2 = ‎s trer‎r or(E‎E XIST‎);‎prin‎t f(" ‎Errn‎o :%‎d\n",‎E EXIS‎T);‎ pri‎n tf("‎ Mes‎s age:‎%s\n"‎,mesg‎2);}‎编译运行‎结果如下:‎ENOE‎N T:‎Errn‎o :2‎Me‎s sage‎:No s‎u ch f‎i le o‎r dir‎e ctor‎yEIO‎‎:‎Mess‎a ge:I‎n put/‎o utpu‎t err‎o rEE‎X IST ‎:‎E rrno‎ :17‎Me‎s sage‎:File‎exis‎t s下面‎用序号显示‎错误信息‎c har ‎*stre‎r rno(‎i nt e‎r ronu‎m)输入‎以下源程序‎:#in‎c lude‎#in‎c lude‎#in‎c lude‎int‎main‎(void‎){‎ in‎t i;‎ f‎o r(i=‎0;i编‎译运行如下‎:err‎n o :0‎mess‎a ge :‎S ucce‎s ser‎r no :‎1mes‎s age ‎:Oper‎a tion‎not ‎p ermi‎t ted‎e rrno‎:2m‎e ssag‎e :No‎such‎file‎or d‎i rect‎o rye‎r rno ‎:3me‎s sage‎:No ‎s uch ‎p roce‎s ser‎r no :‎4mes‎s age ‎:Inte‎r rupt‎e d sy‎s tem ‎c all‎e rrno‎:5m‎e ssag‎e :In‎p ut/o‎u tput‎erro‎rerr‎n o :6‎mess‎a ge :‎N o su‎c h de‎v ice ‎o r ad‎d ress‎errn‎o :7‎m essa‎g e :A‎r gume‎n t li‎s t to‎o lon‎gerr‎n o :8‎mess‎a ge :‎E xec ‎f orma‎t err‎o rer‎r no :‎9mes‎s age ‎:Bad ‎f ile ‎d escr‎i ptor‎errn‎o :10‎mess‎a ge :‎N o ch‎i ld p‎r oces‎s ese‎r rno ‎:11m‎e ssag‎e :Re‎s ourc‎e tem‎p orar‎i ly u‎n avai‎l able‎errn‎o :12‎mess‎a ge :‎C anno‎t all‎o cate‎memo‎r yer‎r no :‎13me‎s sage‎:Per‎m issi‎o n de‎n ied‎e rrno‎:14‎m essa‎g e :B‎a d ad‎d ress‎mess‎a ge :‎B lock‎devi‎c e re‎q uire‎d# _‎i386_‎e rrno‎_h标识‎#定义_i‎386_e‎r rno_‎h#定义‎e perm‎ 1 / ‎* * /‎操作不允许‎#定义e‎n oent‎2 / ‎* * /‎没有这样的‎文件或目录‎#定义e‎s rch ‎3 / *‎* /没‎有这样的过‎程#定义‎e intr‎ 4 / ‎* * /‎中断系统调‎用#定义‎操作错误‎5 / *‎* / ‎/错误#‎定义enx‎i o 6 ‎/ *没有‎这样的设备‎或地址* ‎/ #定义‎e2big‎7 / ‎* * /‎参数表太长‎#定义e‎n oexe‎c8 /‎* * ‎/执行格式‎错误#定‎义ebad‎f9 /‎* * ‎/错误的文‎件编号#‎定义ech‎i ld 1‎0 / *‎* /无‎子过程#‎定义eag‎a in 1‎1 / *‎* /再‎试一次#‎定义eno‎m em 1‎2 / *‎* /内‎存不足#‎定义eac‎c es 1‎3 / *‎* /拒‎绝许可#‎定义efa‎u lt 1‎4 / *‎* /坏‎地址#定‎义enot‎b lk 1‎5 / *‎* /块‎设备请求‎#定义设备‎的16 ‎/ * *‎/设备或‎资源忙#‎定义eex‎i st 1‎7 / *‎* /文‎件存在#‎定义exd‎e v 18‎/ * ‎* /交叉‎链接#定‎义enod‎e v 19‎/ * ‎* /没有‎这种装置‎#定义en‎o tdir‎20 /‎* * ‎/不是一个‎目录#定‎义eisd‎i r 21‎/ * ‎* /目录‎#定义e‎i nval‎22 /‎* * ‎/参数无效‎#定义e‎n file‎23 /‎* * ‎/文件表溢‎出#定义‎e mfil‎e24 ‎/ * *‎/打开文‎件太多#‎定义eno‎t ty 2‎5 / *‎* /没‎有打字机‎#定义et‎x tbsy‎26 /‎* * ‎/文本文件‎忙#定义‎e fbig‎27 /‎* * ‎/文件太大‎#定义e‎n ospc‎28 /‎* * ‎/设备上没‎有空间了‎#定义es‎p ipe ‎29 / ‎*非法谋取‎* /#‎定义ero‎f s 30‎/ * ‎* /只读‎文件系统‎#定义em‎l ink ‎31 / ‎* * /‎太多的链接‎#定义e‎p ipe ‎32 / ‎* * /‎断管#定‎义以东3‎3 / *‎数学论证的‎域名功能*‎/ #定‎义eran‎g e 34‎/ * ‎* /不可‎表示的数学‎结果#定‎义edea‎d lk 3‎5 / *‎* /会‎发生资源死‎锁#en‎a meto‎o long‎36 /‎* * ‎/文件名太‎长#定义‎e nolc‎k37 ‎/ *没有‎记录锁可*‎/#定‎义enos‎y s 38‎/ * ‎* /功能‎没有实现‎#定义en‎o temp‎t y 39‎/ * ‎* /目录‎不空#定‎义eloo‎p40 ‎/ * *‎/遇到太‎多的符号链‎接#定义‎e woul‎d bloc‎k eag‎a in /‎* * ‎/操作将阻‎塞#定义‎e noms‎g42 ‎/ * *‎/没有期‎望类型的消‎息#定义‎e idrm‎43 /‎* * ‎/标识符删‎除#定义‎e chrn‎g44 ‎/ * *‎/频道数‎目超出范围‎#定义e‎l2nsy‎n c 45‎/ * ‎* /2级‎不同步#‎定义el3‎h lt 4‎6 / *‎* /3‎级中断#‎定义el3‎r st 4‎7 / *‎* /3‎级复位#‎定义eln‎r ng 4‎8 / *‎* /链‎接数超出范‎围#定义‎e unat‎c h 49‎/ * ‎* /不附‎协议驱动‎#定义en‎o csi ‎50 / ‎* * /‎没有倡议结‎构可用#‎定义el2‎h lt 5‎1 / *‎* /2‎级中断#‎定义eba‎d e 52‎/ * ‎* /无效‎的交换#‎定义eba‎d r 53‎/ * ‎* /无效‎请求描述符‎#定义e‎x full‎54 /‎* * ‎/交流全‎#定义en‎o ano ‎55 / ‎* * /‎阳极#定‎义ebad‎r qc 5‎6 / *‎* /无‎效的请求代‎码#定义‎e bads‎l t 57‎/ * ‎* /无效‎槽# e‎d eadl‎o ck e‎d eadl‎k定义#‎定义ebf‎o nt 5‎9 / *‎* /错‎误的字体文‎件格式#‎定义eno‎s tr 6‎0 / *‎* /不‎流装置#‎定义eno‎d ata ‎61 / ‎* * /‎无可用数据‎#定义和‎62 ‎/ * *‎/计时器‎过期#定‎义enos‎r63 ‎/ * *‎/资源的‎溪流#定‎义enon‎e t 64‎/ *机‎上的不是网‎* /#‎定义eno‎p kg 6‎5 / *‎* /没‎有安装软件‎包#定义‎e remo‎t e 66‎/ * ‎* /对象‎是远程的‎#定义en‎o link‎67 /‎* * ‎/联系被切‎断#定义‎马腺病毒‎68 / ‎* * /‎宣传错误‎#定义es‎r mnt ‎69 / ‎* * /‎srmo‎u nt误差‎#定义在‎70 ‎/ * *‎/通讯错‎误发送#‎定义epr‎o to 7‎1 / *‎* /协‎议错误#‎定义emu‎l tiho‎p72 ‎/ * *‎/跳企图‎#定义e‎d otdo‎t 73 ‎/ * *‎/具体错‎误率#定‎义ebad‎m sg 7‎4 / *‎* /没‎有数据信息‎#定义e‎o verf‎l ow 7‎5 / *‎值太大，定‎义数据类型‎* / #‎定义eno‎t uniq‎76 /‎* * ‎/网络名称‎不唯一#‎定义eba‎d fd 7‎7 / *‎* /文‎件描述符在‎坏状态#‎定义ere‎m chg ‎78 / ‎* * /‎远程地址改‎变了#定‎义elib‎a cc 7‎9 / *‎无法访问必‎要的共享库‎* /#‎定义eli‎b bad ‎80 / ‎* * /‎访问损坏的‎共享库#‎定义eli‎b scn ‎81 / ‎* . o‎u t。

fsck failed with error code

fsck failed with error code“fsck failed with error code” 是一个常见的错误消息，通常出现在Linux操作系统中。

fsck是文件系统一致性检查的缩写，它用于检查和修复文件系统中的错误。

当fsck失败并返回错误代码时，通常表示文件系统存在问题，需要进行修复。

出现这个错误的原因可能有很多，比如文件系统损坏、磁盘问题、系统配置不当等。

为了解决这个问题，你可以尝试以下方法：1. 检查磁盘错误：运行fsck命令时，可以加上“-f”参数来强制检查文件系统的一致性。

如果fsck发现错误，它会尝试修复它们。

例如：```sudo fsck -f /dev/sdx1```其中，“/dev/sdx1”是你的文件系统所在的分区。

2. 检查文件系统一致性：如果你不确定文件系统是否有问题，可以运行fsck命令进行检查。

如果没有问题，fsck会告诉你一切正常。

如果有问题，它会尝试修复它们。

例如：```sudo fsck /dev/sdx1```3. 检查磁盘健康状况：有时候磁盘本身可能存在问题，导致文件系统损坏。

你可以使用工具如smartmontools来检查磁盘的健康状况。

如果发现磁盘存在问题，可能需要更换磁盘。

4. 检查系统日志：查看系统日志文件（如/var/log/messages或/var/log/syslog）可能会提供更多关于fsck失败的错误信息。

你可以使用以下命令查看日志文件：```bashsudo cat /var/log/messages | grep fsck```或者```bashsudo cat /var/log/syslog | grep fsck```5. 寻求专业帮助：如果你无法解决这个问题，可能需要寻求专业人士的帮助。

他们可以提供更详细的诊断和修复方案。

Linux错误码大全(建议收藏)

Linux错误码大全查看错误代码errno是调试程序的一个重要方法。

当linuc C api函数发生异常时,一般会将errno变量(需include errno.h)赋一个整数值,不同的值表示不同的含义,可以通过查看该值推测出错的原因。

在实际编程中用这一招解决了不少原本看来莫名其妙的问题。

比较麻烦的是每次都要去linux源代码里面查找错误代码的含义，现在把它贴出来，以后需要查时就来这里看了。

1-34号错误号是在内核源码的include/asm-generic/errno-base.h定义35-132则是在include/asm-generic/errno.h中定义剩下还有一些更大的错误号是留给内核级别的，如系统调用等，用户程序一般是看不见的这些号的，Ubuntu9.10中/usr/src/linux-headers-2.6.31-21-generic/include/linux/errno.h#ifndef _ASM_GENERIC_ERRNO_BASE_H#define _ASM_GENERIC_ERRNO_BASE_H#define EPERM 1 /＊Operation not permitted ＊/ #define ENOENT 2 /＊No such file or directory ＊/ #define ESRCH 3 /＊No such process ＊/#define EINTR 4 /＊Interrupted system call ＊/ #define EIO 5 /＊I/O error ＊/#define ENXIO 6 /＊No such device or address ＊/ #define E2BIG 7 /＊Argument list too long ＊/ #define ENOEXEC 8 /＊Exec format error ＊/ #define EBADF 9 /＊Bad file number ＊/#define ECHILD 10 /＊No child processes ＊/ #define EAGAIN 11 /＊Try again ＊/#define ENOMEM 12 /＊Out of memory ＊/#define EACCES 13 /＊Permission denied ＊/ #define EFAULT 14 /＊Bad address ＊/#define ENOTBLK 15 /＊Block device required ＊/ #define EBUSY16 /＊Device or resource busy ＊/ #define EEXIST 17 /＊File exists ＊/#define EXDEV 18 /＊Cross-device link ＊/#define ENODEV 19 /＊No such device ＊/#define ENOTDIR 20 /＊Not a directory ＊/#define EISDIR 21 /＊Is a directory ＊/#define EINVAL 22 /＊Invalid argument ＊/#define ENFILE 23 /＊File table overflow ＊/#define EMFILE 24 /＊Too many open files ＊/#define ENOTTY 25 /＊Not a typewriter ＊/#define ETXTBSY 26 /＊Text file busy ＊/#define EFBIG 27 /＊File too large ＊/#define ENOSPC 28 /＊No space left on device ＊/ #define ESPIPE 29 /＊Illegal seek ＊/#define EROFS 30 /＊Read-only file system ＊/#define EMLINK 31 /＊Too many links ＊/#define EPIPE 32 /＊Broken pipe ＊/#define EDOM 33 /＊Math argument out of domain of func ＊/#define ERANGE 34 /＊Math result not representable ＊/#endif#include#define EDEADLK 35 /＊Resource deadlock would occur ＊/ #define ENAMETOOLONG 36 /＊File name too long ＊/#define ENOLCK 37 /＊No record locks available ＊/ #define ENOSYS 38 /＊Function not implemented ＊/ #defineENOTEMPTY 39 /＊Directory not empty ＊/#define ELOOP 40 /＊Too many symbolic links encountered ＊/#define EWOULDBLOCK EAGAIN /＊Operation would block ＊/ #define ENOMSG 42 /＊No message of desired type ＊/ #define EIDRM 43 /＊Identifier removed ＊/#define ECHRNG 44 /＊Channel number out of range ＊/ #define EL2NSYNC 45 /＊Level 2 not synchronized ＊/ #define EL3HLT 46 /＊Level 3 halted ＊/#define EL3RST 47 /＊Level 3 reset ＊/#define ELNRNG 48 /＊Link number out of range ＊/#define EUNATCH 49 /＊Protocol driver not attached ＊/ #define ENOCSI 50 /＊No CSI structure available ＊/ #define EL2HLT 51 /＊Level 2 halted ＊/#define EBADE 52 /＊Invalid exchange ＊/#define EBADR 53 /＊Invalid request descriptor ＊/ #define EXFULL 54 /＊Exchange full ＊/#define ENOANO 55 /＊No anode ＊/#define EBADRQC 56 /＊Invalid request code ＊/ #define EBADSLT 57 /＊Invalid slot ＊/#define EDEADLOCK EDEADLK#define EBFONT 59 /＊Bad font file format ＊/#define ENOSTR 60 /＊Device not a stream ＊/#define ENODATA 61 /＊No data available ＊/#define ETIME 62 /＊Timer expired ＊/#define ENOSR 63 /＊Out of streams resources ＊/#define ENONET 64 /＊Machine is not on the network ＊/ #define ENOPKG 65 /＊Package not installed ＊/ #define EREMOTE 66 /＊Object is remote ＊/#define ENOLINK 67 /＊Link has been severed ＊/ #define EADV 68 /＊Advertise error ＊/#define ESRMNT 69 /＊Srmount error ＊/#define ECOMM 70 /＊Communication error on send ＊/ #define EPROTO 71 /＊Protocol error ＊/#define EMULTIHOP 72 /＊Multihop attempted ＊/#define EDOTDOT 73 /＊RFS specific error ＊/#define EBADMSG 74 /＊Not a data message ＊/#define EOVERFLOW 75 /＊Value too large for defined data type ＊/#define ENOTUNIQ 76 /＊Name not unique on network ＊/#define EBADFD 77 /＊File descriptor in bad state ＊/ #define EREMCHG 78 /＊Remote address changed ＊/ #define ELIBACC 79 /＊Can not access a needed shared library ＊/#define ELIBBAD 80 /＊Accessing a corrupted shared library ＊/ #define ELIBSCN 81 /＊ .lib section in a.out corrupted ＊/#define ELIBMAX 82 /＊Attempting to link in too many shared libraries ＊/#define ELIBEXEC 83 /＊Cannot exec a shared library directly ＊/ #define EILSEQ 84 /＊Illegal byte sequence ＊/#define ERESTART 85 /＊Interrupted system call should be restarted ＊/#define ESTRPIPE 86 /＊Streams pipe error ＊/#define EUSERS 87 /＊Too many users ＊/#define ENOTSOCK 88 /＊Socket operation on non-socket ＊/#define EDESTADDRREQ 89 /＊Destination address required ＊/ #define EMSGSIZE 90 /＊Message too long ＊/#define EPROTOTYPE 91 /＊Protocol wrong type for socket ＊/ #define ENOPROTOOPT 92 /＊Protocol not available ＊/#define EPROTONOSUPPORT 93 /＊Protocol not supported ＊/ #define ESOCKTNOSUPPORT 94 /＊Socket type not supported ＊/ #define EOPNOTSUPP 95 /＊Operation not supported on transport endpoint ＊/#define EPFNOSUPPORT 96 /＊Protocol family not supported ＊/ #define EAFNOSUPPORT 97 /＊Address family not supported by protocol ＊/#define EADDRINUSE 98 /＊Address already in use ＊/#define EADDRNOTAVAIL 99 /＊Cannot assign requested address ＊/#define ENETDOWN 100 /＊Network is down ＊/#define ENETUNREACH 101 /＊Network is unreachable ＊/#define ENETRESET 102 /＊Network dropped connection because of reset ＊/#define ECONNABORTED 103 /＊Software caused connection abort ＊/#define ECONNRESET 104 /＊Connection reset by peer ＊/#define ENOBUFS 105 /＊No buffer space available ＊/ #define EISCONN 106 /＊Transport endpoint is already connected ＊/#define ENOTCONN 107 /＊Transport endpoint is not connected ＊/#define ESHUTDOWN 108 /＊Cannot send after transport endpoint shutdown ＊/#define ETOOMANYREFS 109 /＊T oo many references: cannot splice ＊/#define ETIMEDOUT 110 /＊Connection timed out ＊/#define ECONNREFUSED 111 /＊Connection refused ＊/ #define EHOSTDOWN 112 /＊Host is down ＊/#define EHOSTUNREACH 113 /＊No route to host ＊/#define EALREADY 114 /＊Operation already in progress ＊/ #define EINPROGRESS 115 /＊Operation now in progress ＊/ #define ESTALE 116 /＊Stale NFS file handle ＊/ #define EUCLEAN 117 /＊Structure needs cleaning ＊/ #define ENOTNAM 118 /＊Not a XENIX named type file ＊/ #define ENAVAIL 119 /＊No XENIX semaphores available ＊/ #define EISNAM 120 /＊Is a named type file ＊/ #define EREMOTEIO 121 /＊Remote I/O error ＊/#define EDQUOT 122 /＊Quota exceeded ＊/#define ENOMEDIUM 123 /＊No medium found ＊/#define EMEDIUMTYPE 124 /＊Wrong medium type ＊#define ECANCELED 125 / ＊操作已取消＊/#define ENOKEY 126 / ＊必需的密钥不可用＊/ #define EKEYEXPIRED 127 / ＊密钥已过期＊/#define EKEYREVOKED 128 / ＊密钥已被撤销＊/#define EKEYREJECTED 129 / ＊密钥被服务拒绝＊// ＊用于强大的互斥体＊/#define EOWNERDEAD 130 / ＊所有者死亡＊/#define ENOTRECOVERABLE 131 / ＊状态不可恢复＊/#define ERFKILL 132 / ＊由于射频杀死＊/#ifdef __KERNEL__/ ＊＊用户程序切勿看到这些内容。

打印Linux系统错误编码及提示

系统运维工程师和系统开发工程师在日常工作中，经常会遇到此类问题“当你进行了一些不当操作，系统会给你错误提示”，这些错误提示在操作系统中都是错误编码的，每一个提示对应一个错误编码，错误编码供程序代码中方便调用，接下来我们会打印出linux操作系统的错误编码及提示，如下：一、系统环境系统版本：内核版本：二、程序代码代码如下：三、编译运行结果如下：[root@CentOS6 erro_num]# gcc error_num.c[root@centos6 erro_num]# ./a.out0:Success1:Operation not permitted2:No such file or directory3:No such process4:Interrupted system call5:Input/output error6:No such device or address7:Argument list too long8:Exec format error9:Bad file descriptor10:No child processes11:Resource temporarily unavailable 12:Cannot allocate memory13:Permission denied14:Bad address15:Block device required16:Device or resource busy17:File exists18:Invalid cross-device link19:No such device20:Not a directory21:Is a directory22:Invalid argument23:Too many open files in system 24:Too many open files25:Inappropriate ioctl for device 26:Text file busy27:File too large28:No space left on device29:Illegal seek30:Read-only file system31:Too many links32:Broken pipe33:Numerical argument out of domain 34:Numerical result out of range 35:Resource deadlock avoided36:File name too long37:No locks available38:Function not implemented39:Directory not empty40:Too many levels of symbolic links 41:Unknown error 4142:No message of desired type43:Identifier removed44:Channel number out of range 45:Level 2 not synchronized46:Level 3 halted47:Level 3 reset48:Link number out of range49:Protocol driver not attached50:No CSI structure available51:Level 2 halted52:Invalid exchange53:Invalid request descriptor54:Exchange full55:No anode56:Invalid request code57:Invalid slot58:Unknown error 5859:Bad font file format60:Device not a stream61:No data available62:Timer expired63:Out of streams resources64:Machine is not on the network65:Package not installed66:Object is remote67:Link has been severed68:Advertise error69:Srmount error70:Communication error on send71:Protocol error72:Multihop attempted73:RFS specific error74:Bad message75:Value too large for defined data type76:Name not unique on network77:File descriptor in bad state78:Remote address changed79:Can not access a needed shared library80:Accessing a corrupted shared library81:.lib section in a.out corrupted82:Attempting to link in too many shared libraries 83:Cannot exec a shared library directly84:Invalid or incomplete multibyte or wide character 85:Interrupted system call should be restarted 86:Streams pipe error87:Too many users88:Socket operation on non-socket89:Destination address required90:Message too long91:Protocol wrong type for socket92:Protocol not available93:Protocol not supported94:Socket type not supported95:Operation not supported96:Protocol family not supported97:Address family not supported by protocol98:Address already in use99:Cannot assign requested address100:Network is down101:Network is unreachable102:Network dropped connection on reset103:Software caused connection abort104:Connection reset by peer105:No buffer space available106:Transport endpoint is already connected 107:Transport endpoint is not connected108:Cannot send after transport endpoint shutdown 109:Too many references: cannot splice110:Connection timed out111:Connection refused112:Host is down113:No route to host114:Operation already in progress115:Operation now in progress116:Stale NFS file handle117:Structure needs cleaning118:Not a XENIX named type file119:No XENIX semaphores available120:Is a named type file121:Remote I/O error122:Disk quota exceeded123:No medium found124:Wrong medium type125:Operation canceled126:Required key not available127:Key has expired128:Key has been revoked129:Key was rejected by service130:Owner died131:State not recoverable如果你看过nginx-1.0.10源码，里面有一个类似的错误编码预定义135个，在objs/ngx_auto_config.h 中，#define NGX_SYS_NERR135，事实证明，这种思想是非常可取的，我们自己写软件的时候，不妨尝试一下？/儒道至圣最新章节。

Linux新手必读常见命令行错误及解决方法

Linux新手必读常见命令行错误及解决方法Linux操作系统作为一款强大且广泛应用的操作系统，其命令行界面是最为重要的一部分。

然而，对于新手来说，掌握命令行并不是一件容易的事情。

在使用过程中，经常会遇到各种错误提示，影响正常的使用体验。

本文将介绍一些常见的命令行错误以及解决方法，帮助Linux新手更好地应对各种情况。

错误一：命令找不到或不存在（Command not found）这是一个非常常见的错误，意味着输入的命令在当前的环境中没有找到。

这通常是由于命令不存在或者命令没有被正确地安装所致。

解决方法：1. 确保所输入的命令正确无误，检查是否拼写错误。

2. 使用适当的命令进行搜索。

例如，使用`which`命令可以查找某个命令的路径，例如`which command_name`。

3. 检查命令是否被正确地安装。

可以尝试使用`apt-get`或者`yum`等包管理器进行命令的安装。

4. 如果命令仍然无法找到，可能需要手动安装命令或者检查环境变量设置。

错误二：权限不足（Permission denied）Linux系统中，每个用户都有相应的权限来访问和执行文件。

当遇到权限不足的错误提示时，说明当前用户没有执行该命令的权限。

解决方法：1. 使用`sudo`命令，该命令可以提升当前用户的权限并执行命令。

例如，`sudo command_name`。

2. 如果当前用户没有sudo权限，则需要使用管理员账户来执行命令。

错误三：文件或目录不存在（No such file or directory）当输入的文件或者目录不存在时，就会出现这个错误提示。

这可能是由于输入错误的文件名或者目录路径所致。

解决方法：1. 确认输入的文件或者目录路径是否正确，并检查拼写错误。

2. 使用`ls`命令来查看当前目录下的文件和目录，确认所要操作的文件或目录是否存在。

错误四：命令语法错误（Syntax error）当输入的命令语法错误时，系统会提示命令的用法或者提供一些错误信息。

[Linux]命令返回值以及错误对照表

[Linux]命令返回值以及错误对照表Linux执⾏完命令之后默认会有⼀个返回值# lsapp backupconfig.json Doc manage.py __pycache__ settings.py# echo $?错误对照表"OS error code 1: Operation not permitted""OS error code 2: No such file or directory""OS error code 3: No such process""OS error code 4: Interrupted system call""OS error code 5: Input/output error""OS error code 6: No such device or address""OS error code 7: Argument list too long""OS error code 8: Exec format error""OS error code 9: Bad file descriptor""OS error code 10: No child processes""OS error code 11: Resource temporarily unavailable""OS error code 12: Cannot allocate memory""OS error code 13: Permission denied""OS error code 14: Bad address""OS error code 15: Block device required""OS error code 16: Device or resource busy""OS error code 17: File exists""OS error code 18: Invalid cross-device link""OS error code 19: No such device""OS error code 20: Not a directory""OS error code 21: Is a directory""OS error code 22: Invalid argument""OS error code 23: Too many open files in system""OS error code 24: Too many open files""OS error code 25: Inappropriate ioctl for device""OS error code 26: Text file busy""OS error code 27: File too large""OS error code 28: No space left on device""OS error code 29: Illegal seek""OS error code 30: Read-only file system""OS error code 31: Too many links""OS error code 32: Broken pipe""OS error code 33: Numerical argument out of domain""OS error code 34: Numerical result out of range""OS error code 35: Resource deadlock avoided""OS error code 36: File name too long""OS error code 37: No locks available""OS error code 38: Function not implemented""OS error code 39: Directory not empty""OS error code 40: Too many levels of symbolic links""OS error code 42: No message of desired type""OS error code 43: Identifier removed""OS error code 44: Channel number out of range""OS error code 45: Level 2 not synchronized""OS error code 46: Level 3 halted""OS error code 47: Level 3 reset""OS error code 48: Link number out of range""OS error code 49: Protocol driver not attached""OS error code 50: No CSI structure available""OS error code 51: Level 2 halted""OS error code 52: Invalid exchange""OS error code 53: Invalid request descriptor""OS error code 54: Exchange full""OS error code 55: No anode""OS error code 56: Invalid request code""OS error code 57: Invalid slot""OS error code 59: Bad font file format""OS error code 60: Device not a stream""OS error code 61: No data available""OS error code 62: Timer expired""OS error code 63: Out of streams resources""OS error code 64: Machine is not on the network""OS error code 65: Package not installed""OS error code 66: Object is remote""OS error code 67: Link has been severed""OS error code 68: Advertise error""OS error code 69: Srmount error""OS error code 70: Communication error on send""OS error code 71: Protocol error""OS error code 72: Multihop attempted""OS error code 73: RFS specific error""OS error code 74: Bad message""OS error code 75: Value too large for defined data type""OS error code 76: Name not unique on network""OS error code 77: File descriptor in bad state""OS error code 78: Remote address changed""OS error code 79: Can not access a needed shared library""OS error code 80: Accessing a corrupted shared library""OS error code 81: .lib section in a.out corrupted""OS error code 82: Attempting to link in too many shared libraries""OS error code 83: Cannot exec a shared library directly""OS error code 84: Invalid or incomplete multibyte or wide character""OS error code 85: Interrupted system call should be restarted""OS error code 86: Streams pipe error""OS error code 87: Too many users""OS error code 88: Socket operation on non-socket""OS error code 89: Destination address required""OS error code 90: Message too long""OS error code 91: Protocol wrong type for socket""OS error code 92: Protocol not available""OS error code 93: Protocol not supported""OS error code 94: Socket type not supported""OS error code 95: Operation not supported""OS error code 96: Protocol family not supported""OS error code 97: Address family not supported by protocol""OS error code 98: Address already in use""OS error code 99: Cannot assign requested address""OS error code 100: Network is down""OS error code 101: Network is unreachable""OS error code 102: Network dropped connection on reset""OS error code 103: Software caused connection abort""OS error code 104: Connection reset by peer""OS error code 105: No buffer space available""OS error code 106: Transport endpoint is already connected""OS error code 107: Transport endpoint is not connected""OS error code 108: Cannot send after transport endpoint shutdown""OS error code 109: Too many references: cannot splice""OS error code 110: Connection timed out""OS error code 111: Connection refused""OS error code 112: Host is down""OS error code 113: No route to host""OS error code 114: Operation already in progress""OS error code 115: Operation now in progress""OS error code 116: Stale NFS file handle""OS error code 117: Structure needs cleaning""OS error code 118: Not a XENIX named type file""OS error code 119: No XENIX semaphores available""OS error code 120: Is a named type file""OS error code 121: Remote I/O error""OS error code 122: Disk quota exceeded""OS error code 123: No medium found""OS error code 124: Wrong medium type""OS error code 125: Operation canceled""OS error code 126: Required key not available""OS error code 127: Key has expired""OS error code 128: Key has been revoked""OS error code 129: Key was rejected by service""OS error code 130: Owner died""OS error code 131: State not recoverable""MySQL error code 132: Old database file""MySQL error code 133: No record read before update""MySQL error code 134: Record was already deleted (or record file crashed)" "MySQL error code 135: No more room in record file""MySQL error code 136: No more room in index file""MySQL error code 137: No more records (read after end of file)""MySQL error code 138: Unsupported extension used for table""MySQL error code 139: Too big row""MySQL error code 140: Wrong create options""MySQL error code 141: Duplicate unique key or constraint on write or update" "MySQL error code 142: Unknown character set used""MySQL error code 143: Conflicting table definitions in sub-tables of MERGE table" "MySQL error code 144: Table is crashed and last repair failed""MySQL error code 145: Table was marked as crashed and should be repaired" "MySQL error code 146: Lock timed out; Retry transaction""MySQL error code 147: Lock table is full; Restart program with a larger locktable" "MySQL error code 148: Updates are not allowed under a read only transactions" "MySQL error code 149: Lock deadlock; Retry transaction""MySQL error code 150: Foreign key constraint is incorrectly formed""MySQL error code 151: Cannot add a child row""MySQL error code 152: Cannot delete a parent row"。