Home / user-313361

niels's questions

Martin Hope
niels
Asked: 2015-09-28 21:35:38 +0800 CST
  • 3

How do I make freebsd show initiators a mountable target from a zpool?

On a fresh install of FreeBSD 10.2 (hostname bohr) I made a zpool named tank with a single vdev which is 2 disks in a mirror; then I used zfs to make a 4GB volume (images). I set up an iSCSI LUN with no-authentication for the group and target (for testing) pointing at images. Linux, FreeBSD, and OS X initiators can discover the target and connect but none of them finds a volume that I can format or mount.

root@bohr:/tank/volumes # zfs list
NAME                  USED  AVAIL  REFER  MOUNTPOINT
tank                 4.13G   895G    96K  /tank
tank/volumes         4.13G   895G   100K  /tank/volumes
tank/volumes/images  4.13G   899G    64K  -
root@bohr:/tank/volumes # zpool status
  pool: tank
  state: ONLINE
  scan: none requested
config:

    NAME        STATE     READ WRITE CKSUM
    tank        ONLINE       0     0     0
      mirror-0  ONLINE       0     0     0
        ada1    ONLINE       0     0     0
        ada2    ONLINE       0     0     0

errors: No known data errors

root@bohr:~ # cat /etc/ctl.conf
auth-group ag0 {
    chap house shortshortdress
}

portal-group pg0 {
    discovery-auth-group no-authentication
    listen 0.0.0.0
    listen [::]
} 

target iqn.2015-09.com.example:images {
    auth-group no-authentication
    portal-group pg0

    lun 0 {
        path /tank/volumes/images
        size 4G
    }
}

so, here's a representative linux initiator, note the absence of /dev/sdd in the output of fdisk -l:

niels@suse_linux:~> lsscsi
[0:0:0:0]    disk    ATA      WDC WD1600AAJB-5 01.0  /dev/sda
[1:0:0:0]    cd/dvd  HL-DT-ST DVD-ROM GDR8162B 0015  /dev/sr0
[1:0:1:0]    cd/dvd  _NEC     DVD+RW ND-1100A  10FD  /dev/sr1
[2:0:0:0]    disk    ATA      TOSHIBA DT01ACA2 MX4O  /dev/sdb
[3:0:0:0]    disk    ATA      TOSHIBA DT01ACA2 MX4O  /dev/sdc
[21:0:0:0]   disk    FREEBSD  CTLDISK          0001  /dev/sdd

niels@suse_linux:~> sudo /usr/sbin/fdisk -l
root's password:

Disk /dev/sda: 160.0 GB, 159974776832 bytes, 312450736 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000c3390

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048     4208639     2103296   82  Linux swap / Solaris
/dev/sda2   *     4208640    46153727    20972544   83  Linux
/dev/sda3        46153728   312449023   133147648   83  Linux

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 2000.3 GB, 2000264691712 bytes, 3906766976 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Results on OS X are similar, connection but nothing available to diskutil. I tried using the freebsd box as an initiator also, and it will make the connection, but still no device I can access. Back to bohr for another example of a connection made, but 

root@bohr:~ # iscsictl -L
Target name                          Target portal    State
iqn.2015-09.com.example:images 192.168.1.148    Connected: da0

I followed the FreeBSD manual for zfs and iscsi.

freebsd
Martin Hope
niels
Asked: 2015-09-26 13:24:40 +0800 CST
  • 3

My collaborator is splitting from his institute and wants help moving his application and data off the institute's network. And of course things are moving quickly.

He has 12 TB of image data on a 400 TB SAN, which is addressed over iSCSI.

The application server currently runs in a separate 1U Dell pizza box, runs on Windows Server 2003 for now (plan is to upgrade to 2012 when the app company certifies their product build) and the app officially only supports iSCSI; although a long-time tech rep at the company says he's seen it work with NFS. He says he only needs to run an SQL script to update the paths.

Here's my proposed workflow:

  • Setup a zpool (tank) on FreeBSD 10.2 on a Dell Precision T7400 with 5 6TB disks in either a RAIDZ1 or 4 disks in two mirror vdevs. Let's call this machine bohr
  • Set up an iSCSI targets with LUNs that point to volumes (images and images2)
  • Plug bohr into the institute's network (they're fine with that)
  • Mount the institute's SAN, as an initiator or via SMB
  • copy the data to the LUNs
  • point the application server at the new LUNs
  • Charles (the app company's rep) runs his SQL
  • Take bohr and the app server and set them up at the new site.

The only alternative I thought of was to make the app server do the transfer. It seems like it might actually slow things down, but would also avoid me having to set up bohr as an initiator.

My questions: am I making sense? Does the plan sound like it would work? Am I missing any steps? Does it make sense to also set up bohr to serve the same data over NFS simultaneously (for pulling data for other research uses) or should I require iscsi access for all clients?

nfs