Sponsored Content
Full Discussion: Kernal Panic questions
Operating Systems SCO Kernal Panic questions Post 302458088 by ccd1977 on Wednesday 29th of September 2010 03:48:45 PM
Old 09-29-2010
OK. we did a fresh install on another box. Everything was good after we entered the keys and activated. But now we are getting an error.

It is getting an error for the swap file. It says, /Sbin/Swap:Can't determine Size of device '/dev/swap'; specify size explicitly

How do I resolve this on a Unixware 7.1.3?

Last edited by ccd1977; 09-29-2010 at 04:55 PM..
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

kernal parameters on Linux 7.3

Hi all, I am running 7.3 Redhat Linux, I have Oracle database running on it and I have some problem with the memory. every time I startup the database, the memory was peak up to 630M of Ram out 640M ram on the entire box and I didn't specify that much of memory on my database. Oracle advise me... (2 Replies)
Discussion started by: lapnguyen
2 Replies

2. UNIX for Dummies Questions & Answers

Kernal Panic

Received the following on the weekend. Panic:k_trap kernel mode trap type 0X0000000e cannot dump 163739 pages to dumpdev hd (1/41):space for only 48640 pages Dump not complete Safe to power off or press any key to reboot Any ideas how to fix this one? It also happen a month ago. (3 Replies)
Discussion started by: jcoleman544
3 Replies

3. Linux

reload kernal without reboot

Hello! Does anyone know howto reload your kernal without rebooting the machine? I´ve updated the "/etc/security/limits.conf " file and need to make this active without rebooting the machine. this is Red Hat Advanced Server 2.1AS Regards... dOzY (3 Replies)
Discussion started by: dozy
3 Replies

4. UNIX for Dummies Questions & Answers

Kernal Information

Hi friends, i would like to know the kernal information (semaphores), which command do i use Thanks (4 Replies)
Discussion started by: shaan_dmp
4 Replies

5. UNIX for Advanced & Expert Users

Questions regarding a PANIC situation

Hi, Last week, we experienced 2 KERNEL PANIC error on our SCO Unix 5.0.7 server within a 2 hour span. So I called our sofware support which is OGC using running on an Informix Database. Within 5 minutes I had as answer that the problem was an Hardware issue. Since the server is supported by... (4 Replies)
Discussion started by: adamsville2k
4 Replies

6. Linux

Kernal panic error& setuproot:error mounting /proc&/sys

Hi all, I am new to redhat/fedora linux. In fedora linux 6,we created one file system(hda3 - /fs). in this mount poing we were installed mounta vista os. while booting we are getting below error messages. 1) Booting 'mountaVisat(2.6.18_pro 500_pc_target-x86_586 smp)' root(hd0,1)... (2 Replies)
Discussion started by: arjunreddy3
2 Replies

7. UNIX for Dummies Questions & Answers

Panic kernal-mode address fault on user address 0x14

:) Firstly Hi all!!, im NEW!! and on here hoping that someone might be able to offer me some help... i have a server that keeps crashing every few days with the error message: PANIC KERNAL-MODE ADDRESS FAULT ON USER ADDRESS 0X14 KERNAL PAGE FAULT FROM (CS:EIP)=(100:EF71B5BD) EAX=EF822000... (10 Replies)
Discussion started by: Twix
10 Replies

8. Solaris

kernal parameter setting

hi, can anybody tell me how to increase the parameters like project.max-shm-ids on solaris10. i have used prctl, but got reset while server reboot. thnks and regards Ajay (1 Reply)
Discussion started by: ajaysahoo
1 Replies

9. Solaris

Kernal Parameters

Hi, Can you please let me know about kernal parameters? Where we can see that kernal parameters? we are using System = SunOS 5.10. Please let me know commands to see these kernal parameters file or files. (1 Reply)
Discussion started by: kancherla.sree
1 Replies

10. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
SYSTEMD.SWAP(5) 						   systemd.swap 						   SYSTEMD.SWAP(5)

NAME
systemd.swap - Swap unit configuration SYNOPSIS
swap.swap DESCRIPTION
A unit configuration file whose name ends in ".swap" encodes information about a swap device or file for memory paging controlled and supervised by systemd. This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The swap specific configuration options are configured in the [Swap] section. Additional options are listed in systemd.exec(5), which define the execution environment the swapon(8) program is executed in, in systemd.kill(5), which define the way these processes are terminated, and in systemd.resource-control(5), which configure resource control settings for these processes of the unit. Swap units must be named after the devices or files they control. Example: the swap device /dev/sda5 must be configured in a unit file dev-sda5.swap. For details about the escaping logic used to convert a file system path to a unit name, see systemd.unit(5). Note that swap units cannot be templated, nor is possible to add multiple names to a swap unit by creating additional symlinks to it. IMPLICIT DEPENDENCIES
The following dependencies are implicitly added: o All swap units automatically get the BindsTo= and After= dependencies on the device units or the mount units of the files they are activated from. Additional implicit dependencies may be added as result of execution and resource control parameters as documented in systemd.exec(5) and systemd.resource-control(5). DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set: o Swap units automatically acquire a Conflicts= and a Before= dependency on umount.target so that they are deactivated at shutdown as well as a Before=swap.target dependency. FSTAB
Swap units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). Swaps listed in /etc/fstab will be converted into native units dynamically at boot and when the configuration of the system manager is reloaded. See systemd-fstab- generator(8) for details about the conversion. If a swap device or file is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence. When reading /etc/fstab, a few special options are understood by systemd which influence how dependencies are created for swap units. noauto, auto With noauto, the swap unit will not be added as a dependency for swap.target. This means that it will not be activated automatically during boot, unless it is pulled in by some other unit. The auto option has the opposite meaning and is the default. nofail With nofail, the swap unit will be only wanted, not required by swap.target. This means that the boot will continue even if this swap device is not activated successfully. OPTIONS
Swap files must include a [Swap] section, which carries information about the swap device it supervises. A number of options that may be used in this section are shared with other unit types. These options are documented in systemd.exec(5) and systemd.kill(5). The options specific to the [Swap] section of swap units are the following: What= Takes an absolute path of a device node or file to use for paging. See swapon(8) for details. If this refers to a device node, a dependency on the respective device unit is automatically created. (See systemd.device(5) for more information.) If this refers to a file, a dependency on the respective mount unit is automatically created. (See systemd.mount(5) for more information.) This option is mandatory. Note that the usual specifier expansion is applied to this setting, literal percent characters should hence be written as "%%". Priority= Swap priority to use when activating the swap device or file. This takes an integer. This setting is optional and ignored when the priority is set by pri= in the Options= key. Options= May contain an option string for the swap device. This may be used for controlling discard options among other functionality, if the swap backing device supports the discard or trim operation. (See swapon(8) for more information.) Note that the usual specifier expansion is applied to this setting, literal percent characters should hence be written as "%%". TimeoutSec= Configures the time to wait for the swapon command to finish. If a command does not exit within the configured time, the swap will be considered failed and be shut down again. All commands still running will be terminated forcibly via SIGTERM, and after another delay of this time with SIGKILL. (See KillMode= in systemd.kill(5).) Takes a unit-less value in seconds, or a time span value such as "5min 20s". Pass "0" to disable the timeout logic. Defaults to DefaultTimeoutStartSec= from the manager configuration file (see systemd- system.conf(5)). Check systemd.exec(5) and systemd.kill(5) for more settings. SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.exec(5), systemd.kill(5), systemd.resource-control(5), systemd.device(5), systemd.mount(5), swapon(8), systemd-fstab-generator(8), systemd.directives(7) systemd 237 SYSTEMD.SWAP(5)
All times are GMT -4. The time now is 08:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy