09-04-2002
Disk Usage
This problem could of Heavy disk Usage
try
a) by increasing SWAP space
use swapadd
or for more details check out man swapadd
b) by cleaning disk ie., run any disk managment package
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
When I came officce this morning I saw this error messages on the screen
-----
PANIC:srmountfun - Error 6 mounting rootdev hd (1/42)
Cannot dump 32639 pages to dumpdev hd (1/41) : space for only 0 pages
Dump not completed
--------
and machine was reboot mode. Why this problem... (3 Replies)
Discussion started by: alisev
3 Replies
2. UNIX for Advanced & Expert Users
Hi
I have a compaq server and the raid controller has crashed it was a Smart Array 3200 and was replaced with a Samrt Array 5300.
The problem I have is that it gets to a certain point in booting and comes up with a error message PANIC - error 19 error loading root dev. I am using sco openserver... (2 Replies)
Discussion started by: nhulley
2 Replies
3. UNIX for Dummies Questions & Answers
hello :-)
I have one problem with my LiLO... I installed PLD Linux on my computer but when it boots, the last thing I can see is:
request_module Root fs not mounted
VFS: Cannot open root device 03:01
Kernel panic: VFS: unable to mount root fs on 03:01
and the system stops :-(
what... (1 Reply)
Discussion started by: pgas
1 Replies
4. SCO
Hi Friends ,
i am getting the following error when iam booting a sco unix system.
------------------
H init
PANIC : srmountfun --Error 22 mounting rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : space for only 0 pages.
Dump not completed.
Safe to power off.... (1 Reply)
Discussion started by: sveera
1 Replies
5. Linux
I have compiled kernel version 2.6.12 in my linux box mandrake 10.1. I have followed www.digitalhermit.com/linux/Kernel-Build-HOWTO.html instructions. I have copied .config file from /usr/src/linux and lightly modified it (only the processor type) by xconfig. I have compiled the source and modules.... (3 Replies)
Discussion started by: Davide71
3 Replies
6. SCO
Anyone know how you go about interrogating a panic / core dump with crash for SCO Unix (5 Replies)
Discussion started by: ccarcher
5 Replies
7. Solaris
Hi All, I've been troubleshooting this sendmail panic I'm getting on my dmesg. The errors are:
Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: Losing ./qfl1G1hGuD000884: savemail panic
Feb 16 09:44:17 fakeserver_name sendmail: l1G1hGuD000884: SYSERR(root): savemail: cannot save... (2 Replies)
Discussion started by: grumash
2 Replies
8. Solaris
Hello experts..
What is system panic? If a system is in that state.. what will happen?
Why is it goes to panic condition?
Just give me information about Panic condition.. How can i resolve this issue..?
If you know any links(URL) or Books...? replay me back....
Thanks in... (5 Replies)
Discussion started by: younus_syed
5 Replies
9. Red Hat
Hi,
one of our linux server got panic with the following messages
Jun 2 17:09:57 inchesfttu006 kernel: ------------------------
Jun 2 17:09:57 inchesfttu006 kernel: kernel BUG at kernel/exit.c:904!
Jun 2 17:09:57 inchesfttu006 kernel: invalid operand: 0000
Jun 2 17:09:57 inchesfttu006... (1 Reply)
Discussion started by: rajasekg
1 Replies
10. SCO
Hello
when i booting my SCO Server I become this Message
PLS can anyone help me?
Cheers
Christoph (1 Reply)
Discussion started by: cga
1 Replies
LEARN ABOUT OSF1
volreattach
volreattach(8) System Manager's Manual volreattach(8)
NAME
volreattach - Reattaches disk drives that have once again become accessible
SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...]
/usr/sbin/volreattach -c accessname
OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the
failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the
name of the disk group and disk media name at which the disk can be reattached is displayed.
DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment.
This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical
Storage Manager is started, causing disks to enter the failed state.
If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the
reattach happens before any volumes on the disk are started.
The volreattach command is called from the voldiskadm menus as part of disk recovery.
The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching
disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists.
EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned.
SEE ALSO
volintro(8), voldiskadm(8), volrecover(8)
volreattach(8)