What happened here? This icon, anyone know how to solve it?

 

What is the problem?  That is the standard icon for a file that has one of more files not currently protected (e.g. On a pool that is not redundant)

 

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

15 hours ago, itimpi said:

What is the problem?  That is the standard icon for a file that has one of more files not currently protected (e.g. On a pool that is not redundant)

 

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

 

I've done something to make the folder lose this protection, but I can't identify what.

I don't know how to read the diagnostics. I'll study the topic that explains it.
Tks

bdrtec-diagnostics-20240916-1119.zip

That share also exists on the VM_docker pool, and since that pool is not redundant, it will show the share as unprotected, if you move everything to the array it will correct that.

26 minutes ago, JorgeB said:

That share also exists on the VM_docker pool, and since that pool is not redundant, it will show the share as unprotected, if you move everything to the array it will correct that.

I honestly don't know how I did it.
In the folder settings (share) it says:

 

Primary storage (for new files and folders): Array

 

But the Vms_pool also has the folder. I executed some containers and maybe I created a folder in this pool. 

I'll try deleting it to see if it works (this folder is just a test, it doesn't contain any important data).

 

Thanks for the explanation, and I'll learn how to read this diagnostics.