| Title: | LSM |
| Moderator: | SMURF::SHIDERLY |
| Created: | Mon Jan 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 803 |
| Total number of notes: | 2852 |
This is has been cross-posted into Digital Unix conf. (#9379)...
A customer had a system crash (Machine Check) but unfortunately
the crash dump has not been saved because of LSM it seems...
>> savecore: Can't set LSM swap volume preference in
>> /dev/vol/rootdg/swapvol1
I had a look at a few points, but didn't succeed...
Here is the /etc/fstab:
-----------------------
chpd01> more /etc/fstab
root_domain#root / advfs rw 0 0
sys_domain#usr /usr advfs rw 0 0
sys_domain#var /var advfs rw
sys_domain#tmp /tmp advfs rw
/dev/vol/rootdg/swapvol1 swap1 ufs sw 0 2
#/proc /proc procfs rw 0 0
Here is the /etc/rc.config:
---------------------------
.
.
GATED_FLAGS=
PAGERAW="1"
PAGEFILE="/dev/re1c"
PARTITION="re1c"
PARTITIONTYPE="SWXCR"
PAGEMINSZ=0
PAGEMAXSZ=0
QUOTA_CONFIG=
.
.
To me, this indicates system is using /etc/fstab entries for
swapping !
No /etc/swapdefault:
--------------------
chpd01> ls -l /sbin/swa*
lrwxrwxrwx 1 root system 24 Jul 20 1996
/sbin/swapdefault.old -> /dev/vol/rootdg/swapvol1
-rwxr-xr-x 1 bin bin 155648 Jul 25 1995 /sbin/swapon
I found a similar case reported in conf LSM (note #733) but this
didn't help me either:
>> Savecore is getting an error while trying to set the swap volume's
>> read policy to preferred. This error could be caused either because
>> swapvol's minor number is not set to one (1) or because the swap
>> plex that resides on the boot disk is not enabled or configired.
chpd01> ls -l /dev/vol/rootdg/swapvol1
brw------- 1 root system 40, 10 Jul 20 1996
/dev/vol/rootdg/swapvol1
chpd01>
chpd01> file /dev/vol/rootdg/swapvol1
/dev/vol/rootdg/swapvol1: block special (40/10)
To me minor number does not seem to be 1, but 10 !???
And what could cause the swap plex that resides on the boot disk
not to be enabled or configured at startup after the system crashed ?
>> The primary swap must be configured as "swapvol", so that's probably
>> why it's failing.
Does it mean that the name MUST be "swapvol", in my case it's name
is "/dev/vol/rootdg/swapvol1" !
Can someone give me any tips to correct/troubleshoot this problem
which prevents my customer's machine to save the crash dumps...
If we cannot manage to fix this LSM problem, we'll be at the same
point next system crash...
Cheers,
============================
Alain MARTIN/SSG Switzerland
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 778.1 | More info needed | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Thu Apr 03 1997 13:20 | 11 |
Please,
Post the result of :
volprint -vht
voldisk list
uname -a
And also, how did you create the swapvol1 volume ?
| |||||
| 778.2 | volprint, voldisk and uname info... | LEMAN::MARTIN_A | Be vigilant... | Fri Apr 04 1997 07:40 | 87 |
Hi Manu,
>> the result of volprint, voldisk & uname :
Script started on Fri Apr 04 10:18:15 1997
chpd01# volprint -vht
V NAME USETYPE KSTATE STATE LENGTH READPOL
PREFPLEX
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT
ST-WIDTH MODE
SD NAME PLEX PLOFFS DISKOFFS LENGTH DISK-NAME
DEVICE
v swapvol1 gen ENABLED ACTIVE 4109296 ROUND -
pl swapplex1a swapvol1 ENABLED ACTIVE 4109296 CONCAT -
RW
sd swapdisk2-01 swapplex1a 0 0 4109296 swapdisk2
re9
pl swapplex2b swapvol1 ENABLED ACTIVE 4109296 CONCAT -
RW
sd swapdisk1-01 swapplex2b 0 0 4109296 swapdisk1
re1
v sysvol fsgen ENABLED ACTIVE 3847312 SELECT -
pl sysplex1a sysvol ENABLED ACTIVE 3847312 CONCAT -
RW
sd rz0g-01 sysplex1a 0 0 3847312 rz0g
rz0g
pl sysplex1b sysvol ENABLED ACTIVE 3847312 CONCAT -
RW
sd rz1g-01 sysplex1b 0 0 3847312 rz1g
rz1g
chpd01# voldisk list
DEVICE TYPE DISK GROUP STATUS
re0 sliced diskre0 sapdg online
re1 sliced swapdisk1 rootdg online
re10 sliced Sap1b-RE10 sapdg online
re11 sliced SapDB2b-RE11 sapdg online
re12 sliced SapDB3b-RE12 sapdg online
re13 sliced SapDB1b-RE13 sapdg online
re14 sliced diskre14 sapdg online
re15 sliced - - error
re2 sliced Sap1aRE2 sapdg online
re3 sliced SapDB1aRE3 sapdg online
re4 sliced SapDB2aRE4 sapdg online
re5 sliced SapDB3aRE5 sapdg online
re6 sliced diskre6 sapdg online
re7 sliced - - error
re8 sliced diskre8 sapdg online
re9 sliced swapdisk2 rootdg online
rz0g simple rz0g rootdg online
rz1g simple rz1g rootdg online
chpd01# uname -a
OSF1 chpd01 V3.2 148 alpha
chpd01#
>> And also, how did you create the swapvol1 volume ?
1) # voldiskadd
2) # volassist make swapvol1 2054648k rz1
3) # vi /etc/fstab
/dev/vol/rootdg/swapvol1 swap1 ufs sw 0 2
4) # rm /sbin/swapdefault
5) # shutdwon -r now
Swapon -s ouptput:
------------------
Swap partition /dev/vol/swapvol1:
Allocated space: 256831 pages (2006MB)
In-use space: 2118 pages ( 0%)
Free space: 254713 pages ( 99%)
Total swap allocation:
Allocated space: 256831 pages (2006MB)
In-use space: 2118 pages ( 0%)
Available space: 254713 pages ( 99%)
Hope it'l give any clue....
Cheers,
Alain
| |||||
| 778.3 | Unfortunately, this setup is unsupported. | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Fri Apr 04 1997 11:40 | 22 |
Aie! aie! aie! mon cher Alain,
Ah! The standard procedures have NOT been followed to create your
swap volume. The primary swap volume must be on the same disk as the
root volume, and must be encapsulated together with root.
There is no rootvol volume in your setup, and the swapvol1 volume is
not on a different disk than root.
So, your setup is completely unsupported and I can only advice you to
read in the LSM Admin guide the chapter about the root/swap
encapsulation and mirroring. There is also a lot of notes about the
system disk encapsulation/mirroring in this conference.
So you must find a free disk than can contain the root partition on the
partition A and the swap on partition B. The disk should also have at
least three unused partition (i.e. with "unused" in the fstyp field,
even if there is no free sectors allocated to them).
Sorry, but I cannot help you furthermore with this setup...
Regards, Manu.
| |||||
| 778.4 | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Fri Apr 04 1997 11:44 | 12 | |
Sorry, the next line
>>> There is no rootvol volume in your setup, and the swapvol1 volume
is not on a different disk than root.
should be read as
>>> There is no rootvol volume in your setup, and the swapvol1 volume
is on a different disk than root.
^^^^^^^^^^^^^^^^^
Manu.
| |||||
| 778.5 | Thanks Manu !!! | PANTER::MARTIN | Be vigilant... | Fri Apr 04 1997 13:18 | 9 |
Thanks Manu.
The things are much clear to me now !
I'll tell the customer that his config is not supported then...
Cheers,
Alain
| |||||