Replication task successful when not able to be unmounted from destination
Description
Problem/Justification
Impact
Activity
Bug Clerk January 13, 2025 at 7:28 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Vladimir Vinogradenko January 13, 2025 at 7:28 PM
I have to close this as the uploaded debug contains no traces of such errors. Feel free to reopen it when the issue appears again.
Pål Andreas Lindsetmo January 13, 2025 at 7:13 PM
@Vladimir Vinogradenko I am sorry, the details of these events are no longer clear to me as I found a workaround (deleted dataset at destination, made new one which weren’t busy).
I had several of these events in the few (3-7) days prior to uploading the logs.
Hopefully you can use some information to debug, if not I am sorry for being able to help troubleshoot further.
Anyways; thanks for the great work you all are doing!
Vladimir Vinogradenko January 13, 2025 at 6:45 PM
@Pål Andreas Lindsetmo that would be terrible. However, the logs start on 2024/07/31 and I only see one unmount
error that occurred on 2024/12/18 20:09:52. Do you remember when this happened and which datasets were involved?
Pål Andreas Lindsetmo January 13, 2025 at 6:41 PM
@Vladimir Vinogradenko correct
To replicate: Busy dataset at destination. Start replication from sending side via SSH. Task shows as successful even if the replication task was not able to run due to a busy data set unmountable at destination (shows in task log)
Session ID: 7bef25e0-6a7e-ea27-b823-d5d7b783dcdd