Author Topic: Transparent RAID (tRAID) Version 1.1 Preview release  (Read 5628 times)

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #60 on: February 16, 2017, 11:28:01 am »
Exactly the same behavior after having changed to NTFS (this issue is not ReFS-specific)
Broker logs will be needed here to substantiate.
The fix was tested to work perfectly for NTFS.

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #61 on: February 17, 2017, 04:55:38 am »
I have exactly the same behavior as I reported for ReFS. I appended a log file where I moved three folders named scenario1, scenario2 and scenario3 according to the earlier descriptions.

You have to scroll to the section from 2017-02-17 at about 12 o'clock. Normal recycle bin is disabled.

Still, this is perfectly acceptable for me, I just want to report.

To add something positive:
Note that through my whole migration process of about 12 TB not a single log entry has been created and the parity seems to be perfectly fine. The few remaining log entries are from the Mercurial issue (code=5) and my attempts to mount as removable (Code=87).

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #62 on: February 17, 2017, 04:59:22 am »
The issue with the collapsed drive file statistics chart was actually my own stupidity: After uncollapsing, it additionally had to be resized.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #63 on: February 18, 2017, 06:53:23 am »
I have exactly the same behavior as I reported for ReFS. I appended a log file where I moved three folders named scenario1, scenario2 and scenario3 according to the earlier descriptions.

You have to scroll to the section from 2017-02-17 at about 12 o'clock. Normal recycle bin is disabled.

Still, this is perfectly acceptable for me, I just want to report.

To add something positive:
Note that through my whole migration process of about 12 TB not a single log entry has been created and the parity seems to be perfectly fine. The few remaining log entries are from the Mercurial issue (code=5) and my attempts to mount as removable (Code=87).
Quite strange.

Scenario 1 & 3, the folder is opened without intent for deletion but gets deleted. Why Explorer would do that is a mystery.
In scenario 2, the empty folder gets opened for deletion and gets deleted. Another mystery is that was not the intended behavior.

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #64 on: February 20, 2017, 06:07:38 am »
Still no issues with the latest preview. Seems to work well. (Except the strange moving files issue)

Looks like NTFS also resolved my remaining Mercurial issues. At least I was not able to trigger any repository corruption so far during my tests ...

Only a slight remark: I occasionally get warnings "Exception while dispatching incoming RPC call org.eclipse.jetty.io.EofException" etc. in the Web UI log. This is typically accommodated by several "stop(41)" info entries during START of the Web UI (at least that's what the timestamp says). Looks like something get's stuck during shutdown there. I appended some excerpts of the web ui log to clarify. However, I do not detect any impact on the behavior of the Web UI itself.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #65 on: February 20, 2017, 09:09:48 am »
...
Only a slight remark: I occasionally get warnings "Exception while dispatching incoming RPC call org.eclipse.jetty.io.EofException" etc. in the Web UI log. This is typically accommodated by several "stop(41)" info entries during START of the Web UI (at least that's what the timestamp says). Looks like something get's stuck during shutdown there. I appended some excerpts of the web ui log to clarify. However, I do not detect any impact on the behavior of the Web UI itself.
There is a file named log4j.properties in the installation directory.
There should be a line that reads "log4j.logger.org.eclipse.jetty=ERROR".
Do you have that line?

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #66 on: February 20, 2017, 09:18:35 am »
Yes:

[...]

log4j.logger.com.tchegbe=INFO
log4j.logger.org.eclipse.jetty=ERROR
log4j.logger.org.quartz=ERROR
log4j.logger.com.google.gwt=ERROR
log4j.logger.com.metaparadigm.jsonrpc=ERROR
log4j.logger.java.lang.Thread=ERROR

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #67 on: February 20, 2017, 12:44:08 pm »
Please update that entire section to:
Code: [Select]
log4j.logger.com.tchegbe=INFO
log4j.logger.org.eclipse.jetty=ERROR
log4j.logger.org.quartz=ERROR
log4j.logger.com.google.gwt=ERROR
log4j.logger.com.metaparadigm.jsonrpc=ERROR
log4j.logger.java.lang.Thread=ERROR
log4j.logger.javax.servlet=ERROR

Changes have been made for the next build.
Thanks.

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #68 on: February 20, 2017, 01:54:28 pm »
Strange:

After I had updated the log properties file and restarted the server, the success e-mail message of the last Verify Sync was resent (it initially arrived 5 hours ago).

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #69 on: February 20, 2017, 03:41:38 pm »
Confirmed. Please add to bug.flexraid.com as low priority for later.

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #71 on: February 21, 2017, 12:36:16 pm »
FYI:

With log properties file changed, I get the same warnings, but now during the shutdown period.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #72 on: February 21, 2017, 12:48:43 pm »
FYI:

With log properties file changed, I get the same warnings, but now during the shutdown period.
As ERROR or WARNING.
The change is more of a log filter than resolving the error itself. It is actually not a defect, which is why suppressing the log is the proper thing to do.

Offline adridolf

  • Jr. Member
  • **
  • Posts: 89
  • Karma: +0/-0
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #73 on: February 21, 2017, 01:55:01 pm »
Warning. As before (log attached).

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,385
  • Karma: +201/-15
    • View Profile
Re: Transparent RAID (tRAID) Version 1.1 Preview release
« Reply #74 on: February 21, 2017, 04:13:16 pm »
The log is exactly the same as before.
The recent entries show no issue. Meant to attach something different?