Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeyError [zreplicate thing] #20

Open
muzyk10 opened this issue Oct 21, 2016 · 3 comments
Open

KeyError [zreplicate thing] #20

muzyk10 opened this issue Oct 21, 2016 · 3 comments

Comments

@muzyk10
Copy link

muzyk10 commented Oct 21, 2016

Im wondering why is that below.
On localhost ./zreplicate works as expected:

lap bin # ./zreplicate -vo --create-destination --no-replication-stream data/test data/backup
Replicating dataset localhost:data/test into localhost:data/backup...
Assessing that the source dataset exists...

Assessing that the destination dataset exists...

Replicating (full) data/test to data/backup
Base snapshot available in destination: None
Target snapshot available in source: <Snapshot: data/test@autosnapshot-2016-10-21-014702>
send from @ to data/test@autosnapshot-2016-10-21-014702 estimated size is 9,50K
total estimated size is 9,50K
TIME SENT SNAPSHOT
40,7KiB 0:00:00 [1,29GiB/s] [ <=>
receiving full stream of data/test@autosnapshot-2016-10-21-014702 into data/backup@autosnapshot-2016-10-21-014702

received 40,4KB stream in 1 seconds (40,4KB/sec)

Replication complete.

but doing it to remote direction (all the user zfs/zfs-shell/sudo stuff is OK) outputs:

lap bin # ./zreplicate -o -v --create-destination --no-replication-stream localhost:data/test zfs@edge1:rpool/DATA/backup/test
Replicating dataset localhost:data/test into zfs@edge1:rpool/DATA/backup/test...
Assessing that the source dataset exists...
Assessing that the destination dataset exists...
Creating missing destination dataset exists as requested
Traceback (most recent call last):
File "./zreplicate", line 78, in
dst_conn.create_dataset(destination_dataset_name)
File "/home/llu/praca/zfs/zfs-tools/bin/../src/zfstools/connection.py", line 66, in create_dataset
return self.pools.lookup(name)
File "/home/llu/praca/zfs/zfs-tools/bin/../src/zfstools/connection.py", line 58, in _get_poolset
self._poolset.parse_zfs_r_output(stdout2,properties)
File "/home/llu/praca/zfs/zfs-tools/bin/../src/zfstools/models.py", line 179, in parse_zfs_r_output
fs = self.pools[poolname]
KeyError: 'rpool'

@Rudd-O
Copy link
Owner

Rudd-O commented Oct 25, 2016

On 10/21/2016 12:14 AM, muzyk10 wrote:

Im wondering why is that below.
On localhost ./zreplicate works as expected:

lap bin # ./zreplicate -vo --create-destination
--no-replication-stream data/test data/backup
Replicating dataset localhost:data/test into localhost:data/backup...
Assessing that the source dataset exists...


    Assessing that the destination dataset exists...

Replicating (full) data/test to data/backup
Base snapshot available in destination: None
Target snapshot available in source:
send from @ to data/test@autosnapshot-2016-10-21-014702 estimated
size is 9,50K
total estimated size is 9,50K
TIME SENT SNAPSHOT
40,7KiB 0:00:00 [1,29GiB/s] [ <=>

receiving full stream of data/test@autosnapshot-2016-10-21-014702
into data/backup@autosnapshot-2016-10-21-014702


    received 40,4KB stream in 1 seconds (40,4KB/sec)

Replication complete.

but doing it to remote direction (all the user zfs/zfs-shell/sudo
stuff is OK) outputs:

lap bin # ./zreplicate -o -v --create-destination
--no-replication-stream localhost:data/test
zfs@edge1:rpool/DATA/backup/test
Replicating dataset localhost:data/test into
zfs@edge1:rpool/DATA/backup/test...
Assessing that the source dataset exists...
Assessing that the destination dataset exists...
Creating missing destination dataset exists as requested
Traceback (most recent call last):
File "./zreplicate", line 78, in
dst_conn.create_dataset(destination_dataset_name)
File
"/home/llu/praca/zfs/zfs-tools/bin/../src/zfstools/connection.py",
line 66, in create_dataset
return self.pools.lookup(name)
File
"/home/llu/praca/zfs/zfs-tools/bin/../src/zfstools/connection.py",
line 58, in _get_poolset
self._poolset.parse_zfs_r_output(stdout2,properties)
File
"/home/llu/praca/zfs/zfs-tools/bin/../src/zfstools/models.py",
line 179, in parse_zfs_r_output
fs = self.pools[poolname]
KeyError: 'rpool'


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#20, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVIwsXzMXko4fEOhLAejSg57rb94CE4ks5q2APtgaJpZM4KcvHq.

On the second case, it doesn't seem like listing the remote pool is
returning "rpool" as part of the ZFS list.

Does the remote end (the receiving side) actually have a pool called
/rpool/?

Just wondering.

Rudd-O
http://rudd-o.com/

@muzyk10
Copy link
Author

muzyk10 commented Oct 26, 2016

local host pool name is 'data' and remote host pool name is 'rpool'

@Rudd-O
Copy link
Owner

Rudd-O commented Dec 7, 2020

Can you still repro with latest master?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants