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

Groups > linux.debian.user > #212266

Re: where is my disk space

Show all headers | View raw

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

On Mon, 5 Aug 2019, Long Wind wrote:

> Thank David!it seems it's bug of X
>  tail -100 .local/share/xorg/Xorg.1.log

To me it looks like the log below is telling you that your power key
was either being held down or stuck in that position.

That is all.

>
> [ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.465] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
> [ 21261.466] (EE) libinput bug: Key count for KEY_POWER reached abnormal values
>
> ......
>
>    On Monday, August 5, 2019, 12:07:30 PM GMT+8, David Wright <deblis@lionunicorn.co.uk> wrote:
>
> On Sun 04 Aug 2019 at 20:56:01 (+0000), Long Wind wrote:
>>   the file is more than 3 G, i can't read it with nanoi have 3 G memory, no swap
>> why don't X print important error msg to terminals?i can't see any of them
>>
>> is it a bug of X?? my problem isn't solved,
>> ls .local/share/xorg/ -ltotal 3770920
>> -rw-r--r-- 1 zhou zhou      32654 Aug  5 04:40 Xorg.0.log
>> -rw-r--r-- 1 zhou zhou      39127 Aug  5 04:38 Xorg.0.log.old
>> -rw-r--r-- 1 zhou zhou 3861332996 Aug  4 22:16 Xorg.1.log
>
> You reported Sun, 4 Aug 2019 10:43:06 +0000 (UTC) that:
>     Xorg.0.log.old
>     it's more than 3.9G
>     it seems keeping growing
>     clearly i don't need it,
>     i delete it
>
> Since then it would appear that you've run X twice, so any Xorg.0.log*
> files from that era have long gone. But now you've sprung the file
> Xorg.1.log on us, which looks as though you've run 2 X servers at the
> same time, just on the one occasion, the evening of 2019-08-04.
> (But I don't know whether you timezone is really UTC.)
>
> I'm guessing that whatever made Xorg.0.log huge also had the same
> effect on Xorg.1.log so it would be useful to look at that file
> before you delete it.
> $ tail -100 ~/.local/share/xorg/Xorg.1.log
> will show you the last 100 lines which might be enough. If not,
> you can sample the file with
> $ less ~/.local/share/xorg/Xorg.1.log
> and then by typing  50p  70p  90p  95p  which will move to 50%,
> 70%, 90%, 95% of the way through the file, faster than scrolling.
>
> It's quite possible that the files' sizes were entirely caused by
> your running two X servers at the same time. The log may tell
> you what the issue was, and it would be useful to post it
> (the issue, and perhaps a few lines from the log) here.
>
>> below is Xorg.0.log:
>
> [snipped]
>
>> On Sunday, August 4, 2019, 11:37:07 PM GMT+8, David Wright <deblis@lionunicorn.co.uk> wrote: 
>>   On Sun 04 Aug 2019 at 13:06:07 (+0200), Pascal Hambourg wrote:
>>> Le 04/08/2019 à 12:43, Long Wind a écrit :
>>>> i think i find out
>>>> it's in ~/.local it's Xorg.0.log.old
>>>> it's more than 3.9G
>>>> it seems keeping growing
>>>> clearly i don't need it, i delete it
>>>> it should solve my problem
>>>
>>> What about Xorg.0.log ?
>>> If these files keep growing up to such a size, then it means that they
>>> are flooded by repeated messages. Before deleting them, you should
>>> read their contents and fix the underlying issue or they will fill
>>> your disk space again and again.
>>
>> Agreed. It would be odd if Xorg.0.log.old is still growing because
>> that's the log from the previous session. So I'd assume it's
>> probably Xorg.0.log that's growing, and Xorg.0.log.old is just
>> sitting there.
>>
>> Bear in mind that if you delete a file that is still held open by
>> some process, you won't reclaim the free space until that process
>> closes the file. So until that time, du will no longer see its
>> space as used but df will not see it as available either.
>
> Cheers,
> David.
>
>

-- 
  The day will come              |  Last words, August Spies (1855--1887).
  When our silence will be       |  Hanged, by the U.S. state of Illinois,
  More powerful than             |  alongside fellow journalists
  The voices you strangle today  |  Adolf Fischer and Albert Parsons.

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

Thread

where is my disk space Long Wind <longwind2@yahoo.com> - 2019-08-04 10:40 +0200
  Re: where is my disk space <tomas@tuxteam.de> - 2019-08-04 11:30 +0200
    Re: where is my disk space Long Wind <longwind2@yahoo.com> - 2019-08-04 11:40 +0200
      Re: where is my disk space Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-04 11:50 +0200
        Re: where is my disk space Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-04 12:00 +0200
          Re: where is my disk space Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-04 12:30 +0200
      Re: where is my disk space "Thomas Schmitt" <scdbackup@gmx.net> - 2019-08-04 12:00 +0200
      Re: where is my disk space <tomas@tuxteam.de> - 2019-08-04 12:30 +0200
        Re: where is my disk space Long Wind <longwind2@yahoo.com> - 2019-08-04 12:50 +0200
          Re: where is my disk space Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-08-04 13:10 +0200
            Re: where is my disk space David Wright <deblis@lionunicorn.co.uk> - 2019-08-04 17:40 +0200
              Re: where is my disk space Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-08-04 23:40 +0200
              Re: where is my disk space David Wright <deblis@lionunicorn.co.uk> - 2019-08-05 06:10 +0200
                Re: where is my disk space Long Wind <longwind2@yahoo.com> - 2019-08-05 06:20 +0200
                Re: where is my disk space davidson <davidson@freevolt.org> - 2019-08-05 18:10 +0200
                Re: where is my disk space Curt <curty@free.fr> - 2019-08-05 18:40 +0200
                Re: where is my disk space David Wright <deblis@lionunicorn.co.uk> - 2019-08-06 02:10 +0200
                Re: where is my disk space Long Wind <longwind2@yahoo.com> - 2019-08-12 10:00 +0200
                Re: where is my disk space David Wright <deblis@lionunicorn.co.uk> - 2019-08-12 16:50 +0200
                Re: where is my disk space Long Wind <longwind2@yahoo.com> - 2019-08-13 01:00 +0200
    Re: where is my disk space Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-04 11:40 +0200
  Re: where is my disk space Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-04 12:00 +0200

csiph-web