[Damaged Drive Always Damaged?]

On 9/29/2021 at 6:11 PM, Christopher (Drashna) said:

Are the bad sectors showing up under the sector/surface scan part?   If so, the only way to permanently clear them is to write to those locations, which should force the disk to remap/reallocate those sectors.  

However, StableBit Scanner doesn't have that ability, intentionally.  We activately avoid writing to the disk, to fix issues, as it can prevent data recovery from working properly. 

That said, a "chkdsk /b" pass may help here... but worst case, a full (non-quick) format will get the job done (and possible find and fix other sectors that havent been identified as bad, yet). 

/b seems to just clear the damaged sectors, but what is needed is a way to acknowledge the damaged sectors but stop reporting it in Scanner.  I had the same problem and I don't want my disk to stop being used unless the damage is significant.  There needs to be a method in Scanner to mark a damaged drive as healthy again, the same way you can mark a damaged file system as healthy again.

[Previous file versions?]

Is it possible to access previous file versions with StableBit DrivePool, like the Windows file history?  It's making copies anyway, right?  

And secondly, with this same process, can you find a file you previously deleted?

[Hardlink Support, again]

46 minutes ago, Christopher (Drashna) said:

For DrivePool, hardlink support won't ever happen.  This is because of how hard links work.  

Specifically, hard link files basically link to the same set of data, on the same volume. They cannot exist across  disks/volumes, because the data resides on the volume. 

Because the driver for StableBit DrivePool pool drive forwards the info to the underlying disks, there isn't a way to support hard links.  And even if there was, it would be expensive in terms of performance.  And since that happens in the kernel, that could grind the system to a halt. 

 

 

Yes, that's basically what I said.  My question was, what are my alternatives to achieve a similar result?

46 minutes ago, Christopher (Drashna) said:

For DrivePool, hardlink support won't ever happen.  This is because of how hard links work.  

Specifically, hard link files basically link to the same set of data, on the same volume. They cannot exist across  disks/volumes, because the data resides on the volume. 

Because the driver for StableBit DrivePool pool drive forwards the info to the underlying disks, there isn't a way to support hard links.  And even if there was, it would be expensive in terms of performance.  And since that happens in the kernel, that could grind the system to a halt. 

 

 

Yes that's basically what I said.  My question was, what are alternatives to achieve a similar result?

[Hardlink Support, again]

Hello.

So I have been reading all the details about Hardlinks not supported and Symbolic links will basically do the same thing.  Here is my issue.  I teach various subjects and film videos that are quite large.  Many times these videos fit into multiple subjects and I had been using Hardlinks because it saves me space, and, I don't want the original to be deleted before I am done with the data that exists in another topic via a hardlink, especially since I lose track of how many times I used that video and where the original is.  So If I used a shortcut and delete one topic once I am finished with it, I may delete the data that only exists as a shortcut in another topic that would now no longer work.  Hardlinks solved that problem since the data doesn't actually delete until ALL hardlinks have been deleted.  How can I now work around this since Hardlinks are not supported?  Straight out copying the data which is huge is not an option.

Thanks.