REPLICATION / Please move system dataset of remote side to another pool

[BlazeStar]

Using FreeNAS-9.3-STABLE-201511280648

I just got this error message today :

Code:

Please move system dataset of remote side to another pool

What the hell does that mean ?

I've been replicating for over a year now and this just popped up :S

 

[dlavigne]

Yup, new in latest SU. See #12143 in http://download.freenas.org/9.3.1/STABLE/201511280648/ChangeLog for details.

 

[depasseg]

I got hit with this as well. It means that on your replication destination system, the .system dataset is on the same pool as the replication target AND your are replicating into the root of that pool. There are 2 options:

1. use the GUI to move the system dataset to a different pool.
2. create a sub-dataset and replicate into that.

I also found that even after I moved my system dataset, there were still remnants left behind which continued to provide errors. I just completely wiped the pool and started over (using a sub-dataset).

 

[depasseg]

I wish errors had error codes that could be looked up in a KB article or forum post.

 

[BlazeStar]

I got hit with this as well. It means that on your replication destination system, the .system dataset is on the same pool as the replication target AND your are replicating into the root of that pool. There are 2 options:

1. use the GUI to move the system dataset to a different pool.
2. create a sub-dataset and replicate into that.

I also found that even after I moved my system dataset, there were still remnants left behind which continued to provide errors. I just completely wiped the pool and started over (using a sub-dataset).

Sorry for delay and thanks for the response.

So I checked and the .system dataset is NOT on the same pool as the replication target.

The replication target is a different volume, a different HD, and it does not have a .system dataset.

In the GUI it does report the .system dataset to be on a different volume too.

I just don't get it.

And I would like to avoid at all cost to destroy my replication target volume because it would take about 2 months, given the internet transfer speed, to reach the first successful replication :(

 

[depasseg]

Can you please provide the results of "zfs list" from teh destination system in code tags?

 

[BlazeStar]

Can you please provide the results of "zfs list" from teh destination system in code tags?

Sorry for very long delay, I was on extended vacations (much needed).

I still have the same problem and as requested here's the result of ZFS LIST

Code:

NAME                                                               USED  AVAIL  REFER  MOUNTPOINT
BUSINESS                                                          1.17T  2.34T   136K  /mnt/BUSINESS
BUSINESS/.system                                                  1.60G  2.34T   170M  /mnt/BUSINESS/.system
BUSINESS/.system/configs-d693e87545574e0bb5bd7bed67e6e6ce          512K  2.34T    96K  /mnt/BUSINESS/.system/configs-d693e87545574e0bb5bd7bed67e6e6ce
BUSINESS/.system/cores                                            12.8M  2.34T  8.06M  /mnt/BUSINESS/.system/cores
BUSINESS/.system/rrd-d693e87545574e0bb5bd7bed67e6e6ce              960K  2.34T    96K  /mnt/BUSINESS/.system/rrd-d693e87545574e0bb5bd7bed67e6e6ce
BUSINESS/.system/samba4                                            236M  2.34T  3.85M  /mnt/BUSINESS/.system/samba4
BUSINESS/.system/syslog-d693e87545574e0bb5bd7bed67e6e6ce           183M  2.34T  39.7M  /mnt/BUSINESS/.system/syslog-d693e87545574e0bb5bd7bed67e6e6ce
BUSINESS/Backup                                                    496K  2.34T    96K  /mnt/BUSINESS/Backup
BUSINESS/Backup/pfSense                                            248K  2.34T    96K  /mnt/BUSINESS/Backup/pfSense
BUSINESS/Shares                                                    512G  2.34T   104K  /mnt/BUSINESS/Shares
BUSINESS/Shares/Compta                                            4.08G  2.34T  2.01G  /mnt/BUSINESS/Shares/Compta
BUSINESS/Shares/Direction                                         3.11G  2.34T  2.76G  /mnt/BUSINESS/Shares/Direction
BUSINESS/Shares/Divers                                            82.9M  2.34T  70.2M  /mnt/BUSINESS/Shares/Divers
BUSINESS/Shares/Employes                                          26.7G  2.34T  23.2G  /mnt/BUSINESS/Shares/Employes
BUSINESS/Shares/FTP                                               5.05M  2.34T   148K  /mnt/BUSINESS/Shares/FTP
BUSINESS/Shares/Partage                                           4.67G  2.34T   132K  /mnt/BUSINESS/Shares/Partage
BUSINESS/Shares/RPM                                                274M  2.34T   257M  /mnt/BUSINESS/Shares/RPM
BUSINESS/Shares/SRH                                               15.4G  2.34T  14.4G  /mnt/BUSINESS/Shares/SRH
BUSINESS/Shares/TT                                                 444G  2.34T   416G  /mnt/BUSINESS/Shares/TT
BUSINESS/Shares/CPA                                               12.0G  2.34T  6.90G  /mnt/BUSINESS/Shares/CPA
BUSINESS/Shares/CPA-Partage                                       1.05G  2.34T  4.77M  /mnt/BUSINESS/Shares/CPA-Partage
BUSINESS/Virtualization                                            687G  2.34T    96K  /mnt/BUSINESS/Virtualization
BUSINESS/Virtualization/ISO                                       7.01G  2.34T  7.01G  /mnt/BUSINESS/Virtualization/ISO
BUSINESS/Virtualization/Machines                                   680G  2.34T   180G  /mnt/BUSINESS/Virtualization/Machines
Hm                                                                5.60T  4.93T   264K  /mnt/Hm
Hm/.system                                                         131M  4.93T   120M  legacy
Hm/.system/configs-f6da24756e2f4dee86c3a9c9fb75829f               7.69M  4.93T  7.69M  legacy
Hm/.system/cores                                                  1.08M  4.93T  1.08M  legacy
Hm/.system/rrd-f6da24756e2f4dee86c3a9c9fb75829f                    144K  4.93T   144K  legacy
Hm/.system/samba4                                                  416K  4.93T   416K  legacy
Hm/.system/syslog-f6da24756e2f4dee86c3a9c9fb75829f                1.19M  4.93T  1.19M  legacy
Hm/Divers                                                         67.8G  4.93T  67.8G  /mnt/Hm/Divers
Hm/Documents                                                      2.67M  4.93T   132K  /mnt/Hm/Documents
Hm/Documents/owncloud                                             2.54M  4.93T  2.54M  /mnt/Hm/Documents/owncloud
Hm/Maisons                                                         256K  4.93T   256K  /mnt/Hm/Maisons
Hm/Medias                                                         3.57T  4.93T   132K  /mnt/Hm/Medias
Hm/Medias/Films                                                   2.45T  4.93T  2.45T  /mnt/Hm/Medias/Films
Hm/Medias/Series                                                  1.12T  4.93T  1.12T  /mnt/Hm/Medias/Series
Hm/Prisons                                                        18.5G  4.93T   428K  /mnt/Hm/Prisons
Hm/Prisons/.warden-template-pluginjail--x64                        449M  4.93T   449M  /mnt/Hm/Prisons/.warden-template-pluginjail--x64
Hm/Prisons/.warden-template-pluginjail-9.2-x64                     721M  4.93T   721M  /mnt/Hm/Prisons/.warden-template-pluginjail-9.2-x64
Hm/Prisons/.warden-template-portjail-9.2-x64                      1.58G  4.93T  1.58G  /mnt/Hm/Prisons/.warden-template-portjail-9.2-x64
Hm/Prisons/couchpotato_1                                           369M  4.93T  1.06G  /mnt/Hm/Prisons/couchpotato_1
Hm/Prisons/owncloud_1                                              446M  4.93T  1.14G  /mnt/Hm/Prisons/owncloud_1
Hm/Prisons/plexmediaserver_1                                      14.2G  4.93T  14.9G  /mnt/Hm/Prisons/plexmediaserver_1
Hm/Prisons/sickrage_1                                              689M  4.93T  1.35G  /mnt/Hm/Prisons/sickrage_1
Hm/Prisons/transmission_1                                          130M  4.93T   579M  /mnt/Hm/Prisons/transmission_1
Hm/TimeMachine                                                    1.24T  4.93T   112K  /mnt/Hm/TimeMachine
Hm/TimeMachine/MacBookPro                                          568G   456G   568G  /mnt/Hm/TimeMachine/MacBookPro
Hm/TimeMachine/Mini                                                698G   326G   698G  /mnt/Hm/TimeMachine/Mini
Hm/Torrents                                                        729G  4.93T   140K  /mnt/Hm/Torrents
Hm/Torrents/Fichiers                                               136K  4.93T   136K  /mnt/Hm/Torrents/Fichiers
Hm/Torrents/Telechargements                                        729G  4.93T   729G  /mnt/Hm/Torrents/Telechargements
freenas-boot                                                      1.69G  5.52G    31K  none
freenas-boot/ROOT                                                 1.63G  5.52G    25K  none
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201505040117                 3.46M  5.52G   496M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201505130355                 4.01M  5.52G   511M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201506162331                 8.47M  5.52G   513M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201506232120                   36K  5.52G   516M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201506292332                 10.2M  5.52G   519M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201509022158                 8.86M  5.52G   520M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201509282017                 1.59G  5.52G   524M  /
freenas-boot/ROOT/default                                         3.85M  5.52G   471M  legacy
freenas-boot/grub                                                 54.2M  5.52G  6.79M  legacy

My replication target is the BUSINESS volume.

 

[depasseg]

Your replication target, BUSINESS, has a. system dataset. That is the issue.

 

[BlazeStar]

okay so I just delete those files? no risk?

 

[depasseg]

I think you need to do some investigation, because you told me a couple posts ago that your replication target didn't have a .system dataset, but it does. The simplest fix is to create a new dataset on your destination and replicate into that.

 

[depasseg]

And to answer your question, no, you can't just delete it. There is risk.

 

[Fuganater]

I just figured this issue out a few days ago. Are you trying to backup TO the Business dataset or Business is the dataset you want to replicate to another? Is the backup located on the same machine or a different one?

Business\Backup should be your replication target but we need to know what dataset you are trying to replicate.

 

[BlazeStar]

And to answer your question, no, you can't just delete it. There is risk.

From the GUI, the system dataset is not on this volume.

It is on the Hm volume (pool).

Does that give me green light to delete the .system files or no?

Because I don't want to start over a new replication... with the amount of data, and the internet connection speed, it'll take over a month!

I just figured this issue out a few days ago. Are you trying to backup TO the Business dataset or Business is the dataset you want to replicate to another? Is the backup located on the same machine or a different one?

Business\Backup should be your replication target but we need to know what dataset you are trying to replicate.

I'm trying to replicate TO the Business volume.

The two FreeNAS systems are two different boxes, in different locations.
Replication is over the Internet.

I know which dataset I'm trying to replicate... it's the business volume on the FreeNAS at work!

I've been replicating for years and now this pesky warning prevents me from continuing to do so :(

 

[depasseg]

If you are sure that the system dataset is somewhere else then you can delete it. OTOH, are you sure it isn't part of the Push dataset? The data came from somewhere.

This happened to me and I triple checked before deleting it.

 

[BlazeStar]

If you are sure that the system dataset is somewhere else then you can delete it. OTOH, are you sure it isn't part of the Push dataset? The data came from somewhere.

This happened to me and I triple checked before deleting it.

Well yeah for sure it could most definitely come from the replicated data!

But what then?

Every time I replicate it's going to create again a replicated system dataset, and then whine about the fact that there's a system dataset on target?
Is there a workaround this?

 

[depasseg]

Well yeah for sure it could most definitely come from the replicated data!

But what then?

Every time I replicate it's going to create again a replicated system dataset, and then whine about the fact that there's a system dataset on target?
Is there a workaround this?

Yes there is a workaround. I gave it to you in my first post. Create a dataset on pull and replicate into that instead of the root. That's what I did.

 

[hansch]

This bug came back... Freenas 11.2 U1.
- The system dataset is NOT on the replication target
- The replication target is a sub dataset (a pool within a pool), not a root volume
- The error still pops up
- Another thing: I accidentally choose a dedicated user WITHOUT checking "use dedicated user" --- and it still uses that one.

That means I have to file 2 (more) bugs.

 

[pro lamer]

That means I have to file 2 (more) bugs

Will you post their numbers so we can follow up?

Sent from my phone

 

[hansch]

I switched the two systems and replicated the other way round, now it works.