Project

General

Profile

Bug #26134

ZFS replication causes datasets to become unavailable

Added by B W almost 3 years ago. Updated almost 3 years ago.

Status:
Closed: Duplicate
Priority:
No priority
Assignee:
Sean Fagan
Category:
OS
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

I recently set up ZFS replication of my datasets to an external backup drive which already has a few previously existing backup datasets for one-off backups and other miscellaneous items. I accomplished this by pointing the destination dataset to localhost. That seems to work fine, but the existing datasets on the backup drive become available and /var/log/messages becomes flooded with the following:

Oct 8 08:32:57 freenas collectd23156: statvfs(/mnt/backup/jails/plex) failed: No such file or directory

There is one such line for each of my datasets.

If I reboot the machine, all datasets are available again -- until a replication task takes place again.

log.png (60.2 KB) log.png B W, 10/09/2017 06:35 PM
12665

Related issues

Has duplicate FreeNAS - Feature #23784: Add ability to replicate local pools to legacy UIReady for Testing
Has duplicate FreeNAS - Bug #25786: collectd and statvfs still reporting no such file or dir after rep task comes in from prod systemClosed: Duplicate2017-09-06

History

#1 Updated by B W almost 3 years ago

12665

#2 Updated by Sean Fagan almost 3 years ago

  • Status changed from Unscreened to 15
  • Assignee changed from Release Council to Sean Fagan

This is the way replication works. It's annoying, but it's due to how they're implemented, how ZFS replications work, and how unix works.

What, exactly, are you replicating?

(The main reason it doesn't tend to show up is the dataset being replicated to doesn't exist the first time, and so is created read-only, which causes mounts to be hidden.)

#3 Updated by B W almost 3 years ago

Sean Fagan wrote:

This is the way replication works. It's annoying, but it's due to how they're implemented, how ZFS replications work, and how unix works.

What, exactly, are you replicating?

(The main reason it doesn't tend to show up is the dataset being replicated to doesn't exist the first time, and so is created read-only, which causes mounts to be hidden.)

I think this is probably a dupe. See Bug #25786 for example.

#4 Updated by Sean Fagan almost 3 years ago

Yes, it is the same thing. I am just curious what you are replicating, and to where.

#5 Updated by B W almost 3 years ago

Replicating my main drive pool to an external backup drive (localhost as destination).

#6 Updated by Dru Lavigne almost 3 years ago

  • Has duplicate Feature #23784: Add ability to replicate local pools to legacy UI added

#7 Updated by Dru Lavigne almost 3 years ago

  • Status changed from 15 to Closed: Duplicate
  • Target version set to N/A

#8 Updated by Dru Lavigne over 2 years ago

  • Has duplicate Bug #25786: collectd and statvfs still reporting no such file or dir after rep task comes in from prod system added

Also available in: Atom PDF