AoE target storage clarification

Thanks to Serge, I fixed the udev weirdness I had earlier.

As I mentioned before, I'm looking to replace my Archlinux Samba server with the possibility of using AoE.

I've been using the following as my guide to AoE http://www.howtoforge.com/low-cost-san

For testing, I'm using my Archlinux 3.1.2 kernel machine as the target with the following in /etc/rc.local:

/sbin/modprobe aoe
/usr/sbin/vbladed 0 1 eth0 /dev/sdb1

/dev/sdb1 was formatted as a ext4 partition.

For the initiator, I used a Windows 7 x64 machine. The Windows machine was able to find the Linux target, then
I used Computer Management to format the storage as a NTFS drive. Then a copied a test file of several
hundred megabytes which worked. Even rebooted the Linux and WIndows machine to confirm the test file was
still around, which it was.

However, when it came time see if the Linux machine can see the test file, I turned off the Windows machine and
rebooted the Linux machine with the modprobe and vblade commands commented out in /etc/rc.local.

Then on the Linux machine I typed, 'mount -r -t ntfs /dev/sdb1 /mnt' but it came back with the error message of
wrong fs type, bad superblock, bad option on /dev/sdb1. Even did 'mount -r -t ext4/dev/sdb1 /mnt' with
same error message.

So, my question is, how does a Linux target host mount a client's initiator storage device? Just want to
confirm the test file on the Linux machine. Guess I am asking for the functionality of the Linux machine to
see what the Windows machine is putting on the storage device. I can currently do that with Samba by going to
the SMB share on the Linux machine.