[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Got exact same error from a current devtest.sh run
** Attachment added: screen shot of overcloud resize kernel oops
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233075/+attachment/4043543/+files/Overcloud_resizebug.jpg
--
You received this bug notification because you are a member
Steven's report is with saucy as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure with raring
Status in “linux” package in Ubuntu:
Incomplete
Bug
I've reproduced this recently with saucy, without the --max-resize
option, but only resizing to 20-30G from a 2G base, which is well within
the heuristics ext4 has.
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of
This appears to be fixed actually (reference in other bug)
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
Correct status is a bit hard to say as the problem was the journal which
was defined too small given the image size on creation. There may or may
not be a better way to detect this and bail early.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Nuts, wrong reference...
We may have found some more data on the situation: bug 1233008 reports
on a failure to resize with the same images..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We may have found some more data on the situation: bug 1233024 reports
on a failure to resize with the same images..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
So as of IRC feedback this seems to work on a current Quantal kernel.
Which means the next steps should be to verify on one side whether for
example the originally released Raring kernel (3.8.0-19.29) already
showed that problem and on the other side whether a current Saucy
(3.11.0-9.16) kernel
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure with raring
interestingly quantal didn't resize, but it didn't lockup either.
Definitely more investigation warranted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233075
Title:
resizefs failure
huh,
root@undercloud-notcompute-jws3awlsb2kh:/home/heat-admin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 1.8T 0 disk
��sda1 8:1020G 0 part /
12 matches
Mail list logo
