NAS4Free, Take2, Success!

I fixed it!  That Samba crash I had while reading data from NAS - it is fixed!
I recreated mirror zpool, redid all CIFS/SMB settings, recreated shares, restarted the service and it just works!  Let me dig deeper to figure out what exactly had the effect!

Now somebody help me to understand this:

nas:~# diskinfo -v ada0
ada0
        512             # sectorsize
        4000317440      # mediasize in bytes (3.7G)
        7813120         # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        7751            # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        DKZ112610180725 # Disk ident.

nas:~# diskinfo -v ada1
ada1
        512             # sectorsize
        500107862016    # mediasize in bytes (465G)
        976773168       # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        969021          # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        WD-WCAWF0558229 # Disk ident.

nas:~# diskinfo -v ada2
ada2
        512             # sectorsize
        2000398934016   # mediasize in bytes (1.8T)
        3907029168      # mediasize in sectors
        4096            # stripesize
        0               # stripeoffset
        3876021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        6YD20H52        # Disk ident.

nas:~# diskinfo -v ada3
ada3
        512             # sectorsize
        2000398934016   # mediasize in bytes (1.8T)
        3907029168      # mediasize in sectors
        4096            # stripesize
        0               # stripeoffset
        3876021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        6YD1Z7CA        # Disk ident.

nas:~# gpart show ada0
=>      0  7813120  ada0  BSD  (3.7G)
        0       16        - free -  (8.0k)
       16   179408     1  freebsd-ufs  (87M)
   179424  7633696        - free -  (3.7G)

nas:~# gpart show ada1
=>       34  976773101  ada1  GPT  (465G) [CORRUPT]
         34         94        - free -  (47k)
        128    4194304     1  freebsd-swap  (2.0G)
    4194432  972578703     2  freebsd-zfs  (463G)

nas:~# gpart show ada2
gpart: No such geom: ada2.
nas:~# gpart show ada3
gpart: No such geom: ada3.

Here ada0 is my compact flash card in PATA, ada1 is OpenIndiana boot disk - why does it have corrupted partition table?  The fun part is that ada2 and ada3 used for zpool mirror are not visible to gpart. Yet they are perfectly listed in web GUI!  And in the system log I see this:

Apr 8 22:20:03  nas  kernel: GEOM_NOP: Device ada2.nop created.
Apr 8 22:20:03  nas  kernel: GEOM_NOP: Device ada3.nop created.

I am at a big loss here.
Here is network throughput as measured from HTPC:

File System	Read (MB/s)	CPU use (%)	Write(MB/s)	CPU use (%)
ZFS mirror on Barracuda Greens connected to ICH7 SATA2 ports	40	20	40	40-50

But this is not a whole story.  Here is network throughput graph:

Writing to NAS is done at a relatively steady pace, around 40MB/sec while using substantial CPU resources.  It would be still interesting to learn why such deep dips happen now and then.  Reading pace on the other hand is anything but steady.  Understandably CPU usage is much lower.

Checked Enable large read/write in the advanced section of Services|CIFS/SMB|Settings.  Restarted.  Writing unaffected.  Reading is steadier but at a lower rate.  No crashes!



Enable use sendfile setting can not be saved - is it because sendfile is not supported in BSD?
Will follow up after NIC upgrade on this guide.
Let's do a stress test!  I will copy all the movies - 1.05TB - to NAS now!  Windows is telling me it will take 8 hours.  Steady 40MB/sec write, disks at 35°C and 33°C, CPU utilization 50% +10% -20%