[TOS7]Why My Shared Folders Are Not Editable/Visible?

[RyanYang]

Applicable Version:
TOS 7

Symptoms:
1. In the TOS 7.0 Control Panel, when editing shared folders generated via the Snapshot application from TOS 6, the information fails to load properly.
2. Such shared folders are not displayed in the TOS 7 File Manage.

Cause:
Due to optimizations in the system permission mechanism in TOS 7.0, shared folders generated via the Snapshot application from TOS 6.0 have permission configurations that are incompatible with the new mechanism. This results in the inability to edit permissions or display these folders normally in TOS 7.0.

Solution:
1. Determine the Target Shared Folder Path Information
All shared folders displayed in the Control Panel indicate the volume they belong to. You can use this information to determine the actual path.
For example, the "public" folder located in "Volume1" has an actual path of `/Volume1/public`.

2. Check Shared Folder Properties
Open the Terminal application from the "All Applications" section on the TOS desktop, and execute the following command (replace the path with the actual folder path recorded in step 1) to check the folder's read-only property:

Code: Select all

btrfs property get -ts /Volume1/public ro

Command Output Explanation:
If the output is `ro=true`, the folder is currently in read-only state, and the read-only flag needs to be removed.

3. Remove the Shared Folder Read-Only Flag (Execute only if `ro=true`)
Execute the following command to temporarily remove the read-only restriction on the folder (ensuring subsequent property configurations can be executed normally):

Code: Select all

btrfs property set /Volume1/public ro false

4. Add Extended Attributes to the Shared Folder
Execute the following command to add TOS 7.0-compatible extended attributes to the target folder:

Code: Select all

setfattr -n user.folder -v 1 /Volume1/public

5. Configure tmacl Permission Flags
Execute the built-in permission configuration tool to add tmacl permission flags to the folder (adapting to the TOS 7.0 permission control mechanism):

Code: Select all

/usr/sbin/aclconv

6. Restore the Folder's Read-Only Flag
Execute the following command to restore the folder to its original read-only state (maintaining the permission restriction logic of the Snapshot replication plan):

Code: Select all

btrfs property set /Volume1/public ro true

7. Process Other Shared Folders
If there are multiple target folders corresponding to replication plans, repeat the above steps by replacing `/Volume1/public` in the commands with the actual paths of other folders, completing the configuration one by one.

Note:
Shared folders generated by Snapshot replication plans are locked in a read-only state by default, allowing only viewing. Direct modifications, deletions, or permission adjustments are not supported. If such operations are required, delete the corresponding replication task in the Snapshot application first (deleting the task does not remove the data in the folder; it only releases the read-only lock), and then permissions can be modified or the folder can be deleted normally.