Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - jitdor

Pages: [1]
I have just upgraded my tRAID from 1.0 to 1.1 and when I try to sign in to the admin portal using Chrome, an error shows on the lower right corner and I'm not able to access the dashboard. However, on Edge and Firefox Quantum the portal works fine.

What could be the problem here? Thanks in advance.

General Discussion / Files randomly left behind on Landing Disk
« on: September 21, 2017, 12:05:46 pm »
I have a 7-disk configuration on tRAID that has been running for a few years, with a 128GB SSD formatted as a single ReFS partition being used solely as a landing disk.

Of late, I notice the landing disk buffer gets filled up very quickly, so I took a peek into the drive and noticed that the available storage is 50-60GB less. I make sure the landing disk is not in use before I took ownership of the hidden folders trying to find out what's hogging the space. To my surprise, there are a few old files being left over on the landing disk, which had already been copied to the array long ago. I am not able to find any pattern because it happens rather randomly - the files that are left behind have different creation dates and during the same period there are many other files of the same type and size which got transferred to the array and removed from the landing disk.

There is no implication to data integrity (so far) and the verify tasks always turn out to be successful. If anything the only compliant is that I need to check the available space on the landing disk regularly.

If anyone has any suggestions on why this occurred, I'd be happy to investigate further. Thanks!

I am using t-RAID on a 5-disk array running on Windows Server 2012 R2. I have followed the Wiki to add and set the System Environment Variable of "FLEXRAID_NZFS_LOG_LEVEL" to "error". Restarted it of course. But it is still churning out log files at an alarming rate -- 15GB of them in just a couple of days.

After reading the logs, I notice most of the log entries are "OnSetAllocationSize" and "OnSetEndOfFile" events -- which should not even appear under the "error" verbose setting at all. It seems the System Variable entries was not observed and simply ignored by the FlexRAID host service.

Is there anything else I could try? Thank you.

General Discussion / How to quickly identify file(s) in a specific range?
« on: December 21, 2015, 02:35:46 am »
Is there a way I can quickly identify a specific file (or files) that is stored within a range of the storage pool?

E.g. I want to know what are the exact files stored between xxxxx150 to xxxxx166 bytes.

Thank you!

General Discussion / Landing Disk Exclusion Rule for uTorrent *.!ut files
« on: November 21, 2015, 09:37:02 am »
I use a 128GB SSD as the dedicated landing disk for my T-RAID Storage Pool, and would like to experiment exclusion rules to the landing disk as there seems to be some issues with uTorrent when adding a big task with landing disk enabled -- even with the pre-allocation setting enabled.

As such, I would like to have an exclusion rule such that when the file name extension is !ut AND when the file size is >10GiB, the save would go directly to the array and bypassing the landing disk.

After reading the wiki, the closest thing I could come up for the above rule as Exclusion is

The above does not seem to be working. It might have something to do with the "!" being treated as negation but *.\!ut does not seem to work either...

Any help on the topic is appreciated. Thank you!

Performance Tuning / Optimizing Landing Disk for uTorrent
« on: May 10, 2015, 01:31:10 pm »
I am using a relatively large SSD volume formatted in ReFS as a landing disk in a t-RAID config. Is there a way to configure FlexRAID mover thread to leave the incomplete files (*.!ut) on the landing disk and only move them after downloading is completed?

In addition, I am seeing multiple WriteToDisk errors when working with very large (>20GB) torrents, which I suspect is caused by the tiered storage model (landing disk --> array).

Any help is appreciated!

Pages: [1]