Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Replication tels lies to Storage pools

Description

Hi there,

I have 2 pools:

QData on several disks z1
QNonMedia-Backup on 1 disk

I had 2 replication tasks all going to the QNonMedia-Backup Pool
One was execute first and put the whole QNonMedia-Backup pool in read only.
The second assumed it was succesfull and managed to let Storage even believe it.

It was a lie..

In attached screenshots one can clearly see that thereé a mismatch between MC and the gui of Truenas.

Problem/Justification

None

Impact

None

Activity

Show:

Vladimir Vinogradenko January 27, 2022 at 3:30 AM

As you say, your QNonMedia-Backup pool root dataset is read-only. As the error message says, replication to QNonMedia-Backup/Documenten succeeded (and the dataset is present in the UI), but QNonMedia-Backup/Documenten directory creation failed, because QNonMediaBackup is read-only. Please temporarily disable read-only property on QNonMedia-Backup and then create this directory manually; then, on the next replication, QNonMedia-Backup/Documenten will be mounted and you will be able to see its contents in the file manager.

Bonnie Follweiler January 24, 2022 at 4:01 PM

Thank you .

This ticket is now in our queue to review.

An engineering representative will update with any further questions or details in the near future.

iX-Tony January 21, 2022 at 9:46 PM

Thank you for the report, . Can you please attach a debug file to the "Private Attachments" section of this ticket? To generate a debug file on TrueNAS CORE, log in to the TrueNAS web interface, go to System > Advanced, then click SAVE DEBUG and wait for the file to download to your local system.

User Configuration Error
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Impact

High

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created January 20, 2022 at 10:29 PM
Updated July 6, 2022 at 9:01 PM
Resolved January 27, 2022 at 3:30 AM