[Info-vax] Problems detected with analyze/disk

[Bart.Zorn@gmail.com]

On Nov 22, 8:07 pm, anwa <anders_s_wal... at yahoo.se> wrote:
> On 22 Nov, 16:12, CY <christ... at gmail.com> wrote:
>
> > Hmm, TCPIP$REXEC_RUN.LOG should not be affected by 3:d party.. sho err
> > will not give anything?, on a san? did they do (assuming you are not
> > san master) anything? any analyze on the file just to get the really
> > good VMS hackers (and no I´m not one of them) started dir/full is
> > sorta ... no...
>
> > a m$ approach, all eco pacs in, latest version everywhere and so on.
>
> > Just my 2 cents...
>
> > //CY
>
> We use the usual C/C++/MMS/LSE/RDB development software from HP/
> Oracle.
> Aditionally GNU-AWK, Make and some jsvn (Java based Subversion
> client). Disks
> are SAN disks.
>
> My primary strategy is to get the disks repaired, and then keep a
> close look
> to make sure they behave as they should.
>
> The problem in this case seems to get rid of files with "unprintable"
> characters
> in their names, with just access to the file-id. With a full file spec
> I could have
> used the recommended procedure to copy all multiple allocated files
> and delete
> all but one, then repair the disk. Just don't know how to do it fith
> only file-id's.
>
> Thanks for all input
>
> Anders Wallin

I have been in a situation where our SAN storage management team saw
it fit to allocate one ldev to both our VMS cluster AND some u*x
system. Luckily it was our test cluster, but very strange things
happened!

In other words, let the SAN people double check their configuration!

HTH,

Bart