On Apr 02, 2011, at 22:02, Ted Ts'o wrote: > Sorry for not following up sooner. Are you still able to reproduce > this failure? If I set up an identical Debian stable instance on > EC-2, am I likely to reproduce it myself? Do you have a package list > or EC2 base image I can use as a starting point?
I'll need to check on this. Unfortunately it was not a trivial process to install Debian "squeeze" onto an EC2 instance; it took a couple ugly Perl scripts, a patched Debian-Installer, and several manual post-install-but-before-reboot steps (like fixing up GRUB 0.99). One of these days I may get time to update all that to the official "wheezy" release and submit bug reports. I have an exact image of the failing instance, but it has proprietary data on it and if I stand up an old copy I need to be careful not to actually let it send all the queued emails :-D. It's probably easier for me to halt email delivery and clone the working instance and try to reproduce from there. If I recall, the (easily undone) workaround was to remount from "data=journal" to "data=ordered" on a couple filesystems. It may take a day or two to get this done, though. If it comes down to it I also have a base image (from "squeeze" as of 9 months ago) that could be made public after updating with new SSH keys. Thanks again! Cheers, Kyle Moffett -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/15e8241a-37a0-4438-849e-a157a376c...@boeing.com
