API tools faq
paste
Advertisement
Guest User

e2fsck -n

a guest
Jul 23rd, 2018
179
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.82 KB | None | 0 0
raw download clone embed print report
  1. /dev/dm-1 contains a file system with errors, check forced.
  2. Resize inode not valid. Recreate? no
  3.  
  4. ...
  5.  
  6. Illegal block #262142 (758287166) in inode 7. IGNORED.
  7. Illegal block #262143 (2074328446) in inode 7. IGNORED.
  8. Illegal block #262144 (2181095733) in inode 7. IGNORED.
  9. Illegal block #262145 (3962860329) in inode 7. IGNORED.
  10. Illegal block #262146 (925109813) in inode 7. IGNORED.
  11. Illegal block #262147 (1190339829) in inode 7. IGNORED.
  12. Illegal block #262148 (3818784234) in inode 7. IGNORED.
  13. Illegal block #262149 (2990678000) in inode 7. IGNORED.
  14. Illegal block #262150 (2500831991) in inode 7. IGNORED.
  15. Illegal block #262151 (1459615598) in inode 7. IGNORED.
  16. Illegal block #262152 (1428774103) in inode 7. IGNORED.
  17. Illegal block #262153 (721943098) in inode 7. IGNORED.
  18. Too many illegal blocks in inode 7.
  19. Clear inode? no
  20.  
  21. Suppress messages? no
  22.  
  23. Illegal block #262154 (2446473632) in inode 7. IGNORED.
  24. Illegal block #262155 (3343359539) in inode 7. IGNORED.
  25. Inode 7, i_blocks is 90120, should be 73360. Fix? no
  26.  
  27. Inode 392449 seems to contain garbage. Clear? no
  28.  
  29. Inode 392491 passes checks, but checksum does not match inode. Fix? no
  30.  
  31. Inode 392497 has inline data and extent flags set but i_block contains junk.
  32. Clear inode? no
  33.  
  34. Inode 392497 has INLINE_DATA_FL flag on filesystem without inline data support.
  35. Clear? no
  36.  
  37. Inode 392497 is in use, but has dtime set. Fix? no
  38.  
  39. Inode 392497 has a extra size (18411) which is invalid
  40. Fix? no
  41.  
  42. Inode 392497 has INDEX_FL flag set but is not a directory.
  43. Clear HTree index? no
  44.  
  45. HTREE directory inode 392497 has an invalid root node.
  46. Clear HTree index? no
  47.  
  48. Inode 392497, i_size is 7701896689863869971, should be 0. Fix? no
  49.  
  50. Inode 392497, i_blocks is 123296423704134, should be 0. Fix? no
  51.  
  52. Inode 392497 passes checks, but checksum does not match inode. Fix? no
  53.  
  54. Inode 392498 seems to contain garbage. Clear? no
  55.  
  56. Inode 392498 is in use, but has dtime set. Fix? no
  57.  
  58. Inode 392498 has imagic flag set. Clear? no
  59.  
  60. Inode 392498 has a extra size (10677) which is invalid
  61. Fix? no
  62.  
  63. Inode 392498, i_size is 89820549539796794, should be 0. Fix? no
  64.  
  65. Inode 392498, i_blocks is 169690736450073, should be 0. Fix? no
  66.  
  67. Inode 392498 passes checks, but checksum does not match inode. Fix? no
  68.  
  69. Inode 392499 seems to contain garbage. Clear? no
  70.  
  71. Inode 392499 has INLINE_DATA_FL flag on filesystem without inline data support.
  72. Clear? no
  73.  
  74. Inode 392499 is in use, but has dtime set. Fix? no
  75.  
  76. Inode 392499 has imagic flag set. Clear? no
  77.  
  78. Inode 392499 has a extra size (50685) which is invalid
  79. Fix? no
  80.  
  81. Error while iterating over blocks in inode 392499: Cannot iterate data blocks of an inode containing inline data
  82.  
  83. /dev/dm-1: ********** WARNING: Filesystem still has errors **********
  84.  
  85.  
  86. /dev/dm-1: ********** WARNING: Filesystem still has errors **********
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!