FreeNas - Replication - Cannot Attach Replicated snapshot Volume to ISCSI Target

[krish290785@yahoo.com]

Hi All

I have been trying the FreeNas Replication and stuck with a small problem here. I was successful in doing a A-Sync Replication for the volumes from One FreeNas Appliance to the another FreeNas Appliance. Everything seems to be working fine till then. so, I thought of testing one of the Replicated Volume by binding to an ISCSI target and mount Via ISCSI protocol from the Second FreeNas Appliance (The second appliance which has the volumes replicated from primary). I was pretty stuck at that point and unable to get any progress from there. When i try to bind it to a ISCSI target and start the ISCSI service, i was getting the below errors at the shell under /var/log/messages.

Feb 13 10:17:53 freenas notifier: istgt_lu.c:1674:istgt_lu_add_unit: ***ERROR*** LU1: LUN0: Auto size error (/dev/zvol/Raid1/raki@auto-20130213.1015-1h)
Feb 13 10:17:53 freenas istgt[3203]: istgt_lu.c:1674:istgt_lu_add_unit: ***ERROR*** LU1: LUN0: Auto size error (/dev/zvol/Raid1/raki@auto-20130213.1015-1h)
Feb 13 10:17:53 freenas notifier: istgt_lu.c:1996:istgt_lu_init: ***ERROR*** lu_add_unit() failed Feb 13 10:17:53 freenas istgt[3203]: istgt_lu.c:1996:istgt_lu_init: ***ERROR*** lu_add_unit() failed

I have been struggling since last two days to get a resolution for this issue.

Any quick help would be appreciated.

Thanks in advance
Bala

 

[krish290785@yahoo.com]

Any Help Guys.?

 

[TravisT]

Bala,

Just came across your thread. I'm having a similar problem. See my thread here.

Have you made any progress? When I change my iSCSI device extent to point to my replicated volume, I get the auto size error you reference above. I don't know iSCSI well enough to know how to fix this.

 

[James]

Are you using the snapshot or a clone? A replicated snapshot is read only. You can either set the iscsi target to read only or clone the snapshot (clones are writeable copies of a snapshot) and set that to the extent.

 

[TravisT]

That's good info. Did not realize that. Does that apply when using the ZFS send | zfs receive commands?

If I understand correctly, by doing a zfs send/receive it should rebuild the original file system using the original snapshot on the receiving end. If he's just replicating the snapshots, I could see how that would be read only.

 

[TravisT]

Not meaning to hijack this thread, but I'm having the same issue as the OP. I replicated a snapshot to a temporary datastore. That went well. I removed the original iSCSI target and device extend. I added the new iSCSI device extent (pointing to the replicated zvol) and added a new associated target. When I do that, I receive the same error:

Code:

Mar 25 10:46:44 sannas01 istgt[99357]: reload configuration #7
Mar 25 10:46:44 sannas01 istgt[99357]: istgt_lu.c:1742:istgt_lu_add_unit: ***ERROR*** LU9: LUN0: Auto size error (/dev/zvol/Temp/media.disk1-backup)
Mar 25 10:46:44 sannas01 istgt[99357]: istgt_lu.c:2332:istgt_lu_reload_update: ***ERROR*** lu_add_unit() failed

Below is some other info that may or may not help in id'ing the problem:

Code:

~# zfs list
NAME                      USED  AVAIL  REFER  MOUNTPOINT
Temp                      163G  1.63T   129G  /mnt/Temp
Temp/media.disk1-backup  33.8G  1.63T  33.8G  -
moose                    2.60T   988G   943M  /mnt/moose
moose/Databases          18.7G   988G  18.7G  /mnt/moose/Databases
moose/Files              31.3G   988G  31.3G  /mnt/moose/Files
moose/Media              2.04T   988G  2.04T  /mnt/moose/Media
moose/Reference          35.9G   988G  35.9G  /mnt/moose/Reference
moose/Software            350G   988G   350G  /mnt/moose/Software
moose/Sort                132G   988G   132G  /mnt/moose/Sort
moose/ftproot             319M   988G   319M  /mnt/moose/ftproot
moose/jail                570M   988G   570M  /mnt/moose/jail
moose/plugins             350M   988G   350M  /mnt/moose/plugins
raptor                   1.03T  2.54T  40.0G  /mnt/raptor
raptor/dc01.disk1         142G  2.64T  39.0G  -
raptor/dc02.disk1         196G  2.64T  93.2G  -
raptor/dc02.disk2         197G  2.63T  99.4G  -
raptor/esxi01.disk1      35.3G  2.57T  2.32G  -
raptor/exbe01.disk1       131G  2.64T  28.6G  -
raptor/fw01.disk1        34.6G  2.57T  1.61G  -
raptor/media01.disk1      146G  2.64T  33.8G  -
raptor/wsfe01.disk1       131G  2.64T  27.5G  -

Code:

~# zfs list -t volume
NAME                      USED  AVAIL  REFER  MOUNTPOINT
Temp/media.disk1-backup  33.8G  1.63T  33.8G  -
raptor/dc01.disk1         142G  2.64T  39.0G  -
raptor/dc02.disk1         196G  2.64T  93.2G  -
raptor/dc02.disk2         197G  2.63T  99.4G  -
raptor/esxi01.disk1      35.3G  2.57T  2.32G  -
raptor/exbe01.disk1       131G  2.64T  28.6G  -
raptor/fw01.disk1        34.6G  2.57T  1.61G  -
raptor/media01.disk1      146G  2.64T  33.8G  -
raptor/wsfe01.disk1       131G  2.64T  27.5G  -

Code:

~# zfs list -t snapshot
NAME                                          USED  AVAIL  REFER  MOUNTPOINT
Temp/media.disk1-backup@03252013-1000            0      -  33.8G  -
raptor@entire_raptor-20130316                   1K      -  40.0G  -
raptor/dc01.disk1@entire_raptor-20130316      456M      -  39.0G  -
raptor/dc02.disk1@entire_raptor-20130316     1.44G      -  93.2G  -
raptor/dc02.disk2@manual-20130315             154M      -  93.2G  -
raptor/dc02.disk2@entire_raptor-20130316      131M      -  93.7G  -
raptor/esxi01.disk1@entire_raptor-20130316   3.23M      -  2.32G  -
raptor/exbe01.disk1@entire_raptor-20130316    462M      -  28.1G  -
raptor/fw01.disk1@entire_raptor-20130316     6.50M      -  1.61G  -
raptor/media01.disk1@entire_raptor-20130316  5.62G      -  33.8G  -
raptor/media01.disk1@20130320-2222           2.39M      -  33.8G  -
raptor/media01.disk1@1                        119K      -  33.8G  -
raptor/media01.disk1@2                       1.13M      -  33.8G  -
raptor/media01.disk1@03252013-1000               0      -  33.8G  -
raptor/wsfe01.disk1@entire_raptor-20130316    320M      -  27.5G  -

raptor/media01.disk1@03252013-1000 is the snapshot that was replicated over to the Temp/media.disk1-backup zvol. The Temp/media.disk1-backup is what I'm pointing the iSCSI target to.