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


Groups > linux.debian.user > #204050

Re: Upgrade Problem

From Michael Stone <mstone@debian.org>
Newsgroups linux.debian.user
Subject Re: Upgrade Problem
Date 2019-01-04 23:40 +0100
Message-ID <xcGie-5VD-27@gated-at.bofh.it> (permalink)
References (3 earlier) <xcB8S-2W9-19@gated-at.bofh.it> <xcBiy-2Zh-9@gated-at.bofh.it> <xcEzM-4QW-21@gated-at.bofh.it> <xcF2O-5gm-25@gated-at.bofh.it> <xcFPd-5LN-33@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | 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.  The file descriptor is still active and
>> the file can be written/read with the descriptor reference, but the file
>> cannot be seen with 'ls' and, as I recall, it will not show up in the
>> calculation made by 'du'.  The calculation made by 'df' will still be
>> accurate, though.
>
>  wouldn't fsck clean that up?

not if the program is still running; it's not an error condition. the 
only case where fsck would help is if the whole machine crashed.

the traditional gotcha for "nonexistent file taking up space" is 
something generating a large log file, when someone tries to free the 
space by deleting the file. if the program writing it is still running, 
the file is gone but the space won't be freed until the program lets go 
of the file. lsof has a "deleted" indicator which can identify this.

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