HP3000-L Archives

February 2015, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gilles Schipper <[log in to unmask]>
Reply To:
Gilles Schipper <[log in to unmask]>
Date:
Sun, 15 Feb 2015 12:26:38 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (74 lines)
The fact your DSTAT ALL shows LDEV 2 as "LONER" indicates that it does 
NOT belong to an existing volumeset, despite the fact that it indicates 
MPEXL_SYSTEM_VOLUME_SET.

If it did, instead of "LONER", DSTAT would show "MEMBER".

(It could also show "MASTER" - but for the fact that it could only be 
true for LDEV 1 for the system volmeset.)

You should be able to add ldev 2 to the MPEXL_SYSTEM_VOLUME_SET via 
VOLUTIL.

Or, better still, you could use VOLUTIL to create a temporary TEST 
volumeset and then place a TEST account and some files therein to ensure 
the drive is okay.

When your testing is complete, you could VSCLOSE TEST, then use VIOLUTIL 
to add LDEV 2 to the MPEXL_SYSTEM_VOLUME_SET.


On 2015-02-15 12:08 PM, Chuck Trites wrote:
> That's the thing.  DTSTAT ALL shows LDEV 2 as LONER MEMBER2 and MPEXL_SYSTEM_VOLUME_SET.
> I personally did a LISTF on @.SYS account when I booted it as a production machine.  FSCHECK showed all was well about a month ago.  DISCFREE showed it about a month ago.  The NPCONFIG has the correct date for when I placed it production.
> Chuck [log in to unmask] Consulting, Inc.59 Doe Ave.Laconia, NH 03246Phone: (603) 219-1500
>   
>
>       On Sunday, February 15, 2015 11:47 AM, Ralph Bagen <[log in to unmask]> wrote:
>     
>
>   Chuck:
>
> As Ryan / Craig / Gilles are suggesting, perhaps LDEV 2 was never previously configured...
>
> However, even although you find LDEV 2 in a LONER state, a :DSTAT ALL should show any previous volume label... how does it appear there?
>
> Was an fscheck clean?
>
> Ralph Bagen
> MPE Support Group, LLC
> E-mail:  [log in to unmask]
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Chuck Trites
> Sent: Sunday, February 15, 2015 9:01 AM
> To: [log in to unmask]
> Subject: [HP3000-L] System_Volume LDev 2 went from Member Status to Loaner?
>
> I have an A500 that was put into production from a DR machine about a month and half ago.  This system has 2 System volumes and a Raid array as it's own volume set.  The LDEV 2 system volume is now showing as Loner status.  Has anyone ever seen this happen?  How else but a SCRATCHVOL or replacement of drive can the status go from Member to Loaner?  System running fine and full backup doesn't show any errors. There aren't many files on Ldev 2, but I would think the full backup would have had a problem trying to store those files. Chuck [log in to unmask] Consulting, Inc.59 Doe Ave.Laconia, NH 03246Phone: (603) 219-1500
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>     
>

-- 
-----------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
PO Box 77566 RPO Sheppard Plaza
Toronto ON M3H 6A7 Canada
Tel: 416.702.7900
email:  [log in to unmask]
web: http://www.gsainc.com
-----------------------------------------------------

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2