Fsck − The unix† File System Check Program


LINK COUNT TABLE OVERFLOW (CONTINUE)



Download 52.5 Kb.
View original pdf
Page24/49
Date14.07.2018
Size52.5 Kb.
1   ...   20   21   22   23   24   25   26   27   ...   49
LINK COUNT TABLE OVERFLOW (CONTINUE)
An internal table for fsck containing allocated inodes with a link count of zero cannot allocate more memory. Increase the virtual memory for fsck.
Possible responses to the CONTINUE prompt are:
YES continue with the program. This error condition will not allow a complete check of the file system.
A second run of fsck should be made to recheck this file system. If another allocated inode with a zero link count is found, this error condition is repeated.
NO terminate the program.
B BAD I=I
Inode I contains block number B with a number lower than the number of the first data block in the file system or greater than the number of the last block in the file system. This error condition may invoke the


Fsck − the unix file system check program
Table of contents
Can’t stat fcan’t make sense out of name
Impossible minfree=
Magic number wrong
Can not read blk
Partially truncated inode
Excessive bad blks
Bad state ddd to blkerr
Partially allocated inode i=
Root inode unallocated (allocate)
Cannot allocate root inode
I out of range i=
Zero length directory i=
Directory corrupted i=
Missing ‘.’ i=
Extra ‘.’ entry i=
Missing ‘..’ i=
Extra ‘..’ entry i=
Bad state s for root inode
No lost+found directory (create)
Sorry. cannot create lost+found directory
Sorry. no space in lost+found directory
Directory f length
Unref file i=
No space left in /lost+found (expand)
Link count type i=


Share with your friends:
1   ...   20   21   22   23   24   25   26   27   ...   49


The database is protected by copyright ©userg.info 2017
send message

    Main page

bosch
camera
chevrolet
epson
fiat
Harley Davidson
Honda
iphone
mitsubishi
nissan
Panasonic
Sony
volvo
xiaomi
Xperia
yamaha