Doesn't look like the fixed version was ever pushed out to Trusty. If you are
using trusty and need this fixed, simply download the source to your machine
and compile it. If you have the build-essential and git packages installed,
it's quite simple. Clone the git repo source for the latest versi
This should be fixed in Vivid and later then.
** Changed in: e2fsprogs (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321958
Title:
resize2fs does no
according to
http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.42.13
this BUG is fixed in e2fsprogs 1.42.12 or higher.
"Fix a 32/64-bit overflow bug that could cause resize2fs to loop
forever. (Addresses-Launchpad-Bug: #1321958)"
is it possible to backport the newest e2fsprogs package to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu Trusty)
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/1321958
Ti
** Changed in: e2fsprogs (Ubuntu Trusty)
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/1321958
Title:
resize2fs does not start to actually grow an ext4
To manage no
** Tags added: trusty
** Also affects: e2fsprogs (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: e2fsprogs (Ubuntu Trusty)
Milestone: None => trusty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Increasing importance due to possible denial-of-service during a resize
of large 'complex' file-systems. In this case both reports using DM RAID
6.
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided => High
** Changed in: e2fsprogs (Ubuntu)
Status: Confirmed => Triaged
--
You rec
I ran e2fsck on this disk, and it found quite alot of problems with
early inodes. After e2fsck completed almost all the root folders were
moved to lost+found. I managed to restore the data by moving them back
from lost+found.
I'd like to note that although I ran resize2fs with the -f flag, I did
r
I have just tried this patch (to resize2fs.c. There is another patch for
resize.c, but I dont have a resize.c in the 1.42.11 src tree), but it
didn't work out the way I'd like.
It seems to went all okay:
/dev/sdb 29T 26T 2.1T
93% /backups
root@
Someone has reported what appears to be the same problem on the linux-
ext4 list, and between correlations of the observations from Dennis
(Thermaltaker) and on the linux-ext4 list, I believe we have a fix that
should address this problem:
http://thread.gmane.org/gmane.comp.file-systems.ext4/44870
** Attachment added: "resize.1.42.8.strace.gz"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+attachment/4159871/+files/resize.1.42.8.strace.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
This bug also affects me. I have tested the new 1.42.11 but no success.
Attached the strace; the debug log is empty for my setup also.
In addition I added a strace/debug file of the 1.42.8 which worked. I hope that
might be helpful.
** Attachment added: "resize.1.42.11.strace"
https://bugs.
** Attachment added: "resize.1.42.8.debug.gz"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+attachment/4159872/+files/resize.1.42.8.debug.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I should maybe mention that both commands showed the same hanging
behaviour again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321958
Title:
resize2fs does not start to actually grow an ext4
To
Here is the output of strace. The resize with - 31 did only produce an
empty file.
** Attachment added: "resize.strace"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+attachment/4117436/+files/resize.strace
--
You received this bug notification because you are a member of
If someone could try running the following tests, it would be very
useful.
1) strace -o /tmp/resize.strace resize2fs /dev/XXX
2) resize2fs -d 31 /dev/XXX | tee /tmp/resize.debug
And then upload the files of the "hanging" resize2fs. It's not
something I've been able to reproduce when doing a q
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (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/1321958
Title:
I had similar problem, 24TB raid 6 array growing to 48TB raid 6 array.
Downgraded to 1.42.8 and was able to resize filesystem. However, with
20TB raid 5 grown to 24TB raid 5 I did not encounter issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
18 matches
Mail list logo
