Your message dated Tue, 16 May 2017 14:34:14 -0400
with message-id <[email protected]>
and subject line Re: Bug#862704: e2fsprogs: Cannot mount Stretch ext4 partition
from my Slackware 14.1 installation.
has caused the Debian Bug report #862704,
regarding e2fsprogs: Cannot mount Stretch ext4 partition from my Slackware 14.1
installation.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
862704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862704
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.43.4-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386
(i686)
Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.43.4-2
ii libblkid1 2.29.2-1
ii libc6 2.24-10
ii libcomerr2 1.43.4-2
ii libss2 1.43.4-2
ii libuuid1 2.29.2-1
ii util-linux 2.29.2-1
e2fsprogs recommends no packages.
Versions of packages e2fsprogs suggests:
pn e2fsck-static <none>
pn fuse2fs <none>
pn gpart <none>
pn parted <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
The Slackware 14.1 distribution uses a 3.10 kernel, which is ancient.
So it's not terribly surprising that it may not be able to mount a
file system made with a more modern e2fsprogs release.
My guess is that it's the metadata checksum feature which is causing
problems. If you create the file system via:
mke2fs -t ext4 -O ^metadata_csum,uninit_bg /dev/sdXX
That should allow you to mount the file system on legacy/ancient
kernels.
Cheers,
- Ted
--- End Message ---
