QTier on QuTS Hero 6.0

I’m having an issue with QTier not working after performing a 10s system reset.

I’m using the following hardware:

TS-h1090FU : 2 NVME SSDs working as the hot tier (two 8TB drives in RAID 0) and a separate sata system SSD (500GB)

A TL-R2400PES-RP expansion bay connected with QXP-3X8PES expansion card. There are 24 24TB drives arranged in a 8x3 RAID 6 array.

The QTier had been working but after I performed the system reset to correct some ACL permission mistakes I made, QTier has never restarted. It is set to run daiy at a specific time but nothing happens. There is data on the hot tier that should be written to the low-speed tier.

I’m using the following firmware: QuTS hero h6.0.0.3500

Is there any way of forcing the QTier to actually start? Or do I just have to wait and hope a new firmware will fix it at some point?

Thanks,

Gaetan

6.0.2

try this sw update

From my experience with Qtier, I would recommend using the automatic mode first.

I don’t know what type of data you are storing on your NAS, but in general the idea behind Qtier is that frequently accessed (“hot”) data should stay on the fast NVMe tier, while less frequently accessed (“cold”) data can be moved to the HDD tier. Qtier hero uses access patterns and configured policies to determine the appropriate tier for the data.

For example, if you have mostly video content and a particular video is accessed only once every 24 hours, I would not consider that truly “hot” data. There is probably no reason to keep all of that content on your NVMe tier.

Because of that, I would personally recommend letting Qtier work automatically rather than trying to manually control every transfer. The system can then optimize the placement according to the workload and configured tiering policy.

What I would try:

Set Qtier to Automatic and monitor what happens for a few days. Check the Qtier statistics/history to see whether data is actually being moved between the tiers. QNAP provides statistics for evaluating tiering activity.

If automatic tiering does not give you the result you want, then try a manual schedule during a period of low activity. I would not start with running it every hour. Tiering itself creates additional storage activity, so it is generally better to let it run during periods when the NAS is less busy.

If you really need the SSD/NVMe tier to contain the most recently or frequently used data as quickly as possible, you can experiment with a more frequent schedule and compare the results. The advantage is that active data can be promoted to the faster tier sooner, but the downside is additional tiering activity and more writes/movement between the tiers.

So my recommendation would be:

First: Automatic → monitor for several days → check Qtier statistics.

Second: if that doesn’t work well, try a scheduled tiering window during low-load hours and compare the results.

However, there is one important thing in your particular case: you said Qtier worked before the system reset and has never started again since the reset. If Qtier is not running at all, regardless of the schedule you select, then I would look at this as a possible Qtier/configuration problem rather than simply a question of choosing the right schedule. In that case I would check the Qtier status and system logs before making any changes to the storage pool.

Also, you are running h6.0.0.3500, which is the firmware version you mentioned. Since Qtier hero is a relatively new feature in QuTS hero h6.0, I would also make sure you are on a current supported firmware before concluding that the only solution is to wait for a future firmware fix. QNAP introduced Qtier hero with QuTS hero h6.0.

In short, I would not immediately force Qtier to run every hour. I would first use Automatic mode, observe the behavior and statistics, and only then increase the frequency if the workload actually requires it.

RAID0 is risky business as Qtier.

I haven’t used it on QuTS yet, but if QTS QTier stopped working, all storage (that is tiered) would be inaccessible, that is not the case here?

@dolbyman Just to clariy a few things: The QTier Storage Pool consists of 2 8TB NVME (RAID 1 fast tier) and 24 24TB HDD as the slow pool (RAID 6, 3x8). The entire storage pool is fully operational. The fast tier has filled up and it operating as it should when the fast tier is full: it just writes to the low-speed tier. The volume is setup with with 'Target Tier" : low-speed and the “write acceleration mode” to “write buffer”. So the only issue is that the tiering just doesn’t run anymore.

@Gunis My understanding is there is no automatic mode with QuTS Hero QTier…only the scheduled tiering.

I will try the latest firmwhere next, maybe that will kick it into gear.

Is there someplace you can see logs that might give an indication of why the Qtier is not starting on schedule?

Thanks,

Gaetan

Here you said the fast tier is RAID0, hence my remarks

And you said Qtier is "not working’, I guess you mean the tiering mechanism has stopped working (as a busted QTier would mean a fully busted storage pool)

Ah yes… I did say RAID 0 for the fast tier. That would be unbelieveably stupid!

not so

if u shedule drain it asap 30min +

@qverified How does one schedule a manual drain? I cannot see how to do that.

Thanks,

Gaetan

I’m aware of how to configure a schedule. QTier WAS working just fine before resetting. It is still configured, see below. The issue is at 21:55, precisely nothing happens. No data movement, status remains at “Idle”. It is as if the system completely ignores the trigger. Is there anywhere to get a log file to see if anything is happening when the qtier is supposed to trigger?

Thanks,

Gaetan