** 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 filesystem from the Ubuntu installer.
+ [Test cases]
  Test Case 1:
  With e2fsprogs 1.44.4-2:
  Download this file system image:
  Run the following commands:
  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 extent
-         (logical block 1272, physical block 466167, len 776)
+         (logical block 1272, physical block 466167, len 776)
  Test Case 2 (Use case of the installer):
  1. Perform a first installation of Ubuntu
  2. Reboot into the freshly installed system and verify everything works as 
  3. Do a second installation and select "Install alonogside". Keep the size 
proposed by the installer and proceed to the end of installation
  4. Reboot
  5. On boot, in the list of installed systems, select the first system 
installed on the machine
  6. Verify that it boots, you can login and it works as expected
  Actual Result
  The FS is corrupted and depending on the corruption it goes to initramfs, 
boots but cannot login, ...
+ [Regression potential]
+ This changes behavior in the update logic for extent blocks; as such, care 
should be taken to make sure that testing takes into account the possibility to 
introduce filesystem corruption while resizing. This is why the test cases 
include running e2fsck as last step.
+ ---
  Attached is the journal of the system installed on the corrupted
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 10:53:57 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-10-18 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.

  After a side by side installation, resized filesystem is corrupted

To manage notifications about this bug go to:

kubuntu-bugs mailing list

Reply via email to