Disks in cluster erroneously reported as full by VMS

[Jan van den Ende]

@Zeni,

>>>
All when I was checking I think I used the modified date so that if the file was one that existed but was growing, that it would be reported,too.
<<<

Unlikely, as the Modified Date only gets updated when the file is closed.

Permanently open files will never update it.

Proost.

Have one on me.

jpe

[Zeni B. Schleter]

@Jan

Going from memory in my suggestion. After the fact, I knew it was open scratch files with huge allocations from sorting. Before finding the problem , I was looking for any possible growth. I have seen uses where empty files are copied and appended to and deleted. Original date is the template creation and the modification reflects its update.

[Robert Brooks_1]

I've checked our MSCP_LOAD value and this is set to '1'. We also use Volume Shadowing between the MSA boxes (each node has a connection to each MSA). Is this wrong, as suggested in an earlier post?

--

That looks fine to me; I have no idea what the previous poster who implied there might be a problem was thinking.

Mixing Shadowing and MSCP-serving is certainly supported! One can obviously shadow a served member unit.

What does not work is the MSCP-serving of the virtual unit (the "DS" device). The notion that it's not supported is technically true, but it flat out will not work, so it's absolutely impossible to get oneself into that type of supported configuration.

Perhaps the posted with the concern was thinking of a different problem?

-- Rob (who has spent a fair amount of time inside both SHDRIVER and DUDRIVER).

[Jon Pinkley]

>>>I've checked our MSCP_LOAD value and this is set to '1'. We also use Volume Shadowing between the MSA boxes (each node has a connection to each MSA). Is this wrong, as suggested in an earlier post?<<<<

That is fine. I am not sure what Andy Bustamante was referring when he stated "In other words are you mixing shadowing and MSCP disk serving? That isn't a supported configuration."

You cannot MSCP serve the DSA virtual units, but creating DSA virtual units from MSCP served memebers is supported. In your case, it will create a backup path in case all direct fibre paths to the node fail, as in the following:

$ sho dev/ful dga6902



I/O paths to device 3
Path PGA0.5000-1FE1-500B-89BD (SIGMA), primary path, current path.
Error count 0 Operations completed 624
Path PGA0.5000-1FE1-500B-89B9 (SIGMA).
Error count 0 Operations completed 352
Path MSCP (OMEGA).
Error count 0 Operations completed 0

$

Jon

[Andy Bustamante]

Robert Brooks is correct and I was in error. I've been making an assumption concerning shadowing and MSCP serving. One of the reasons I'm hear is to continue learning.


Andy Bustamante

[Wim Van den Wyngaert]

Something like this done by your applic ?

WSYS01/MGRWVW>sh dev sd

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt

WSYS01$DKA0: Mounted 0 WSYS01_SYST 600472 502 1
WSYS01/MGRWVW>copy nl: sd:[000000]wim.lis/alloc=10000
WSYS01/MGRWVW>sh dev sd

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt

WSYS01$DKA0: Mounted 0 WSYS01_SYST 590552 497 1
WSYS01/MGRWVW>open/read/shared x sd:[000000]wim.lis
WSYS01/MGRWVW>del sd:[000000]wim.lis;
DELETE SD:[000000]WIM.LIS;1 ? [N]: y
%DELETE-I-FILDEL, SD:[000000]WIM.LIS;1 deleted (10000 blocks)
WSYS01/MGRWVW>sh dev sd

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt

WSYS01$DKA0: Mounted 0 WSYS01_SYST 590552 500 1
WSYS01/MGRWVW>close x
WSYS01/MGRWVW>sh dev sd

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt

WSYS01$DKA0: Mounted 0 WSYS01_SYST 600552 499 1

Wim

[Wim Van den Wyngaert]

WWhat I wanted to say is that your application may have files in use that are already deleted and thus do not show up in dir.

Wim