[SOLVED] Unable to mount ext4 filesystem with 4.4.144
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been a bit busy and just recently found time to update my NAS server to kernel 4.4.144. After performing the install I've been unable to mount a largish ext4 filesystem.
Whenever I try to mount the filesystem I get a "Structure needs cleaning" error message. I've run 'fsck.ext4 -vccf' and 'e2fsck -vccf' to no avail. Every time fsck is run it reports that the last block of the filesystem is bad and that it has updated the filesystem.
Strangely, dumpe2fs reports that the file system is clean. Mounting the filesystem as read-only and verifying the SHA hashes on my files shows that the data is still there and good.
Unable to find the previous patched kernel, I went ahead and installed the kernel that originally came with Slackware 14.2 (4.4.14). Booting 4.4.14 kernel I am able to mount the file system without issue.
Has anyone else seen this issue? Does anyone have any ideas as to what can be done next?
I know it isn't necessarily the "fix" you were looking for, but Pat has updated the kernel to 4.4.153, and that might fix your problem (even if it isn't specified directly).
Code:
Tue Aug 28 22:05:19 UTC 2018
patches/packages/linux-4.4.153/*: Upgraded.
This kernel update enables mitigations for L1 Terminal Fault aka
Foreshadow and Foreshadow-NG vulnerabilities.
Thanks to Bernhard Kaindl for bisecting the boot issue that was preventing
us from upgrading to earlier 4.4.x kernels that contained this fix.
To see the status of CPU vulnerability mitigations on your system, look at
the files in: /sys/devices/system/cpu/vulnerabilities
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3615
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3620
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3546
(* Security fix *)
I've been a bit busy and just recently found time to update my NAS server to kernel 4.4.144. After performing the install I've been unable to mount a largish ext4 filesystem.
Whenever I try to mount the filesystem I get a "Structure needs cleaning" error message. I've run 'fsck.ext4 -vccf' and 'e2fsck -vccf' to no avail. Every time fsck is run it reports that the last block of the filesystem is bad and that it has updated the filesystem.
Strangely, dumpe2fs reports that the file system is clean. Mounting the filesystem as read-only and verifying the SHA hashes on my files shows that the data is still there and good.
Unable to find the previous patched kernel, I went ahead and installed the kernel that originally came with Slackware 14.2 (4.4.14). Booting 4.4.14 kernel I am able to mount the file system without issue.
Has anyone else seen this issue? Does anyone have any ideas as to what can be done next?
Thanks in advance,
I had a very similar problem, only fsck would report that everything was just fine.
I ended up creating a new logical volume and used testdisk from slackbuilds to copy the files over. The filesystem was exposed as a samba share, which I suspect had something to do with it. (However, suspicion isn't proof.)
I know it isn't necessarily the "fix" you were looking for, but Pat has updated the kernel to 4.4.153, and that might fix your problem (even if it isn't specified directly).
Thanks for the heads up, I'll give this a try.
Quote:
Originally Posted by Richard Cranium
I had a very similar problem, only fsck would report that everything was just fine.
I ended up creating a new logical volume and used testdisk from slackbuilds to copy the files over. The filesystem was exposed as a samba share, which I suspect had something to do with it. (However, suspicion isn't proof.)
As another data point, if it helps, my volume wasn't exposed as a SAMBA share.
The last block error seems to be caused by running the badblocks command 'fsck.ext4 -c'. Running 'fsck.ext4 -vf' reports a clean filesystem. The error message I get when running badblocks can be seen here StackExchange. Since my filesystem is running on top of LVM I'm assuming I'm seeing the same error message.
Well, work ate more time than I had thought it would. I got around to the experiment tonight, and the old logical volume mounted without a squeak with the new kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
