29 January 2010

The joys of EC2 and Debian

I'm setting up a new EC2 machine to be a MySQL replication slave. Unfortunately, I'm running in to some issues.

I started by creating a EBS volume to hold the database using the AWS management console. Then I attached it to the new system (ami-daf615b3, from alestic) used fdisk to make a partition, sdf1.

I created an XFS filesystem, just like I have before, using mkfs.xfs /dev/sdf1. That worked. But when I tried to mount it, I got this message:

# mount /dev/sdf1 /vol/
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Dmes showed the rather unenlightening:

XFS: bad version
XFS: SB validate failed

This thread suggested that kernel 2.6.16 and xfsprogs 2.9.6 were incompatible. I was running kernel 2.6.21 and xfsprogs 3.1.0, but I tried the workaround described therein: running mkfs.xfs with the option lazy-count=0. According to the documentation, that may cause a performance hit. Oh well. I recreated the FS and tried mounting it again.


domU-12-31-39-02-F5-F4:/home/jdb# mount /dev/sdf1 /vol/
domU-12-31-39-02-F5-F4:/home/jdb#
Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:------------[ cut here ]------------

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:invalid opcode: 0000 [#1]

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:SMP

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:CPU: 0

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:EIP: 0061:[] Tainted: GF VLI

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:EFLAGS: 00210282 (2.6.21.7-2.fc8xen-ec2-v1.0 #2)

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:EIP is at xen_pgd_pin+0x54/0x5e

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:eax: ffffffea ebx: c1439ef8 ecx: 00000001 edx: 00000000

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:esi: 00007ff0 edi: 00000000 ebp: c19d18f0 esp: c1439ef8

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0069

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:Process udevd (pid: 254, ti=c1439000 task=c1415670 task.ti=c1439000)

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:Stack: 00000002 0007e953 2cf6a000 0059ed40 00000000 c101816d c1bf2300 c1018196

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: c14f82dc c102250e c14f88d0 c1439fb8 c106e111 c1439fb8 bf8a8aa4 01200011

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: 00000000 c19d18f0 c1bf2300 c1346640 c14f82e8 c14f82fc c14f82f8 c1bf2300

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:Call Trace:

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] __pgd_pin+0x2f/0x3c

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] mm_pin+0x1c/0x23

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] copy_process+0xac3/0x10bc

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] kmem_cache_alloc+0x23/0x98

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] do_fork+0x51/0x13a

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] mntput_no_expire+0x11/0x6a

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] sys_clone+0x36/0x3b

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: [] syscall_call+0x7/0xb

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel: =======================

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:Code: eb fe a1 24 c2 38 c1 8b 14 90 81 e2 ff ff ff 7f 89 54 24 04 89 e3 b9 01 00 00 00 31 d2 be f0 7f 00 00 e8 36 54 fe ff 85 c0 79 04 <0f> 0b eb fe 83 c4 0c 5b 5e c3 56 89 c2 53 83 ec 0c c1 ea 0c 80

Message from syslogd@domU-12-31-39-02-F5-F4 at Jan 30 02:42:47 ...
kernel:EIP: [] xen_pgd_pin+0x54/0x5e SS:ESP 0069:c1439ef8


Now a kernel panic is not exactly a good sign. Maybe I'll try a non-alestic image next. Unfortunately, there are no other quasi-official Debian images that I know of. But there are Ubuntu images produced by Canonical. I tried this one, and so far, the filesystem has worked.

No comments:

Post a Comment

About Me

blog at barillari dot org Older posts at http://barillari.org/blog