public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>,
	"Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux Geek <bourne@ToughGuy.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tar'ing /proc ???
Date: Thu, 16 Jan 2003 10:30:45 -0600	[thread overview]
Message-ID: <200301161030.45349.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <Pine.LNX.4.51.0301161505570.20335@dns.toxicfilms.tv>

On Thursday 16 January 2003 08:06 am, Maciej Soltysiak wrote:
> > Normally, you do `tar -clf`
> >
> >                         |________ stay on the same file-system.
> >
> > Otherwise toy need to use --exclude /proc.  Proc is a virtual
> > file-system that contains things like kcore. You can get into
>
> Well i think that besides kcore (and maybe kmem) you should be able
> to archive it.

Ummm not really - consider what some of the data files disappear while
tar is running (process directory tree). You may be in the process of
copying the process memory space when the process exits.

Kablooie

Your current directory just disappeared, along with the other files
you were going to backup.

You end up with a corrupted tar file.

I used to consider this as being possible to make a system
"snapshot" for later examination... but no.

Consider that a process will change contents out from under
tar as well. Since the process memory changed, you cannot
get a consistant process dump.

And think about what happens when the tar starts copying
itself... You can/will get another deadlock.

In fact - you may get a deadlock whenever you read process
memory - that stuff can extend/contract as the system pages
things in and out of memory.

-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

  parent reply	other threads:[~2003-01-16 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 14:02 Tar'ing /proc ??? Linux Geek
2003-01-16 14:04 ` Richard B. Johnson
2003-01-16 14:06   ` Maciej Soltysiak
2003-01-16 14:20     ` Richard B. Johnson
2003-01-16 14:32       ` Linux Geek
2003-01-16 16:30     ` Jesse Pollard [this message]
2003-01-16 14:20   ` Linux Geek
2003-01-16 14:25     ` Richard B. Johnson
2003-01-17 10:50 ` DervishD

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200301161030.45349.pollard@admin.navo.hpc.mil \
    --to=pollard@admin.navo.hpc.mil \
    --cc=bourne@ToughGuy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=solt@dns.toxicfilms.tv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox