Can't create a Pathworks Share

[Karen Lee_3]

I have lot's of pathworks shares - all the same configuration. I added a new raid array and now it won't let me add it.

RTP\\USPAX3> add share/dir pathw_rtp34 diska34:[000000]
%PWRK-E-ERRADDSHARE, error adding share "PATHW_RTP34"
-LM-E-NERR_UNKNOWNDEV, the device or directory does not exis

this is no different from my other devices -same protection and ownership - logicals are the same


%SYSMAN-I-OUTPUT, command execution on node USPAX3
"DISKA34" = "$1$DGA104:" (LNM$SYSTEM_TABLE)
%SYSMAN-I-OUTPUT, command execution on node USPAX1
"DISKA34" = "$1$DGA104:" (LNM$SYSTEM_TABLE)
SYSMAN> do show logical diska33
%SYSMAN-I-OUTPUT, command execution on node USPAX3
"DISKA33" = "$1$DGA111:" (LNM$SYSTEM_TABLE)
%SYSMAN-I-OUTPUT, command execution on node USPAX1
"DISKA33" = "$1$DGA111:" (LNM$SYSTEM_TABLE)

what's up with this?

[Kris Clippeleyr]

Karen,
Haven't got the faintest idea, but are the logicals for the disk defined /EXEC ?
Kris (aka Qkcl)

[Wim Van den Wyngaert]

Found this in another thread :

XDN\\SALES2> add share /dir transfer datadisk:[pc_transfer]
%PWRK-E-ERRADDSHARE, error adding share "TRANSFER"
-LM-E-NERR_UNKNOWNDEV, the device or directory does not exist

I tried using SALES2$DKA600: instead of DATADISK in the share directory specification and it worked...

XDN\\SALES2> add share transfer SALES2$DKA600:[PC_TRANSFER]

Apparently it doesn't like the logical name "DATADISK" in the share specification, even though that was what worked for the last 9 years.

When I restored the system disk, I enabled cluster support. After this change, Pathworks wouldn't work with DKA600: -- it needed to be SALES2$DKA600:.

I redefined the exec mode logical name as follows...

$ define/SYS/EXEC DATADISK SALES2$DKA600: /translation=conceal

And then the original share definition worked...

XDN\\SALES2> add share transfer datadisk:[pc_transfer]
%PWRK-S-SHAREADD, share "TRANSFER" added on server "SALES2"

I guess this is just a Pathworks thing, because I find that the following 2 commands produce the same results:

$ dire dka600:[pc_transfer]
$ dire sales2$dka600:[pc_transfer]

[Petr Spisek]

Hi,
the PATHWORKS doesn't know a newly added disk. Try to (after mount disk) restart PATHWORKS and command will be done.
Petr

[Dave Gudewicz]

Karen,

Did you stop and restart your Advanced Server *after* adding the new raid array?

Dave...

[T. Simpson]

You just need to re-synchronize Advanced Server with the current disks, not restart it.

$ ADMIN SET COMPUTER /AUTOSHARE_SYNCHRONIZE

should do it if the problem is a disk that was not around when Advanced Server was started

[Dave Gudewicz]

Forgot about: (thanks T.Simpson)

ADMIN SET COMPUTER /AUTOSHARE_SYNCHRONIZE

Better than toggling the server, especially when not necessary.

Dave...

[Karen Lee_3]

they re-sync worked - thanks guys

[Jan van den Ende]

Karen,

this may be superfluous, but note that the
/TRANS=CONCEAL
in the DEFINE (as it is also in the example Wim gave above)
is ESSENTIAL

Since it does normally show up in SHOW LOGICAL, it is often overlooked.

hth

Proost.

Have one on me.

jpe

[Aaron Sakovich]

If it IS version numbers, you can reset the version numbers of multiple versions of a file simultaneously from 32767 - 32767-n, to n - 1:

$ rename myfiles.txt;* myfiles.tmp;
$ rename myfiles.tmp;* myfiles.txt;

This is useful when you've got a log file locked open for write, but want to retain more than just the one latest version, for example.

Aaron

[Karen Lee_3]

The problem was resolved with the RESYNC command - thanks everyone.

[Ian Miller.]

Karen,
parhaps you could find time time to assign some points. See

http://forums1.itrc.hp.com/service/forums/helptips.do?#33