Snapshot replication on push "is running" but no snapshots on pull system present

Status
Not open for further replies.

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
Compare the size of that iSCSI-Target1 to the size of the zvoll in the GUI. They are not the same thing.
ok!?
you mean the push or pull system?

sorry, but i really dont know where the problem is.

e.g. the push system (my system1) is broken and i need the replicated snapshots from the pull system (my system2) to get my iscsi target back online!
how can i manage this when its not possible to mount a snapshot-clone On the pull system ?
 
Last edited:

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
how can i manage this when its not possible to mount a snapshot-clone On the pull system ?
Let's clear up a couple things.

Snapshots let you go back in time. If you don't need to go back in time, then you don't need to clone a snapshot.

If you want to share the iscsi zvol on system2, then go through the steps to share the zvol via iscsi. Mounting it isn't the answer, nor the problem, so stop worrying about that. I've told you this before many times. I'm not sure how to state it any clearer.

you mean the push or pull system?
on Push (since you said you can't ls iscsi-target1 on pull).
sorry, but i really dont know where the problem is.
It sounds like the problem is you have an iscsi zvol on system2 that you want to share and incorrectly think that in order to do that, you must 1. make a clone and 2. mount it. You don't.
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
It sounds like the problem is you have an iscsi zvol on system2 that you want to share and incorrectly think that in order to do that, you must 1. make a clone and 2. mount it. You don't.


it's not an iscsi zvol, it's an iscsi file extent on system1 that should be replicated to system2.
i dont know if this makes any difference to this problem
 
Last edited:

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
So ISCSI-Target1 is a dataset with a file called ISCSI-Storage1?

Which dataset are you snapshotting? Are you sure you are recursively snapshotting?

And are you sure you're recursively replicating?
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
So ISCSI-Target1 is a dataset with a file called ISCSI-Storage1?

Which dataset are you snapshotting? Are you sure you are recursively snapshotting?

no, not recursive snapshotting

snapshot-settings.JPG


And are you sure you're recursively replicating?

yes, replicating is recursive.
replicate-settings.JPG

does this means the file is not included in the dataset although its on the same level?
 
Last edited:

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
Can you please provide the output of zfs mount (in code tags) from both push and pull? dataset1/dataset1/iscsi-target1 has over 8TB of data on Pull. It's there, you just can't see it, and we are trying to figure out why you can't see it.
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
Can you please provide the output of zfs mount (in code tags) from both push and pull? dataset1/dataset1/iscsi-target1 has over 8TB of data on Pull. It's there, you just can't see it, and we are trying to figure out why you can't see it.

ok,
Push:
Code:
[root@freenas-99 ~]# zfs mount																									 
freenas-boot/ROOT/9.10.1-U2	 /																								   
freenas-boot/grub			   /boot/grub																						 
vol1							/mnt/vol1																						   
vol1/dataset1				   /mnt/vol1/dataset1																				 
vol1/dataset1/ISCSI-Target1	 /mnt/vol1/dataset1/ISCSI-Target1																	
vol1/dataset1/jails			 /mnt/vol1/dataset1/jails																			
vol1/jails					  /mnt/vol1/jails																					 
vol1/.system					/var/db/system																					 
vol1/.system/cores			  /var/db/system/cores																				
vol1/.system/samba4			 /var/db/system/samba4																			   
vol1/.system/syslog-241bf4dd02d1413596a7e0d91081dbbf  /var/db/system/syslog-241bf4dd02d1413596a7e0d91081dbbf						
vol1/.system/rrd-241bf4dd02d1413596a7e0d91081dbbf  /var/db/system/rrd-241bf4dd02d1413596a7e0d91081dbbf							 
vol1/.system/configs-241bf4dd02d1413596a7e0d91081dbbf  /var/db/system/configs-241bf4dd02d1413596a7e0d91081dbbf					 
[root@freenas-99 ~]#																							 


Pull:
Code:
[root@freenas-101 /mnt/vol1/dataset1/dataset1]# zfs mount																		   
freenas-boot/ROOT/9.10.1-U2	 /																								   
freenas-boot/grub			   /boot/grub																						 
vol1							/mnt/vol1																						   
vol1/dataset1				   /mnt/vol1/dataset1																				 
vol1/dataset1/dataset1		  /mnt/vol1/dataset1/dataset1																		 
vol1/jails					  /mnt/vol1/jails																					 
[root@freenas-101 /mnt/vol1/dataset1/dataset1]#		 
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
And the output of zfs list for both please?
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
And the output of zfs list for both please?
here we go...

Push:

Code:
[root@freenas-99 ~]# zfs list																									   
NAME													USED  AVAIL  REFER  MOUNTPOINT											 
freenas-boot										   1.72G   106G	31K  none													
freenas-boot/ROOT									  1.69G   106G	25K  none													
freenas-boot/ROOT/9.10-STABLE-201604140622			 8.54M   106G   503M  /													   
freenas-boot/ROOT/9.10-STABLE-201604181743			 5.14M   106G   462M  /													   
freenas-boot/ROOT/9.10.1-U2							1.67G   106G   665M  /													   
freenas-boot/ROOT/Initial-Install						 1K   106G   493M  legacy												 
freenas-boot/ROOT/default							  6.73M   106G   500M  legacy												 
freenas-boot/grub									  25.3M   106G  6.33M  legacy												 
vol1												   7.81T  9.03T   153K  /mnt/vol1											   
vol1/.system										   34.1M  9.03T   166K  legacy												 
vol1/.system/configs-241bf4dd02d1413596a7e0d91081dbbf  19.9M  9.03T  19.9M  legacy												 
vol1/.system/cores									 11.5M  9.03T  11.5M  legacy												 
vol1/.system/rrd-241bf4dd02d1413596a7e0d91081dbbf	   153K  9.03T   153K  legacy												 
vol1/.system/samba4									 320K  9.03T   320K  legacy												 
vol1/.system/syslog-241bf4dd02d1413596a7e0d91081dbbf   2.08M  9.03T  2.08M  legacy												 
vol1/dataset1										  7.79T  9.03T   103M  /mnt/vol1/dataset1									 
vol1/dataset1/ISCSI-Target1							7.79T  9.03T  4.58T  /mnt/vol1/dataset1/ISCSI-Target1						
vol1/dataset1/jails									14.6M  9.03T   153K  /mnt/vol1/dataset1/jails								
vol1/jails											  153K  9.03T   153K  /mnt/vol1/jails										 
[root@freenas-99 ~]#																			


Pull:
Code:
[root@freenas-101 /mnt/vol1/dataset1/dataset1]# zfs list																			
NAME															   USED  AVAIL  REFER  MOUNTPOINT								   
freenas-boot													  1.51G   106G	31K  none										 
freenas-boot/ROOT												 1.48G   106G	25K  none										 
freenas-boot/ROOT/9.10-STABLE-201606270534						11.6M   106G   606M  /											
freenas-boot/ROOT/9.10.1-U2									   1.46G   106G   634M  /											
freenas-boot/ROOT/Initial-Install									1K   106G   463M  legacy									   
freenas-boot/ROOT/default										 10.2M   106G   473M  legacy									   
freenas-boot/grub												 19.0M   106G  6.33M  legacy									   
vol1															  8.63T  5.36T   279K  /mnt/vol1									
vol1/.system													  3.97M  5.36T   302K  legacy									   
vol1/.system/configs-9ea32b00462f407e85fe38994184205a			  407K  5.36T   407K  legacy									   
vol1/.system/cores												1.63M  5.36T  1.63M  legacy									   
vol1/.system/rrd-9ea32b00462f407e85fe38994184205a				  279K  5.36T   279K  legacy									   
vol1/.system/samba4												442K  5.36T   442K  legacy									   
vol1/.system/syslog-9ea32b00462f407e85fe38994184205a			   965K  5.36T   965K  legacy									   
vol1/dataset1													 8.61T  5.36T   279K  /mnt/vol1/dataset1						   
vol1/dataset1/dataset1											8.61T  5.36T   279K  /mnt/vol1/dataset1/dataset1				 
vol1/dataset1/dataset1/ISCSI-Target1							  8.61T  5.36T  4.85T  /mnt/vol1/dataset1/dataset1/ISCSI-Target1	
vol1/dataset1/dataset1/ISCSI-Target1-auto-20161027.0703-2m-clone  23.2K  5.36T  4.85T  /mnt/vol1/dataset1/dataset1/ISCSI-Target1-aut
o-20161027.0703-2m-clone																											
vol1/jails														 279K  5.36T   279K  /mnt/vol1/jails							 
[root@freenas-101 /mnt/vol1/dataset1/dataset1]#																			   
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
And on Pull what does the following command return:
zfs mount vol1/dataset1/dataset1/ISCSI-Target1
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
zfs mount vol1/dataset1/dataset1/ISCSI-Target1
Code:
[root@freenas-101 /mnt/vol1/dataset1/dataset1]# zfs mount vol1/dataset1/dataset1/ISCSI-Target1									 
cannot mount '/mnt/vol1/dataset1/dataset1/ISCSI-Target1': failed to create mountpoint											   
[root@freenas-101 /mnt/vol1/dataset1/dataset1]#												 
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
It looks like your Pull dataset1 is read only. Did you set that, or was it done automatically by FreeNAS? You can try changing the settings to read-write (both dataset1 and dataset1/iscsi-target1) and then rerun the mount command.
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
It looks like your Pull dataset1 is read only. Did you set that, or was it done automatically by FreeNAS? You can try changing the settings to read-write (both dataset1 and dataset1/iscsi-target1) and then rerun the mount command.
You are right! it's set to read only but wasn't set by me.
where can i set it back to read/write? looked under "edit" at the dataset settings but couldnt find an option.
ReadOnlyPull.JPG
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
Code:
zfs set readonly=off vol1/dataset1/dataset1
and possibly
Code:
zfs set readonly=off vol1/dataset1/dataset1/ISCSI-Target1
then re-run the mount command.
 

bramble

Dabbler
Joined
Oct 26, 2016
Messages
17
Code:
zfs set readonly=off vol1/dataset1/dataset1
and possibly
Code:
zfs set readonly=off vol1/dataset1/dataset1/ISCSI-Target1
then re-run the mount command.
That did the trick!
Thank You!

I will have an eye on the dataset, under which circumstances it possible goes back to read only....
 
Status
Not open for further replies.
Top