I agree Slackware 14.1 is old so is Wheezy which is supposed to be still supported. Seems to me that the default installation should be backward compatible.
On Tue, May 16, 2017 at 11:36 AM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the e2fsprogs package: > > #862704: e2fsprogs: Cannot mount Stretch ext4 partition from my Slackware > 14.1 installation. > > It has been closed by Theodore Ts'o <ty...@mit.edu>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Theodore Ts'o < > ty...@mit.edu> by > replying to this email. > > > -- > 862704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862704 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > ---------- Forwarded message ---------- > From: "Theodore Ts'o" <ty...@mit.edu> > To: VasantK <vasantkonl...@gmail.com>, 862704-d...@bugs.debian.org > Cc: > Bcc: > Date: Tue, 16 May 2017 14:34:14 -0400 > Subject: Re: Bug#862704: e2fsprogs: Cannot mount Stretch ext4 partition > from my Slackware 14.1 installation. > 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 > > ---------- Forwarded message ---------- > From: VasantK <vasantkonl...@gmail.com> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Cc: > Bcc: > Date: Mon, 15 May 2017 17:27:16 -0700 > Subject: e2fsprogs: Cannot mount Stretch ext4 partition from my Slackware > 14.1 installation. > 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 > >
