Crash with Ftape, X11R6, & /proc/kcore

Crash with Ftape, X11R6, & /proc/kcore

Post by Jakob Schio » Wed, 25 Oct 1995 04:00:00




: I'm looking for some suggestions with this bug.  If I backup up my
: machine with 'tar cvfz /dev/ftape /' while X11R6 is running, the
: entire machine hangs forever as soon as tar encounters the file
: '/proc/kcore'.  This problem does not happen if X11R6 is not running.
: Nor did the problem happen before upgrading to the Slackware 3.0
: kernels.  Does anyone happen to have any ideas about this bug?

You should not backup /proc since it's just info about the current state of
the computer (anyway, restoring it might prove disastrous).  /dev/kproc is
probably the kernel memory, you certainly don't want to write there during
restore :-)

Jakob

--
Jakob Schiotz              !  Fax:    +1 (314) 935 6219
Department of Physics      !  Phone:  +1 (314) 935 4968

St. Louis, MO 63130, USA   !  WWW:    http://nils.wustl.edu/schiotz.html

 
 
 

Crash with Ftape, X11R6, & /proc/kcore

Post by Harvey Fishm » Wed, 01 Nov 1995 04:00:00




> : I'm looking for some suggestions with this bug.  If I backup up my
> : machine with 'tar cvfz /dev/ftape /' while X11R6 is running, the
> : entire machine hangs forever as soon as tar encounters the file
> : '/proc/kcore'.  This problem does not happen if X11R6 is not running.
> : Nor did the problem happen before upgrading to the Slackware 3.0
> : kernels.  Does anyone happen to have any ideas about this bug?

> You should not backup /proc since it's just info about the current state of
> the computer (anyway, restoring it might prove disastrous).  /dev/kproc is
> probably the kernel memory, you certainly don't want to write there during
> restore :-)

Yes, BUT...  What is a good way of NOT backing up /proc with Gtar?  Since
exclude does not function, I have been unable to easily pick and choose
what to copy and what not short of having find make me a list of explicit
files.  Thankfully I have not yet had to do a complete restore so I am not
really sure of the consquences of having saved /proc.  But I suspect that
this is really a read only thingie, though I am not really sure.  I HAVE
found that while I can generally cat /proc/*, I can not get at it with
emacs.  But I have been too busy learning a million and one other things
about my new toy (Linux) to follow this one through.

Harvey

--
----------------------------------------------------------------------------
 Harvey Fishman   |   It is easy to live by the laws that you agree with.

  718-258-7276    |        even the ones that you think are wrong.

 
 
 

1. /proc/kcore vs. /proc/meminfo

The problem: why does /proc/kcore give a different result for a memory size
than reported by /proc/meminfo? /proc/meminfo reports the actual amount in the
system (1.5GB), while kcore seems stuck at ~900MB. Which am I to believe?

This problem was discovered after I spent several hours trying to figure out
why neither the Redhat 7.1 Enterprise (2.4.3-12) edition nor the RH7.1
manually recompiled kernel with the 4GB|64GB memory option configured
recognized all 1.5GB of memory on my system. I kept looking at the size of
/proc/kcore, which never exceeded 1GB, even under the enterprise edition. It
wasn't until I checked /proc/meminfo that I noticed the discrepancy.

Thanks,
-Daniel Weber

2. getty for Zyxel 1494E+

3. /proc/kcore & /core what are those huge files for ?

4. Backup software for Sun's

5. Mosaic & X11R6 crashes

6. Cleanup of current->state for __set_current_state in linu x/fs/*.c

7. 16Mb kcore file in /proc

8. Resetting USB storage device name incrementer (sda)

9. How to control /proc/kcore ?

10. /proc/kcore

11. RFC: /proc/kcore

12. What is the file Kcore in /proc

13. Big "kcore" file in my /proc dir