Difference between revisions of "Review ext4 journalctl logs"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | kernel: [[EXT4]]-fs (vdb1): mounted filesystem with ordered data mode. Opts: (null) | + | Oct 17 07:49:41 kernel: [[EXT4]]-fs (vdb1): mounted filesystem with ordered data mode. Opts: (null) |
| + | |||
| + | Oct 13 07:49:41 SERVER kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: [[auto_da_alloc]],[[acl]],[[user_xattr]],errors=remount-ro,commit=20,[[inode_readahead_blks]]=64,delalloc | ||
| + | |||
kernel: EXT4-fs (vda2): re-mounted. Opts: (null) | kernel: EXT4-fs (vda2): re-mounted. Opts: (null) | ||
| Line 15: | Line 18: | ||
Oct 04 12:11:12 SERVER kernel: EXT4-fs (sdb1): error count since last [[fsck]]: 15 | Oct 04 12:11:12 SERVER kernel: EXT4-fs (sdb1): error count since last [[fsck]]: 15 | ||
| + | |||
| + | Oct 13 07:49:41 SERVER kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: auto_da_alloc,acl,user_xattr,errors=remount-ro,commit=20,[[inode_readahead_blks]]=64,delalloc | ||
| − | |||
Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): Couldn't remount [[RDWR]] because of unprocessed orphan inode list. Please umount/remount instead | Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): Couldn't remount [[RDWR]] because of unprocessed orphan inode list. Please umount/remount instead | ||
Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) | Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) | ||
Latest revision as of 11:26, 26 November 2020
Oct 17 07:49:41 kernel: EXT4-fs (vdb1): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 07:49:41 SERVER kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: auto_da_alloc,acl,user_xattr,errors=remount-ro,commit=20,inode_readahead_blks=64,delalloc
kernel: EXT4-fs (vda2): re-mounted. Opts: (null)
EXT4-fs (sda2): initial error at time 1595448557: ext4_journal_check_start:61
kernel: EXT4-fs (sda2): Remounting filesystem read-only
Aug 10 03:23:58 SERVER kernel: EXT4-fs (sda2): INFO: recovery required on readonly filesystem
kernel: EXT4-fs (sda2): warning: mounting fs with errors, running e2fsck is recommended
touch file.txt touch: cannot touch 'file.txt': Read-only file system
Oct 04 12:11:12 SERVER kernel: EXT4-fs (sdb1): error count since last fsck: 15
Oct 13 07:49:41 SERVER kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: auto_da_alloc,acl,user_xattr,errors=remount-ro,commit=20,inode_readahead_blks=64,delalloc
Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): Couldn't remount RDWR because of unprocessed orphan inode list. Please umount/remount instead Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) Oct 13 07:49:35 SERVER kernel: EXT4-fs (sda2): recovery complete
Related terms[edit]
See also[edit]
ext4e2fsck,,fsck.ext4, superblock, inode, block size, mkfs.ext4 tune2fswipefs,resize2fsstat,extents, Review ext4 journalctl logs. Read-only file system,virt-resize, ACL- File systems:
ext4,XFS,ZFS,btrfs,wipefs,findfs,HDFS,overlay,aufs,virt-filesystems, Windows: (FAT, NTFS, ReFS), GPFS, squashfs, Ecryptfs, Encfs, FUSE, VMFS, Comparison of distributed file systems, Userspace filesystem, Resize filesystem size - systemd-journald:
journalctl,/etc/systemd/journald.conf,journalctl logs,journalctl --list-boots,journalctl --disk-usage,journalctl -u kubelet,journalctl -u prometheus,journalctl --help
Advertising:
