Replies: 2 comments
-
|
I have been able to replicate it now, with the following script: Running this script, the last few lines of output are: The size of Is this expected behaviour, and is there a way to prevent it? The problem this causes with replication can then be shown with a second script: Result: |
Beta Was this translation helpful? Give feedback.
-
|
Oops: in the reproducer script I forgot to set But I had already set So I'm still at a loss how to reproduce this in a standalone dataset. |
Beta Was this translation helpful? Give feedback.
-
This is a weird one. It's fully reproducible with a set of existing datasets I have, but I'm having difficulty replicating it on a fresh zpool and dataset.
This is under Ubuntu 18.04.5 (4.15.0-128-generic), with stock ZoL 0.7.5.
I have some datasets which have been populated by 'zfs receive' (using zrepl). The filesystem state should be equal to the last snapshot, so that it can receive additional incremental updates
The problem is that the filesystem gets out of step from the snapshot. Here it is in the out-of-step state:
To fix this, I roll it back to the snapshot:
The '0B' indicates that the snapshot is equal to the current filesystem state. All good.
However if I unmount it and remount it, it diverges again from the snapshot - and I can see this take place over a period of a few seconds.
However,
zfs diffsays there's no difference (it takes a couple of minutes to report this)In this state, the dataset doesn't work as a target for "zfs recv". The error reported is as per zrepl/zrepl#405
Presumably "zfs recv -F" would work, but (a) zrepl doesn't provide this, and (b) I don't want to lose all other snapshots on the target.
The upshot in short is: if the target machine reboots for any reason, the filesystems are remounted at boot time using
zfs mount -a, and all the "zfs receive" targets stop working until I manually rollback all the datasets to their most recent snapshot.Other information
The dataset is mounted with readonly=on and atime=off:
There is no outstanding partial receive:
The pool is up-to-date with all available features:
The underlying zpool is a mirrored pair of partitions on 4TB spinning hard drives:
Any ideas as to what's going on here??
Beta Was this translation helpful? Give feedback.
All reactions