after looking at the console pointed at in comment 3, I thought i might be able to trigger this by issuing 'reboot-instances' on a running node. I was not successful in doing so.
In a instance of:
eu-west-1 ami-738fb007 ubuntu-precise-daily-i386-server-20120119
I issued reboot via 'euca-reboot-instances' 10 times and colllected log output (the low number is really because it takes 5m to get a console output). None of these resulted in the fsck issue.
after looking at the console pointed at in comment 3, I thought i might be able to trigger this by issuing 'reboot-instances' on a running node. I was not successful in doing so.
In a instance of: precise- daily-i386- server- 20120119
eu-west-1 ami-738fb007 ubuntu-
I issued reboot via 'euca-reboot- instances' 10 times and colllected log output (the low number is really because it takes 5m to get a console output). None of these resulted in the fsck issue.