Open Drive Files entry found size not matching actual data size

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Open Drive Files entry found size not matching actual data size

Re: Open Drive Files entry found size not matching actual data size

by Alt » Mon May 15, 2023 3:15 pm

You may play with memory settings. Read more in our help: R-Linux Settings -> Memory Usage.

Re: Open Drive Files entry found size not matching actual data size

by mattwood2000 » Mon May 15, 2023 12:58 pm

I think I found the issue. The machine I set this up on to load the scan file only has 16G of RAM. I saw it crash when it hit the limit so I suspect the OOM just kills it.

It would be nice if there was some more verbose output from R-Linux.

Thanks, Mat

Open Drive Files entry found size not matching actual data size

by mattwood2000 » Mon May 15, 2023 9:23 am

Hi,

Using the R-Linux 6.2.191150.

I have loaded a drive scan info file and I'm attempting to open the drive files found on a recognized EXT4 partition. The drive is 4TB and the recognized partition is 3.64TB.

The open files dialog is stuck at 94%. The total files/folder count keeps increasing but the total size is reporting 51+ EB which does not make any sense.

I've attempted the file open process a couple of times and left the computer only to come back and find R-Linux closed (crashed/killed) with no error messages.

I've opened it on the console this time so hopefully there will be some stderr message. Wondering if anyone else has seen this kind of behavior?

Thanks!

Top