This bug was fixed in the package e2fsprogs - 1.44.1-1ubuntu1.1
---
e2fsprogs (1.44.1-1ubuntu1.1) bionic; urgency=medium
* d/patches/0001-resize2fs-update-checksums-in-the-extent-tree-s-relo.patch:
do the checksum update later in extent tree relocated block to denote the
:Verification-done for cosmic:
ubuntu@superb-ram:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@superb-ram:~$ e2fsck -f vda1b.raw
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking
This bug was fixed in the package e2fsprogs - 1.44.4-2ubuntu0.2
---
e2fsprogs (1.44.4-2ubuntu0.2) cosmic; urgency=medium
* d/patches/0001-resize2fs-update-checksums-in-the-extent-tree-s-relo.patch:
do the checksum update later in extent tree relocated block to denote the
Verification-done for bionic using e2fsprogs 1.44.1-1ubuntu1.1:
ubuntu@humble-cod:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@humble-cod:~$ e2fsck -f vda1b.raw
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking
I installed e2fsprogs 1.44.4-2 via cosmic-proposed, according to the
instructions.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
I did both testcases. There was no error detected in in testcase #1, and
no error detected in testcase #2, so things seem to work :-)
Details:
- There was a test installation of Ubuntu 18.04.1 LTS in a Toshiba laptop with
an SSD.
- I cloned a Lubuntu 18.10 iso file to a USB pendrive and
** Tags added: id-5c49e9dab8b59b7d3bbca789
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
After a side by side installation, resized filesystem is corrupted
To manage notifications
Hello Jean-Baptiste, or anyone else affected,
Accepted e2fsprogs into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/e2fsprogs/1.44.4-2ubuntu0.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Also affects: e2fsprogs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ - Users resizing filesystems using resize2fs.
+ - Resizing an existing Linux
This has been fixed in the e2fsprogs version in Disco.
[ 8:40AM 10668 ] [ bdmurray@impulse:/tmp/e2fsprogs-1.44.5 ]
$ grep -B1 1798562 doc/RelNotes/v1.44.5.txt
Fix a bug where resize2fs was failing to update the extent tree
checksums in an corner case. (Addresses Launchpad Bug: #1798562)
**
Hello , I face same issue
it shows busybox command line and says file system is corrupted ( tells
to use fsck)
and after doing that from live disk ( i saw it was asking to move nodes
which repairing ) the next time system reboots the kernel panics, errors
were " not syncing attempting to kill"
The attachment "resize2fs: update checksums in the extent tree's
relocated block" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
Thanks for the very nice repro!I've created a fix which will be
going into the maint branch of the e2fsprogs tree. The commit
description:
resize2fs: update checksums in the extent tree's relocated block
When shrinking an file system, and we need to relocate an inode, the
** Description changed:
- Test Case:
+ Test Case 1:
+ With e2fsprogs 1.44.4-2:
+
+ Download this file system image:
+
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz
+
+ Run the following commands:
+
+ bunzip2 vda1b.qcow2.bz
+
** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Importance: High => Critical
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With e2fsprogs 1.44.4-2:
bunzip2 vda1b.qcow2.bz
qemu-img convert vda1b.qcow2 vda1b.raw
e2fsck -f vda1b.raw
resize2fs vda1b.raw 6200M
e2fsck -f vda1b.raw
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Inode 45746 extent block passes checks, but checksum does not match
Possibly related issues:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1783757
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Personally I've fone this first install entire disk ->boot in the os and
restart it -> install alongside-> boot in the second os and then restart
and boot in the first one.all in uefi mode.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the
Just reporting that I was unable to reproduce it in any system
combination, even in the original cosmic next to cosmic case. Same for
bionic on cosmic, cosmic on bionic, cosmic on fedora. So it seems the
issue is not easily reproducible in all cases, must be some specific
combination of components
Apparently it's clearly reproducible with Cosmic alongside Cosmic.
Has anyone been able to reproduce with Cosmic alongside something else
than Cosmic such as an earlier release, another distribution or
operating system?
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
After a side by side installation, resized filesystem is corrupted
To
In Kubuntu with Virtualbox, I end up with the resized Cosmic partition
bootable and starts, but read is read only.
Plenty of KDE error not being able to write config files to the user
home.
Ext4 errors shown in attached screenshot.
** Attachment added: "ext4errors.png"
Cosmic entire disk + cosmic auto-resize (install alongside)
P.S uifi version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
After a side by side installation, resized filesystem is
I had this problem after the uefi fix.in Ubuntu Mate 20181017.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
After a side by side installation, resized filesystem is corrupted
To
@Apolihron, yes but depending on the corruption the system can go into
initramfs if it completely fails to boot (your screenshot), it may boot
but the FS will be RO, or it may recover transparently and all sort of
other side effects are possible.
--
You received this bug notification because you
@APoliihron, when it happened to you what was the original operating
system that you resized? Was it cosmic on cosmic or something else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798562
Title:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1798562
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Last night this problem made me go crazy. Because if you install again 2
os's for dual boot the problem will NOT persists. I can't reproduce this
problem the second time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Do you get this screen?
** Attachment added: "IMG_20181018_025413.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1798562/+attachment/5202514/+files/IMG_20181018_025413.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This problems list night made me go crazy. Because if you install again
2 os's for dual boot the problem will NOT persists. I can't reproduce
this problem the second time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
31 matches
Mail list logo
