** Tags removed: precise trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1365874
Title:
Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
I've been using e2fsprogs-xenial from Simon PPA for a month without
issues so far.
I'm using the an external drive for journal an this options in my fstab
for the volume:
errors=remount-
ro,data=journal,journal_async_commit,nobarrier,commit=60,noatime 0
Thanks for this!
--
You received this
The blog post here:
https://raid6.com.au/posts/fs_ext4_external_journal_caveats/
is not generally true. What journal_async_commit does is convert the
sequence:
1. write journal blocks
2. cache flush
3. write journal commit block
4. cache flush
... to:
1. write journal blocks
2. write
Here is the PPA for all architectures, please test :-
https://launchpad.net/~ubuntu-iremonger/+archive/ubuntu/e2fsprogs-xenial
That is currently a backport of the version in bionic release itself,
but maintains the xenial mke2fs.conf defaults [creating filesystems
without 64bit,metadata_csum] for
That's great Simon! I will test it once it's ready then.
Regarding (b): wouldn't it be easier to try to get the package in
xenial-backports then?
That repo it's activated by default, but as I can read here:
https://help.ubuntu.com/community/UbuntuBackports
On releases before (but not
Marc, Briefly just to let you know I'm working on a PPA for bionic e2fsprogs
backport to xenial, will update when thats' ready. Turns out that:-
(a) Ubuntu devs are rather tied-up fixing bionic18.04 bugs, and
(b) to do a good SRU would need much regression-testing and somebody to push it
I would like to test this configuration in my laptop with a slow
rotational disk + a small SSD:
https://raid6.com.au/posts/fs_ext4_external_journal_caveats/
But, if I understood correctly, I need to configure journal_async_commit
for it to be reliable, and that option automatically enables
If you are trying to build from the unpacked debian sources for 1.43.x,
you'll need to run the commands:
./debian/rules mrproper
./debian/rules
... to have the build system figure out which antique version of Debian
build infrastructure you are using, and regenerate debian/control from
HOWEVER, Trusty e2fsprogs backporting situation actually seems to be that, some
change between 1.43.3-1~bpo8+1 and 1.43.4-2 is where the
trusty-incompatibility has accrued, 1.43.9-2 does NOT build on trusty! :-
https://www.iremonger.me.uk/noidx/e2fs/e2fsprogs-1.43.9_trusty_build-fail.log
A
OK On further investigation, I have confirmed a lot of key-facts (1 of 2
linked comments).
e2fsprogs 1.44.0-1 backports to xenial with no difficulty whatsoever,
passes "make fullcheck" and works in every way I can tell, lots of
resizing and checking and use within gparted, etc, all (apparently)
e2fsprogs 1.44.0 for bionic18.04 has apparently been agreed:-
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1756177
[launchpad build-logs suggest its' been built for PROPOSED but not yet
seen it 'come through' as a package or appear on 'packages.ubuntu.com'
...].
Hopefully that will
See linked bug 1601997, response seems to be to accept your 'new'
defaults for ext4 in 18.04. I note, particularly -- your request about
1.44.0 inclusion doesn't yet seem to be addressed [maybe it requires a
separate bug//issue] ;-(. Do expand on that point if you can.
--
You received this bug
The Metadata_csum feature is a RO_COMPAT feature. Hence, grub2 and os-
prober shouldn't care about this feature (if properly implemented).
This is because the guarntee is that even if the kernel (or userspace
application directly accessing the file system) doesn't know about a bit
in the
FWIW, As was discussed, I checked into Grub2 and os-prober in older supported
ubuntu (which may have similar incompatibility to e2fsprogs, thereby creating a
multibooting issue with 18.04).
After experimenting carefully with a 14.04+16.04+18.04 (GA kernels, no HWE
specifically) BIOS-style
Given your other comment (which I think may have been posted to the wrong
thread):-
[E2fsprogs 1.44.0 now depends on dpkg build-profiles, which means that getting
it backported to 14.04 LTS would require adjusting debian/control and
debian/rules a bit. For 14.04 LTS, I'd urge consideration of
I recently released e2fsprogs 1.44.0 (currently in Debian Unstable,
should hopefully hit Debian Testing in three more days) which turns on
Metadata Checksums for everyone.
https://packages.debian.org/sid/e2fsprogs
Pulling in 1.44.0 supports two new features, largedir and ea_inode,
(neither
Ubuntu 18.04 may well enable (under review) 64bit,metadata_csum by
default, thereby creating ext4 filesystems that are not compatible with
e2fsck on Ubuntu-16.04 LTS (or 14.04)?
This creates all sorts of problems for compatibility/portability of
filesystems, for e.g.:-
* dual-booting 18.04 and
I'm re-assigning the status and importance based on user reports in IRC
and elsewhere.
See also the related "Ubuntu 16.10 installer sets metadata_csum option
on ext4 partition which is incompatible with other LTS Ubuntu versions"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997
Aaaand... installing the hwe-edge packages on Xenial causes LVM EXT4
partitions to fail entirely because e2fsck cannot handle it.
A bit more of an issue than "wishlist".
Workaround: install Zesty e2fsck and e2libs and pray that they work.
--
You received this bug notification because you are a
Unable to check 17.10 ext4 file-system from 16.04 LTS (!).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1365874
Title:
Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not
Unable to check 16.10 ext4 file-system from 16.04 LTS (!).
Here is log:
sudo fsck -fy /dev/sdc1
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sdc1 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!
--
You received this bug
I would REALLY like metadata_csum to be backported for 16.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1365874
Title:
Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do
This is fixed in 16.10. Is there a plan to backport this? I'm guessing
not, because of the risk of regressions. If there's no plans to SRU,
then this bug should probably be closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1365874
Title:
Ubuntu 12.04 LTS, 14.04 LTS, 16.04
I reported bug 1601997 about setting 'metadata_csum' option on ext4
while installing fresh Ubuntu 16.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1365874
Title:
25 matches
Mail list logo
