Linux Labs

Inside the system: resources, kernel, processes / Stage 8 of 12

dmesg and the kernel log

Not running Starting usually ~20 s
Leave the lesson

Step 8 of 8 · summary · 2 min

Summary

  • The kernel writes about failures into a ring buffer: sudo dmesg -T reads it, and sudo journalctl -k reads the copy in the journal that survives a reboot.
  • The EXT4-fs error line names the device, the inode and the process; after it ext4 switches writing off, and e2fsck on the unmounted device repairs the filesystem.
  • segfault at … in … is a program crash from touching memory not its own, status 139, and the line's level is info.
  • An OOM report shows who asked for memory, the group's processes and whom the kernel killed.
  • The archive from the start of the lesson answered Bad message and Input/output error with rw in findmnt because the kernel found the damaged inode of orders-07.csv and switched writing off for the whole filesystem.
Ubuntu 24.04
Loading…