Author Topic: Verify+ passing info. to Verify Sync  (Read 1703 times)

Offline jpearn

  • Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
    • View Profile
Verify+ passing info. to Verify Sync
« on: August 05, 2013, 07:09:41 am »
Just a thought, is it possible that after running a Verify+, the parts which fail could then be Verify Synced with minimal user interaction ?? I'm still getting to grips with the system and trying to pick up the odd 4k bits which fail is a bit hit / miss, so it's easier to run a Verify Sync each time. Which is a bit long winded.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Verify+ passing info. to Verify Sync
« Reply #1 on: August 05, 2013, 08:00:47 am »
If user interaction is to be avoided, then just run the Verify Sync task.
No need to run Verify+ first and then pass the info to Verify Syn.

What would have made sense was if you had stated that after the manual review of Verify+ a user was to choose to sync the affected blocks.
In this case, skipping all the other blocks would save much time.

Offline NLS

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1,018
  • Karma: +29/-4
  • Look ma, no hands!
    • View Profile
    • iLogic
Re: Verify+ passing info. to Verify Sync
« Reply #2 on: August 05, 2013, 08:05:37 am »
Would be nice if system just marked the unsynced blocks when verify+ and then offer the option to verify-sync those only.
---
NLS
Production system: SBS2011 fully patched, intel Core2 Quad, 8GB, 12 disks (1 system IDE, 1 backup IDE, 10 for array and parity most SATA3), parity is 3TB, largest data disk is 3TB, millions of smaller files, common browser Chrome latest.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: Verify+ passing info. to Verify Sync
« Reply #3 on: August 05, 2013, 08:10:31 am »
Would be. However, tracking many blocks is not possible.
A few ranges could be recorded, but tracking specific ranges would take up too much memory.

The reality is, users just have to run the Verify Sync task.
It will automatically abort on disk error, which is the only case where a user would not want to sync the failed blocks.
Outside of a fails disk, there is no other scenario where a user would choose not to sync.

Offline jpearn

  • Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
    • View Profile
Re: Verify+ passing info. to Verify Sync
« Reply #4 on: August 05, 2013, 08:11:44 am »
If user interaction is to be avoided, then just run the Verify Sync task.
No need to run Verify+ first and then pass the info to Verify Syn.

What would have made sense was if you had stated that after the manual review of Verify+ a user was to choose to sync the affected blocks.
In this case, skipping all the other blocks would save much time.

Yep, that's what I was leaning towards !