TOS 6 SMB unable to write, still gets (sys_get_quota) error

[hzink]

This goes back to a topic from 5 years ago, but shows up as well for 2023, and 2024... indicating that this issue isn't really being addressed at all:

2020: viewtopic.php?p=2581&hilit=sys_get_quota#p2581

2023: viewtopic.php?p=27298&hilit=sys_get_quota#p27298

2024: viewtopic.php?p=36459&hilit=sys_get_quota#p36459

On a moderately freshly installed TOS 6 installation on an F4-424 - I use it as a NAS sharing and storing files via SMB to Macs and Windows PCs. It has the latest version of TOS 6 (v6.0.783) installed.

Recently, when copying files to the F4-424, it kept giving errors and aborting the copy - sometimes right away, sometimes after copying a few files.

When checking the logs, this is the consistent error:

../../source3/lib/sysquotas.c:566(sys_get_quota) sys_path_to_bdev() failed for path [.]

After some digging around, this is an SMB error related to BTRFS and quotas. Quotas aren't possible under BTRFS (as the TOS 6 control panel tells me), but this is a persistent SMB issue related to BTRFS.

Unfortunately, TOS 6 formats the drives with BTRFS by default, and nothing has been done in terms of code to compensate for this issue - which essentially leaves the NAS in a more or less unusable state.

While the Terramaster hardware is solid, this makes TOS 6 (or TOS 5, which has the same issue), completely useless and unusable.

My only options left at this point are to attach a fast USB drive to the F4-424, and copy all my files over via a regular Linux file copy, or to backup via SCP or an FTP solution - then, reformat (since you can not really convert BTRFS to ZFS or EXT4, but need to reformat)

At which point I can put TOS 6 back and format as EXT4 (which allegedly doesn't have the issue), or bail on TOS altogether and install another NAS software like UNRAID, TRUENAS, or OpenMediaVault (which I am leaning towards right now, considering that this bug has been completely ignored by Terramaster, it appears, for 5 years - and it is rather fatal once it hits).

[TMnight]

Please schedule an appointment with an engineer for a remote inspection through the official website's online chat.

[hzink]

I think that this is all the response it gets, is all the answer we need regarding this issue.... sadly.

[EthanLiu]

Thank you very much for your patience and attention. We must admit that due to the long history of these issues and internal staff changes, some of the previous issues were indeed mishandled, which caused you trouble. We are very sorry for this. Please rest assured that we have a dedicated team to follow up and we will do our best to provide you with a satisfactory response as soon as possible.

[hzink]

Thank you very much for your patience and attention. We must admit that due to the long history of these issues and internal staff changes, some of the previous issues were indeed mishandled, which caused you trouble. We are very sorry for this. Please rest assured that we have a dedicated team to follow up and we will do our best to provide you with a satisfactory response as soon as possible.

Hi Ethan,

First of all, I appreciate the honesty and your reply ... as you stated yourself, this issue has a long history (it goes back 5 years) and still hasn't been addressed or fixed ... and as you can read, this issue makes the terramaster device virtually unusable as a file server (and that is, after all, the only purpose it has, right?)

Sure, this is under SMB and BTRFS - but SMB is pretty much all we can use for file services (NFS mounts, or using FTP aren't really practical work-arounds), and apparently the other NAS operating systems (TrueNAS, OMV, unRAID, Rockstor), all appear to have addressed this issue (or advise to use ZFS or plain EXT4).

What I am left with, right now, as my only option is to transfer everything on my F4-424 to my drobo (which works reliably and rock-solid as a NAS), and then reformat the Terramaster F4-424, and experiment with unRAID, TrueNAS, OMV, and maybe TOS 6 with ZFS instead of BTRFS.

Regardless, this gives me a very sub-optimal experience with Terramaster, as you can imagine.

[TMvalen]

Hello, we are very sorry for the bad experience you had. We have arranged for technicians to investigate this issue, but the environment cannot be reproduced. Please send the link of this post to the online customer service on the official website to make an appointment for an engineer to conduct remote troubleshooting.
https://www.terra-master.com
The real-time chat window is located at the bottom right corner of the official website.

[hzink]

Hello, we are very sorry for the bad experience you had. We have arranged for technicians to investigate this issue, but the environment cannot be reproduced.

Run latest version of TOS 6, on a F4-424.

Use a Mac with M1 Max as the initiating computer.

I have, now, also set up NFS sharing on that directory (NFSv4) -- and while it initially appears more stable, after a while the copy freezes when starting a copy, and can't be recovered from unless restarting the MacOS computer.

You probably are unable to reproduce the issue because you are using Windows PCs as the clients.

[TMvalen]

Dear User,

Thank you very much for your feedback and for the inconvenience caused by the issues with our product.

The SMB problem you encountered has been confirmed as a known compatibility issue. Currently, the repair work is in our development plan and is in the processing stage.

Before a complete fix is made, to avoid affecting your use, you can try the following temporary solutions:
[Method]: Try temporarily disabling the "Disable Files" option in the SMB advanced settings.

(Please note, this is a temporary mitigation measure. For a complete solution, please wait for the subsequent official update.)

We understand the significance of this issue and will prioritize the resolution process. Please keep an eye on system updates. We will release the fix as soon as it is completed. Once again, thank you for your patience and support!

[hzink]

Before a complete fix is made, to avoid affecting your use, you can try the following temporary solutions:
[Method]: Try temporarily disabling the "Disable Files" option in the SMB advanced settings.

(Please note, this is a temporary mitigation measure. For a complete solution, please wait for the subsequent official update.)

We understand the significance of this issue and will prioritize the resolution process. Please keep an eye on system updates. We will release the fix as soon as it is completed. Once again, thank you for your patience and support!

There is no 'disable files' option in the SMB advanced settings:

[TMvalen]

Sorry, please disable "Veto files" in the advanced settings of SMB.