An ext4 filesystem goes into readonly mode frequently with the following error in log file
-
- Posts: 7
- Joined: 2019/01/17 07:25:53
- Location: coimbatore
An ext4 filesystem goes into readonly mode frequently with the following error in log file
Error Log:
-------------
kernel: EXT4-fs (dm-4): Delayed block allocation failed for inode 54395351 at logical offset 1651 with max blocks 5 with error 30
kernel: EXT4-fs (dm-4): This should not happen!! Data will be lost
kernel: EXT4-fs error (device dm-4) in ext4_writepages:2540: Journal has aborted
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs (dm-4): Remounting filesystem read-only
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56:
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56:
kernel: Detected aborted journal
kernel:
kernel: Detected aborted journal
kernel:
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs (dm-4): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 53608493; err -30
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
Affected version:
------------------------
CentOS 7
Filesystem:
-----------------
ext4
-------------
kernel: EXT4-fs (dm-4): Delayed block allocation failed for inode 54395351 at logical offset 1651 with max blocks 5 with error 30
kernel: EXT4-fs (dm-4): This should not happen!! Data will be lost
kernel: EXT4-fs error (device dm-4) in ext4_writepages:2540: Journal has aborted
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs (dm-4): Remounting filesystem read-only
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56:
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56:
kernel: Detected aborted journal
kernel:
kernel: Detected aborted journal
kernel:
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
kernel: EXT4-fs (dm-4): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 53608493; err -30
kernel: EXT4-fs error (device dm-4): ext4_journal_check_start:56: Detected aborted journal
Affected version:
------------------------
CentOS 7
Filesystem:
-----------------
ext4
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
What is the output from uname -a ?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 7
- Joined: 2019/01/17 07:25:53
- Location: coimbatore
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
Linux example.com 3.10.0-693.11.6.el7.x86_64 #1 SMP Thu Jan 4 01:06:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
Start by running yum update. You are more than 1 year behind on updates and that is a 7.4 kernel when 7.6 is current.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 7
- Joined: 2019/01/17 07:25:53
- Location: coimbatore
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
Is this the known issue in 7.4 kernel?
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
No idea but only the latest is supported.
Edit: there are 23740 lines in the output from rpm -q --changelog kernel-3.10.0-957.1.3.el7.x86_64 since the 3.10.0-693 kernels and of those 71 are listed as being specific to ext4.
Edit: there are 23740 lines in the output from rpm -q --changelog kernel-3.10.0-957.1.3.el7.x86_64 since the 3.10.0-693 kernels and of those 71 are listed as being specific to ext4.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
Just to clarify:
Is upgrading kernal the only permanent solution ?
Is upgrading kernal the only permanent solution ?
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
Updating the kernel is a starting point because only the latest version is supported. Troubleshooting will begin once the system is up-to-date and the problem persists.
CentOS Forum FAQ
-
- Posts: 7
- Joined: 2019/01/17 07:25:53
- Location: coimbatore
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
We have upgraded the kernel version as requested but still the issue persists.
Re: An ext4 filesystem goes into readonly mode frequently with the following error in log file
This is a silly idea, but worth asking: Given that this is an ext4 fs, have you run fsck? Usually if the system goes out into the weeds this is usually my first step. If that does not fix the problem I know I'm in DEEP trouble!!sathishasokan88 wrote: ↑2019/08/26 12:14:56We have upgraded the kernel version as requested but still the issue persists.