[Bug 666211] [NEW] maverick on ec2 64bit ext4 deadlock
Timo Derstappen
teemow at gmail.com
Mon Oct 25 10:19:22 UTC 2010
Public bug reported:
I created an ami from the official image (ami-505c6924 – region eu-
west-1). the rebundled image works fine for a while but ends with nearly
100% iowait and a load of 6000.
The instance type is m1.xlarge without ebs.
There are errors in the amazon console before the kernel starts (see attached boot.log):
Failed to read /local/domain/0/backend/vbd/161/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/161/2049/feature-flush-cache.
If you are lucky you see errors in the syslog like this:
INFO: task jbd2/sda1-8:235 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
jbd2/sda1-8 D ffff880003bcd980 0 235 2 0x00000000
ffff8801b5f49b20 0000000000000246 0000000000000000 0000000000015980
ffff8801b5f49fd8 0000000000015980 ffff8801b5f49fd8 ffff8801b571db80
0000000000015980 0000000000015980 ffff8801b5f49fd8 0000000000015980
The machines are unusable after a few hours. I am testing those images
right now. There is no heavy load expected. Karmic images work fine.
Packages I've installed are build-essential, git-core, ruby, nginx and
couchdb. Node.js is compiled manually.
The same error is described on Alestic by Jay Freeman, unfortunately he didn't open any bug here:
http://alestic.com/2010/10/ec2-ubuntu-maverick#comment-484
AMI:
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=4350
** Affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
maverick on ec2 64bit ext4 deadlock
https://bugs.launchpad.net/bugs/666211
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
More information about the kernel-bugs
mailing list