public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Julius Schwartzenberg <julius.schwartzenberg@gmail.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Theodore Ts'o <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: e2fsck doesn't finish
Date: Sun, 23 Apr 2017 16:07:29 +0200	[thread overview]
Message-ID: <4eb717f7-1ccb-95a0-0b53-e811651965ee@gmail.com> (raw)
In-Reply-To: <4A1EA678-9982-4D9D-8559-713487A372B4@dilger.ca>

Andreas Dilger wrote:
> It would be useful to know which feature(s) that Fedora 25 enabled that
> Ubuntu 16.04 didn't understand.  You could use something like:
> 
>     dumpe2fs -h /dev/XXX | grep -i feature
> 
> under Ubuntu.  Typically, the code shouldn't be enabling any feature on
> the filesystem without an explicit request from the admin.

I expect that Ubuntu's kernel (4.4.0) supports more features than its
e2fsck as I can mount it now. Ubuntu 16.04 comes with e2fsprogs version
1.42.13. The feature that that version says it doesn't support is
inline_data.


> Also, the "failed to mount" case should print something to the console
> logs about an unsupported feature, which would help isolate the problem.

Yes, it printed it couldn't mount the filesystem as ext3 originally, but
I changed /etc/fstab accordingly.

I have always been quite ignorant on filesystem upgrades and features
supported by either the kernel or e2fsprogs and upgrades/downgrades of
existing filesystems as usually everything just works.
I expect that the upgrade from ext3 to ext4 was triggered by Fedora's
installer (not e2fsprogs) and that dual boot configurations are less
tested in general.

Best regards,
Julius

      reply	other threads:[~2017-04-23 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 17:07 e2fsck doesn't finish Julius Schwartzenberg
2017-04-17 14:17 ` Eric Sandeen
2017-04-17 15:11   ` Julius Schwartzenberg
2017-04-17 15:18     ` Eric Sandeen
2017-04-17 19:16 ` Eric Sandeen
2017-04-18  5:24   ` Theodore Ts'o
2017-04-19 20:57     ` Julius Schwartzenberg
2017-04-19 21:07       ` Andreas Dilger
2017-04-23 14:07         ` Julius Schwartzenberg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4eb717f7-1ccb-95a0-0b53-e811651965ee@gmail.com \
    --to=julius.schwartzenberg@gmail.com \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox