Initial findings with new Duo V2

I've already sent a few posts about my initial experience with the new Duo V2, but thought it easier to put it into one feedback post...

I've previously used the ReadyNAS Duo (V1) for a few years, with a final hardware configuration with 1GB RAM and 2x Seagate 2TB HDDs (ST2000DL003)

So, back to the new Duo V2 (running arm 5.3.2), this was the RND2000-200EUS (diskless) model - I'm UK-based, but there doesn't appear to a UK SKU, but the EU model does include a UK and Euro power cables...

Hardware Compatibility List:
This doesn't appear to have the 2TB version of my previous Seagate HDDs, but does have the 1.5TB version, so I initially installed the two ST2000DL003 drives.
I later replaced these with Western Digital (WD20EARX) 2TB HDDs (see below why)...

GUI:
Loads much faster, bit more bling, simpler to navigate, etc...
However, having been used to Front View, it is a bit limited. I can understand this, as it probably targetted to the home-user more than the pro-sumer...

Performance:
Read/writes over the network greatly improved - 40-50MB/s... However, going back to the GUI - you can't adjust the MTU, and currently it is not set up for Jumbo Packets ('ping -f -l' can easily prove that), would this improve performance?
(Works great over wireless too - but didn't benchmark).

DNLA:
I guess still under development - if you modify a file (e.g mp3 ID tag), it will still broadcasts the original version. Going back to the GUI - there is no option to 'Rescan Media'... Hopefully resolved with new firmware.

ReadyNAS Remote:
Doesn't work with iOS devices (iPhone/iPad, etc) as yet. Hopefully resolved with new firmware.

Volume Scan (i_block errors):
Here's my main issue - which might be a problem with my particular Duo V2...
When I did a Restart with Volume Scan, I would get a notification email about 'Volume scan found and corrected errors'. These errors were all related to: Pass 1: Checking inodes, blocks, and sizes - Inode 26181655, i_blocks is 739472, should be 739480. Fix? yes (for about 4-10 different Inode/i_block references). This occured after heavy writes made to the Duo. Once the Volume Scan corrected these errors, subsequent restarts had no errors until a large amount of more data was copied to the Duo.
I initially thought this was due to the Seagte drives not being on the HCL, so went out and purchased two new WD drives (WD20EARX) that were on the HCL... I rebuilt the Duo (volume build takes about 7 hours!). However, as before - started to get the same i_block erros on restart/volume scan... I've just reinstalled the arm 5.3.2 firmware and kicked off a factory reset, so we'll see what happens next...

Summary:
Much improved performance,but still early days in terms of the firmware... Fustration at possible RMA for a brand new (week-old) Duo V2...

Can someone please shed more light on these Inode/i_blocks erros please (below is a last example prior to reinstalling the firmware)...?

***** File system check performed at Sat Jan 7 10:11:28 WET 2012 *****
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Inode 26181655, i_blocks is 739472, should be 739480. Fix? yes

Inode 26181996, i_blocks is 547568, should be 547576. Fix? yes

Inode 26182037, i_blocks is 671744, should be 671752. Fix? yes

Inode 26182083, i_blocks is 594160, should be 594168. Fix? yes

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mapper/c-c: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/c-c: 14538/30285824 files (1.0% non-contiguous), 79676625/484573184 blocks