image of files system in the before state
** Attachment added: "root.qcow2.gz"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+attachment/5156793/+files/root.qcow2.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is the output after the resize. The original was 59.02 GB and I am
resizing to 30G.
** Attachment added: "after.txt"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+attachment/5156598/+files/after.txt
--
You received this bug notification because you are a member of
Here is the dump2efs before the filesystem resize was attempted.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1778140/+attachment/5156597/+files/before.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was offline, run off the Ubuntu live cd. I will get back to you on
the rest on Monday.
From: on behalf of Theodore Ts'o
Reply-To: Bug 1778140 <1778...@bugs.launchpad.net>
Date: Friday, June 22, 2018 at 19:50
To: Maurice R Volaski
Subject: [Bug 1778140] Re: resize2fs hoses a filesystem on
The bug is also present resize2fs 1.43.6. I tried to post directly to
sourceforge for the project, but it doesn't allow me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778140
Title:
resize2fs
Public bug reported:
Resized an ext4 filesystem on LVM. Before resizing, I confirmed
filesystem was clean with e2fsck. After resizing, three errors were
found.
root@ubuntu:~# e2fsck -f /dev/ubuntu-vg/root
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Inode 21110 extent
Public bug reported:
To reproduce this bug, take the following steps
Install Ubuntu 20.04.3 using a ZFS-based root.
Boot into it and get past the initial startup screens.
Take a manual recursive zfs snapshot like so
zfs snapshot -r rpool@beforeanything
Now touch a file on the desktop and
** Description changed:
To reproduce this bug, take the following steps
- Install Ubuntu 20.04.3.
+ Install Ubuntu 20.04.3 using a ZFS-based root.
Boot into it and get past the initial startup screens.
Take a manual recursive zfs snapshot like so
zfs snapshot -r
Public bug reported:
To reproduce this bug, take the following steps
Install Ubuntu 20.04.3 using a ZFS-based root.
Boot into it and get past the initial startup screens.
Install a package like htop to force the creation of a ZSys snapshot and
for additional confirmation in the user space,
Two things. First, I created a separate bug for the failure to revert
ZSys snapshots,
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1950330.
Second, this here is clearly a bug despite Didier's claims to the
contrary. Regular snapshots appear in the menu. Why would anyone think
they are not
>also closing tentatively as opinion
Is this going to be reopened or shall I file new for the Zsys bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949490
Title:
Grub doesn’t fully revert ZFS
If we use a ZSys-created snapshot, first the system hangs after being
reverted. And then nothing is reverted at all. Either that, I should
wait an inordinate amount of time for the revert to happen while the
system is hung.
So there are in this sense, two bugs here, one, the hang, and two the
12 matches
Mail list logo
