Problem with ZFS and devices

I have a really strange problem with ZFS.

I have a filesystem (mypool/scr mounted on /scr) which contains root file
systems for various embedded boards (arm, ppc, mips). The file systems
naturally contain a /dev directory.

I have:
mypool/scr  devices        on                     default

The device numbers a _totally_ fubar on ZFS!

I used a tarball called dev.tar to move dev from a Linux box to my FreeBSD
box.

When I unpack dev.tar under ZFS I see totally screwd up values:

crw-r--r--  1 root  bin      5, 0xc11b0020 Feb  3 22:06 ttyCPM0
crw-r--r--  1 root  bin      0,   0 Feb  3 22:06 ttyCPM1
crw-r--r--  1 root  bin     69, 0xc11a0008 Feb  3 22:06 ttyCPM2
crw-r--r--  1 root  bin      0,   0 Feb  3 22:06 ttyCPM3
crw-r--r--  1 root  bin      0,   0 Feb  3 22:06 ttyCPM4
crw-r--r--  1 root  bin     69, 0xc11a0008 Feb  3 22:06 ttyCPM5

If I unpack dev.tar under UFS (/tmp) then all device numbers are correct:

crw-r--r--  1 root  bin    204,  46 Feb  3 22:06 ttyCPM0
crw-r--r--  1 root  bin    204,  47 Feb  3 22:06 ttyCPM1
crw-r--r--  1 root  bin    204,  48 Feb  3 22:06 ttyCPM2
crw-r--r--  1 root  bin    204,  49 Feb  3 22:06 ttyCPM3
crw-r--r--  1 root  bin    204,  50 Feb  3 22:06 ttyCPM4
crw-r--r--  1 root  bin    204,  51 Feb  3 22:06 ttyCPM5

The screwed up device numbers prevent me from using my FreeBSD box as the
server for my embedded boards.

Even weirder:

root:peedub:~:bash:1> cd /scr/eldk-4.1/arm/arm/dev
root:peedub:dev:bash:2> mknod ttyCPM0 c 204 46
root:peedub:dev:bash:3> ls -l
total 1
crw-r--r--  1 root  bin    0,   0 Apr 22 13:02 ttyCPM0

Any ideas WTF is going here? Is this a pathological problem with ZFS?

-- 
Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde