On Mon, Apr 04, 2011 at 09:24:28AM -0500, Moffett, Kyle D wrote: > > 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.
Sigh, I was whoping someone was maintaining semi-official EC2 images for Debian, much like alestic has been maintaining for Ubuntu. (Hmm, actually, he has EC2 images for Lenny and Etch, but unfortunately not for squeeze. Sigh....) > 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. Couple of questions which might give me some clues: (a) was this a natively formatted ext4 file system, or a ext3 file system which was later converted to ext4? (b) How big are the files/directories involved? In particular, how big is the Postfix mail queue directory, and it is an extent-based directory? (what does lsattr on the mail queue directory report) As far as file sizes, does it matter how big the e-mail messages are, and are there any other database files that postgress might be touching at the time that you get the OOPS? I have found a bug in ext4 where we were underestimating how many journal credits were needed when modifying direct/indirect-mapped files (which would be seen on ext4 if you had a ext3 file system that was converted to start using extents; but old, pre-existing directories wouldn't be converted), which is why I'm asking the question about whether this was an ext2/ext3 file system which was converted to use ext4. I have a patch to fix it, but backporting it into a kernel which will work with EC2 is not something I've done before. Can anyone point me at a web page that gives me the quick cheat sheet? > 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. If we can reproduce the problem on that base image it would be really great! I have an Amazon AWS account; contact me when you have an image you want to share, if you want to share it just with my AWS account id, instead of sharing it publically... - Ted -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org