Brett Bergquist
Dabbler
- Joined
- Jun 7, 2017
- Messages
- 13
I have created a 3TB zvol that I share as an ISCSI target to a Sun M3000 server running Solaris 10/9. The FreeNAS server and the M3000 server are connected by a 10GBASE-CX4 directly connected to each other with a good cable. Both the FreeNAS server and the M3000 server are for lab use in staging and replicating a customer operation environment with relatively large database (about 600G).
The M3000 creates a zpool using the ISCSI target. On this pool a ZFS filesystem is created and within that, a Solaris Zone is created. The zone is populated using 2 compressed TAR files containing the application operating code and a copy of the database.
This all works without errors including networking errors, I/O errors, ISCSI errors, or any error being reported by FreeNAS including scrubbing the pool with the zvol.
However from M3000 server, right after populating the zpool/filesystem, I run "zpool scrub", the pool reports a couple of checksum errors. I have no idea why this might be occurring. I have destroyed the pool, destroyed the vol on the FreeNAS server, recreated everything and still get a couple of checksum errors each time I set this up.
Any ideas will be greatly appreciated.
FreeNAS hardware:
All of the Hitachi UltraStar drives have had SMART diagnostics run with no errors being reported.
Storage setup below. 2 of the SSD drives are used a the ZFS cache devices (one for each pool). The 3'rd SSD drive is the boot device. The 3 6TB drives are going to be just used as for backup storage usage.
The "M0/m3000space" is the zvol that is shared as the ISCSI target to the M3000.
The M3000 creates a zpool using the ISCSI target. On this pool a ZFS filesystem is created and within that, a Solaris Zone is created. The zone is populated using 2 compressed TAR files containing the application operating code and a copy of the database.
This all works without errors including networking errors, I/O errors, ISCSI errors, or any error being reported by FreeNAS including scrubbing the pool with the zvol.
However from M3000 server, right after populating the zpool/filesystem, I run "zpool scrub", the pool reports a couple of checksum errors. I have no idea why this might be occurring. I have destroyed the pool, destroyed the vol on the FreeNAS server, recreated everything and still get a couple of checksum errors each time I set this up.
Any ideas will be greatly appreciated.
FreeNAS hardware:
- Norco RPC-4220 4U Rackmount Server Case with 20 Hot-Swappable SATA/SAS Drive Bays, MiniSAS Connector
- SuperMicro X9DRL-iF Motherborard
- 64G of ECC Memory
- 2 Intel Xeon E5-2670 Sandy Bridge-EP 2.6GHz (3.3GHz Turbo Boost) 20MB L3 Cache LGA 2011 115W BX80621E52670 Server Processor
- LSI SAS 9201-16I HOST BUS ADAPTER
- 17 Hitachi Ultrastar™ 7K3000 2TB SATA 6Gb/sec Hard Drives
- 3 Toshiba 7200 6TB SATA 6Gbs/sec Hard Drives
- 3 250G SSD Drives
- Chelsio 10GBASE-CX4 Dual Port Network Card
- UPS powered
All of the Hitachi UltraStar drives have had SMART diagnostics run with no errors being reported.
Storage setup below. 2 of the SSD drives are used a the ZFS cache devices (one for each pool). The 3'rd SSD drive is the boot device. The 3 6TB drives are going to be just used as for backup storage usage.
Code:
[root@sanserver] ~# zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT M0 7.25T 603G 6.66T - 12% 8% 1.00x ONLINE /mnt M1 7.25T 2.45G 7.25T - 0% 0% 1.00x ONLINE /mnt S0 16.2T 6.12M 16.2T - 0% 0% 1.00x ONLINE /mnt freenas-boot 232G 888M 231G - - 0% 1.00x ONLINE - [root@sanserver] ~# zpool status pool: M0 state: ONLINE scan: scrub repaired 0 in 1h50m with 0 errors on Tue Jun 6 22:46:53 2017 config: NAME STATE READ WRITE CKSUM M0 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/0bc62866-f213-11e6-b0a5-00074305936a ONLINE 0 0 0 gptid/251782ff-f2fe-11e6-b22e-00074305936a ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gptid/457367a0-f213-11e6-b0a5-00074305936a ONLINE 0 0 0 gptid/491ef03c-f213-11e6-b0a5-00074305936a ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 gptid/e6a0d5ea-f216-11e6-b0a5-00074305936a ONLINE 0 0 0 gptid/be224a19-f45b-11e6-9a35-00074305936a ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 gptid/1f491cbe-f21b-11e6-b0a5-00074305936a ONLINE 0 0 0 gptid/233ecfb2-f21b-11e6-b0a5-00074305936a ONLINE 0 0 0 cache ada0p1 ONLINE 0 0 0 errors: No known data errors pool: M1 state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Sun May 7 00:00:25 2017 config: NAME STATE READ WRITE CKSUM M1 ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gptid/9ad3caa1-13b0-11e7-9d6f-00074305936a ONLINE 0 0 0 gptid/7fc6767b-f559-11e6-ad35-00074305936a ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 gptid/9836ff68-f559-11e6-ad35-00074305936a ONLINE 0 0 0 gptid/9c35cc68-f559-11e6-ad35-00074305936a ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 gptid/b1d1edef-f559-11e6-ad35-00074305936a ONLINE 0 0 0 gptid/b4d6bdce-f559-11e6-ad35-00074305936a ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 gptid/cf9d2d83-f559-11e6-ad35-00074305936a ONLINE 0 0 0 gptid/d27fc5b6-f559-11e6-ad35-00074305936a ONLINE 0 0 0 cache ada0p2 ONLINE 0 0 0 errors: No known data errors pool: S0 state: ONLINE scan: scrub repaired 0 in 0h0m with 0 errors on Sun May 28 00:00:01 2017 config: NAME STATE READ WRITE CKSUM S0 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 gptid/7850cb65-0413-11e7-ad35-00074305936a ONLINE 0 0 0 gptid/792d7b32-0413-11e7-ad35-00074305936a ONLINE 0 0 0 gptid/7a83c4db-0413-11e7-ad35-00074305936a ONLINE 0 0 0 errors: No known data errors The FreeNAS filesystems look like. Here is the "zfs list" [root@sanserver ~]# zfs list NAME USED AVAIL REFER MOUNTPOINT M0 3.05T 3.97T 23K /mnt/M0 M0/.system 417M 3.97T 402M legacy M0/.system/configs-ea02119b0df4495ba64ec1dbdd61ed06 8.62M 3.97T 8.62M legacy M0/.system/cores 706K 3.97T 706K legacy M0/.system/rrd-ea02119b0df4495ba64ec1dbdd61ed06 23K 3.97T 23K legacy M0/.system/samba4 83.5K 3.97T 83.5K legacy M0/.system/syslog-ea02119b0df4495ba64ec1dbdd61ed06 4.85M 3.97T 4.85M legacy M0/jails 23K 3.97T 23K /mnt/M0/jails M0/m3000space 3.05T 6.43T 601G - M1 1016G 6.03T 23K /mnt/M1 M1/debianspace 1016G 7.02T 2.45G - S0 3.91M 10.5T 117K /mnt/S0 freenas-boot 888M 224G 176K none freenas-boot/ROOT 879M 224G 136K none freenas-boot/ROOT/Initial-Install 8K 224G 848M legacy freenas-boot/ROOT/default 879M 224G 874M legacy freenas-boot/grub 7.29M 224G 7.29M legacy
The "M0/m3000space" is the zvol that is shared as the ISCSI target to the M3000.
Last edited by a moderator: