[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9379.0. "savecore: Can't set LSM swap volume preference..." by PANTER::MARTIN (Be vigilant...) Thu Apr 03 1997 09:21

    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.RTitleUserPersonal
Name
DateLines
9379.1look at LSM note #778...PANTER::MARTINBe vigilant...Fri Apr 04 1997 10:367
    For those of you how are interested, I cross-posted this into
    LSM conference (note #778).
    
    Answer is that customer didn't follow the procedure for 
    encapsulating root/swap !
    
    Alain