So Are You Saying There's a Chance?

[Pac]

@miicar204

Its not large…i probably kept 4% after the restore

So it means it lost 96% of files? That’s weird, I would have expected the disqualification to be way faster in such a scenario. We’ve seen disqualifications happen in less than 24h in the past, but that was before the new audit system though.

@miicar204

BUT, atm, i am still getting uploads and downloads - starting and finishing…(along with download failed errors every log 100 entries or so)

There must be something I don’t get because this suggests only 1% of lost files… ^^’

@miicar204

Anyone ever have 2 nodes reaching on the same HDD array?

I think all kind of setups do exist, but some are better than others
It’s usually not recommended to have 2 nodes on the same HDD (and technically it goes against TOS):

Multiple Nodes per HDD to lower impact of node disqualification?

I don’t know if it is applicable: https://storj.io/storj-operator-terms/ 4.1.4. You will provide and maintain the Storage Node so that, at all times, it will meet the following minimum requirements (“ Minimum Storage Node Requirements ”): 4.1.4.1. Have a minimum of one (1) hard drive and one (1) processor core dedicated to each Storage Node;

I personally do have a disk that runs 2 nodes: 1 main node (4TB) and a small node (500GB) beside it that I kind of “incubated” so it’s ready to be deployed/expanded in the future.
I would not recommend doing that if you have other options because whenever the filewalker hits both nodes at the same time, the disk is crawling under heavy IO load (I believe RAID arrays do not help with regards to IO loads). Also, lose the disk, and you lose both nodes (although I guess a RAID5 kind of array is supposed to prevent that from happening).