i think barrier=0 in /etc/fstab fixed this for me, but there might
have been conflating factors
On Tue, Jun 7, 2011 at 5:23 PM, Mikhail P <email address hidden> wrote:
> Still seeing this issue with 2.6.35-24-virtual.
>
> Adam, You said you are using -28 - perhaps there's something further on
> that fixes? Are you still problem-free?
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (667656).
> https://bugs.launchpad.net/bugs/666211
>
> Title:
> maverick on ec2 64bit ext4 deadlock
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> 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
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/666211/+subscribe
>
i think barrier=0 in /etc/fstab fixed this for me, but there might
have been conflating factors
On Tue, Jun 7, 2011 at 5:23 PM, Mikhail P <email address hidden> wrote: /bugs.launchpad .net/bugs/ 666211 domain/ 0/backend/ vbd/161/ 2049/feature- barrier. domain/ 0/backend/ vbd/161/ 2049/feature- flush-cache. kernel/ hung_task_ timeout_ secs" disables this message. alestic. com/2010/ 10/ec2- ubuntu- maverick# comment- 484 developer. amazonwebservic es.com/ connect/ entry.jspa? externalID= 4350 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/666211/ +subscribe
> Still seeing this issue with 2.6.35-24-virtual.
>
> Adam, You said you are using -28 - perhaps there's something further on
> that fixes? Are you still problem-free?
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (667656).
> https:/
>
> Title:
> maverick on ec2 64bit ext4 deadlock
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> 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/
> Failed to read /local/
>
> 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/
> 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://
>
> AMI:
> http://
>
> To unsubscribe from this bug, go to:
> https:/
>