SOLVED FreeNAS 9.3 FC Fibre Channel Target Mode DAS & SAN

[sfcredfox]

Has anyone using fibre channel upgraded from 9.3 to 9.10?

I'd like to know if all the system tunables remain functional and everything fibre channel still works?

 

[Holt Andrei Tiberiu]

Has anyone using fibre channel upgraded from 9.3 to 9.10?

I'd like to know if all the system tunables remain functional and everything fibre channel still works?

I am using FC on FreeNAS for more than 1 year, i can confirm that it is working on 9.10.X
I have 5 FreeNAS serving ISCSI over FC in production.
It would be nice to have a FC in FreeNAS, iSCSI over ETHERNET is SLOW, SLOWER than FC.
4 ang 8 gbs FC is cheap now, and unless you have SSD HDD's you won't saturate the 8 GBs link of FC
FC is much more stable than ETHERNET

 

[Stefan Pettersson]

Does anyone use freenas with an FC switch, say a HP switch? And, will freenas 10.0 work with FC also??

 

[sfcredfox]

Does anyone use freenas with an FC switch, say a HP switch? And, will freenas 10.0 work with FC also??

I am not using FreeNAS 10, but I am using a FC switch. It works fine for me. Since FreeNAS doesn't support LUN masking, I used zoning on the FC switch to only allow certain WWNs to talk on certain ports. Works great thus far.

 

[Stefan Pettersson]

Thanks! Was thinking about zoning to. On the freenas host, is it possible to see that there is an ISCSI target active? Command for the commandline??

 

[sfcredfox]

Any fibre channel users on 9.10.2 yet?

 

[Holt Andrei Tiberiu]

Yes, as i wrote, It works on 9.10.2 the same way as in 9.3, i use It on all of my boxes

 

[jokken]

sorry for a question that might be answered elsewhere

when using the FC/iscsi target support does the share/extend always have to be zfs?
i am most interested in FC, and i just want to have a ext3 filesystem shared via FC.

Currently I can see the zfs disks on my other FC systems
pci-0000:04:00.0-fc-0x2100001b32004b32-lun-0-part1
pci-0000:04:00.0-fc-0x2100001b32004b32-lun-0-part2
mount /dev/sdc2 /mnt/fcshare
mount: unknown filesystem type 'zfs_member'

thanks!

 

[mav@]

when using the FC/iscsi target support does the share/extend always have to be zfs?
i am most interested in FC, and i just want to have a ext3 filesystem shared via FC.

I'd say that your question sounds odd. The fact that FreeNAS typically stores its FC/iscsi extents on ZFS in no way limits what file system will be stored on top of that by initiators. My best guess is that you somehow managed to share your raw disk of your FreeNAS, that in 99% is not a right way.

 

[jokken]

ok, that is good news to hear. something i suspected. but since im kinda lost and no real FC experience, ill have to ask: how can I create a filesystem on top if that? using initiators in the FreeNAS webUI?

 

[jokken]

ha, if my question sounded odd, then my response to your answer must of sounded even odder. haha
So I must of created a zfs filesystem using the wizard at some earlier point.
so when I shared the disk it was a zfs disk.
the extent was presented as "/dev/disk/by-path/pci-0000:04:00.0-fc-0x2100001b32004b32-lun-0" on the initiators, which became sdc to them.
The sdc1 and sdc2 partitions were the zfs filesystem.
I used fdisk to remove both of them and create a single sdc1 partition as the XFS file system, and can now use it

so it is a bit clearer to me now, although im not 100%, i will continue to use freenas and learn. pretty neat software,

thanks for the help!

 

[ZippyZoodles]

Has anyone confirmed this is still working on FreeNAS Corral?

 

[Skynet3020]

Hi at all

i can confirm that FC run since 9.3 also in 9.10u1 u2 u3 and now i'm on 11.0-RC2 (a4687be8c)

the only one on all version... can i do something to get a better performance ?

i got in a OS X VM System from esxi 6.0 with 4g card's (booth ports are connected)
only 132-219 MB/s write and 192-260 MB/s Read.
In the internal HBA (P410) with 2.5" HDD i got 203 MB/s write and 192MB/s Read

The freenas HBA are 2x LSI SAS 9211-8i with
4 Drives WD Red from 2014/2014 in Raid10
another 4 WD Black 2014 drives in Raid10
7 drives in a RAID Z2 (misc WD drives from 2011-2016 but this drive is not in this VM (only 4 Backups)

All Raid's are managed by Freenas

Testet with aja lite 16GB file

i know drives are not so fast but are this values ok or bad ?

 

[HermesGroup]

It also works the same way on version 11.0-RC
Thanks for all the tips.

Johnny R.

 

[Don Intellys]

Got everything setup and it is working. I ran into a problem.

I'll start with the specifications:

• motherboard make and model

SuperMicro X9DRD-7LN4F

• CPU make and model

2x Intel Xeon E5-2620

• RAM quantity

128 GB

• hard drives, quantity, model numbers, and RAID configuration

Primary (boot) drive - (2) 120 GB Intel SpeedDemon SSD model SSDSC2BB120G401 mirrored

Storage drives - (12) Western Digital RE WD4001FYYG 4TB 7200 RPM 32MB Cache SAS 6Gb/s 3.5" Enterprise Internal Hard Drive (RAIDZ2)
(4) Seagate 4TB SSHD (RAIDZ1)

Cache/Log drives - (4) 120 GB Intel SpeedDemon SSD model SSDSC2BB800G401

• hard disk controllers

Broadcom 2308 SAS2

• network cards

Intel® i350 Quad Port Gigabit Ethernet

• FibreChannel cards

QLogic QLE2560 single-port 8GB

I setup two zvols to handle the two different drive types. I have experience with Nexenta and the ZFS file system. What I did there was to mirror the drives and create the striped zvol off of that (RAID10-ish). I thought I would just create two separate RAIDZx and add two separate LUNs to my VMWare. Well, when I go to add the LUNs, only the first LUN I create shows up. How do I get two different LUNs to show up via FibreChannel?

 

[mav@]

All LUNs configured are always visible on FC. There is no any LUN mapping/masking for FC in FreeNAS.

 

[Don Intellys]

Then what on earth am I doing wrong, here?

 

[mav@]

Try to type `ctladm devlist` and check /etc/ctl.conf for whether you do have two LUNs.

 

[Don Intellys]

I can't even copy/paste correctly:

Code:

root@GV1-MGMT-SAN01:~ # ctladm devlist
LUN Backend	   Size (Blocks)   BS Serial Number	Device ID
  1 block		   19327352832  512 002590c3214c01   iSCSI Disk	  002590c3214c01
  2 block		   21474836480  512 002590c3214c02   iSCSI Disk	  002590c3214c02

 

[Don Intellys]

Nevermind. I deleted the LUN and recreated it and it shows up as expected. Just a temporary glitch.