Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #204075

Re: Upgrade Problem

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Fri, Jan 04, 2019 at 05:04:49PM -0500, songbird wrote:
> Roberto C  Sánchez wrote:
> ...
> > It might also indicate files that exist (i.e., occupy blocks) without
> > having directory entries.  For example, this is the case when a program
> > creates a temporary file, gets the descritor back from the syscall, then
> > immediatley calls unlink on it [...]

Even easier: you rm a file which is still held open by some program
(a log file may be a typical example). The file will continue existing
until the last program which has an open file descriptor to it closes
it. If you think of it, it just makes sense.

[...]

>   wouldn't fsck clean that up?

No, definitely not. Terminating the processes keeping the file open
will help (i.e. reboot will most definitely help).

>   if it might be potential useful information you were missing
> and wanted to get back you could copy the entire partition and
> then run a recovery/forensics program on it to see what it all
> was.

There are tricks to it: open files are to be found in /proc/<PID>/fd:
there are some amusing war stories of clever sysadmins recovering
things from there after some mess-up.

Cheers
-- tomás

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-04 17:20 +0100
  Re: Upgrade Problem steve <dlist@bluewin.ch> - 2019-01-04 17:50 +0100
    Re: Upgrade Problem Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-01-04 18:00 +0100
      Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 18:10 +0100
        Re: Upgrade Problem Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-01-04 18:20 +0100
          Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-04 21:50 +0100
            Re: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 22:20 +0100
              Re: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-04 23:10 +0100
                Re: Upgrade Problem Michael Stone <mstone@debian.org> - 2019-01-04 23:40 +0100
                Re: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-05 15:50 +0100
                Re: Upgrade Problem <tomas@tuxteam.de> - 2019-01-05 10:20 +0100
              Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-05 02:10 +0100
            Re: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-04 23:10 +0100
      Re: Upgrade Problem Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-01-04 18:10 +0100
    Re: Upgrade Problem Roberto C. Sánchez <roberto@debian.org> - 2019-01-04 18:20 +0100
      Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-04 19:00 +0100
        Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-04 19:20 +0100
          Re: Upgrade Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-01-04 20:10 +0100
            Re: Upgrade Problem Brian <ad44@cityscape.co.uk> - 2019-01-04 22:10 +0100
            Re: Upgrade Problem David Wright <deblis@lionunicorn.co.uk> - 2019-01-05 02:30 +0100
              Re: Upgrade Problem Felix Miata <mrmazda@earthlink.net> - 2019-01-05 04:20 +0100
                Re: Upgrade Problem Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-01-05 10:30 +0100
              Re: Upgrade Problem rhkramer@gmail.com - 2019-01-05 16:30 +0100
                Re: Upgrade Problem John Crawley <john@bunsenlabs.org> - 2019-01-07 04:00 +0100
                Re: Upgrade Problem mick crane <mick.crane@gmail.com> - 2019-01-08 15:40 +0100
  Re: Upgrade Problem songbird <songbird@anthive.com> - 2019-01-04 19:30 +0100

csiph-web