Wrong available space on HDD

[funkey]

Is there a patch to show the right available space on HDD?

Information from Para
_ArchiveDisk

TotalKB: -2147483648
UsedKB: 827192688
AvailKB: 1320290452
FreeKB: 1320290452
AvailPerc: -60
FreePerc: -60
Status: OK

[leoknipp]

Hello,

without detailled knowledge about your installation (WinCC OA-version, operating system, size of the HD) we cannot tell you if there is a solution available.

Please refer to the official support address support.automation@siemens.com.
When sending the information to the official address please include the information which WinCC OA-version and which operating system you are using.

Best Regards
Leopold Knipp
Senior Support Specialist

[funkey]

Thank you for answering.

We use PVSS 3.9 running on

SUSE Linux Enterprise Server 11 SP1
Kernel 2.6.32.12-0.7-default
/home 2,8TB size 1,5TB used

[mweber]

Hi Christoph,

it looks like your hard drive is too big
all the values (total, free,...) are stored on internal datapoints (in kB) where the data type is defined as integer.
2,8 TB is a liitle bit too much for int range - (therefore the overflow to negative values) sorry for that.
It is the same in the releases 3.10 and 3.11 - we will consider that issue for future releases.


have a nice day

Markus

P.S.: as a temporary workaround you could change the data type _DiskSpaceCheck with the PARA tool and modify the TotalKB element to be unsigned integer - that should help (at least till your harddrives are below 4TB)

[funkey]

Thank you Markus,
I changed the element to be an unsigned integer, but there is still a negative value (-2147483648 !!??) in the UNSIGNED Integer in TotalKB. And I get following error message:

Code: Select all

PVSS00data   (0), 2012.08.14 07:34:01.887, PARAM,SEVERE,     54, Unexpected state, ValHistEngine, setValue, Falscher Variable-Typ 
System1:_ArchivDisk.TotalKB:_original.._value (Type: 10 Sys: 1 Dp: 122 El: 12 : _original.._value)
INTEGER_VAR

[leoknipp]

Hello,

it looks like the work around cannot be used due to the fact, that the data-manager is expecting an integer value.
Maybe it works when the project is restarted.

Otherwise please take back the changes and restart the project to avoid this log-message.
We have already informed our development department about this problem when using very large discs.
When a solution will be available we cannot tell you right now because we are still investigating the cause for the problem.

Best Regards
Leopold Knipp
Senior Support Specialist

[funkey]

I restartet the server without success. Now I changed the datatype back to (signed) integer.
I hope that there will be a solution some day.