Page 1 of 1

Login loop, deleting files does not help, memory usage at 100%

Posted: Wed Jul 01, 2020 1:05 am
by derjens
Dear gurus,

I ran into a wierd problem. Sequence of events:

- Firefox crashed and rendered the system unresponsive, I had to use the reset button :shock:
- System started normally, I logged on, but there seemed to be 0 bytes free memory on my harddisk
- I restarted the system to try and get rid of the obvious error
- Since then, I cannot log on. When I enter my password, the logon screen disappears and reappears seconds later.
- startx gives me these messages:

[ 36.539386] encryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28]
[ 36.539420] encryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28]
[ 36.539440] Error writing headers; rc = [-28]
[ 36.540301] encryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28]
[ 36.540331] encryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28]
[ 36.540353] Error writing headers; rc = [-28]
xauth: error in locking authority file /home/username/.Xauthority
[ 36.541209] encryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28]
[ 36.541242] encryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28]
[ 36.541263] Error writing headers; rc = [-28]
[ 36.542095] encryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28]
[ 36.542126] encryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28]
[ 36.542146] Error writing headers; rc = [-28]
xauth: error in locking authority file /home/username/.Xauthority

(EE)
Fatal server error:
(EE) Could not write pid to lock file in /tmp/.tX1-lock
(EE)
(EE)
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
[ 51.545105] encryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28]
[ 51.545139] encryptfs_write_metadata: Error writing metadata out to lower file; rc = [-28]
[ 51.545159] Error writing headers; rc = [-28]
xauth: error in locking authority file /home/username/.Xauthority

I read several posts here about the reasons for a login loop and found out that df -h shows:
/dev/sda1 79G 75G 0 100%

So I deleted some larger files from my home directory, but that does not seem to change anything. Usage is still at 100%. What am I doing wrong?

Cheers
derjens

Re: Login loop, deleting files does not help, memory usage at 100%

Posted: Wed Jul 01, 2020 1:28 am
by Kadaitcha Man
derjens wrote:
Wed Jul 01, 2020 1:05 am

Code: Select all

[ 36.539386] encryptfs_write_metadata_to_contents: Error attempting to write header information to lower file; rc = [-28]
Backup your important files and prepare for disaster.

Re: Login loop, deleting files does not help, memory usage at 100%

Posted: Wed Jul 01, 2020 1:47 am
by all41
see this thread regarding login loop
viewtopic.php?p=1769597#p1769597
maybe karlchen's solution will work for you. It has for many

Re: Login loop, deleting files does not help, memory usage at 100%

Posted: Wed Jul 01, 2020 2:58 am
by derjens
Dear all41:

I already checked karlchen's solution and filesystem is at 100% indeed.

My question is: Why is it at 100% when size is 79GB and memory used ist 75GB? And why is it still at 100% after I deleted files from my home directory?

Maybe an error concerning encryption?

Cheers again
derjens

Re: Login loop, deleting files does not help, memory usage at 100%

Posted: Wed Jul 01, 2020 3:23 am
by rene
derjens wrote:
Wed Jul 01, 2020 2:58 am
My question is: Why is it at 100% when size is 79GB and memory used ist 75GB? And why is it still at 100% after I deleted files from my home directory?
Because (79 - 75) * 100 / 79 is just about the 5% of free-space that is by default reserved for the root user lest also he or she would be kept from freeing up enough space to fix things. Also see e.g. viewtopic.php?p=1364606#p1364606 while substituting for the correct root-fs device in your case if you don't manage to free up enough without the GUI active.

In which sense also: note that you rather than logging in graphically can use Ctrl-Alt-F1 and login on a text-console to free up space from a terminal. exit to log out again there, Ctrl-Alt-F7 back to the graphical login.