Reboot after hibernate failed to restore to previous session. - users - Fedora Mailing-Lists

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

1991

1990

1989

1988

1987

1986

1985

1984

1983

1982

1981

1980

Reboot after hibernate failed to restore to previous session.

BT mouse sleeps too often

Crashes of tainted kernels

JD

Monday, 13 April 2015 Mon, 13 Apr '15

2:09 p.m.

Hi. Machine has 8GB ram, and 16GB swap. I hibernated and next day I powered up. My previous session was not restored; i.e., Logged in as normal login and had to start all the apps all over again.

Reply

Show replies by thread

Heinz Diehl

Monday, 13 April Mon, 13 Apr

3 p.m.

On 13.04.2015, jd1008 wrote:

I hibernated and next day I powered up. My previous session was not restored; i.e., Logged in as normal login and had to start all the apps all over again.

https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt

Reply

JD

9:32 p.m.

On 04/13/2015 02:00 PM, Heinz Diehl wrote:

On 13.04.2015, jd1008 wrote: > I hibernated and next day I powered up. My previous session was not > restored; i.e., Logged in as normal login and had to start all the > apps all over again. https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt

As root, I issued the incantation echo shutdown > /sys/power/disk; echo disk > /sys/power/state And rebooted. I did not get back the previous session. Next I will try echo platform > /sys/power/disk; echo disk > /sys/power/state

Reply

JD

9:57 p.m.

On 04/13/2015 08:32 PM, jd1008 wrote:

On 04/13/2015 02:00 PM, Heinz Diehl wrote: > On 13.04.2015, jd1008 wrote: >> I hibernated and next day I powered up. My previous session was not >> restored; i.e., Logged in as normal login and had to start all the >> apps all over again. > https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt As root, I issued the incantation echo shutdown > /sys/power/disk; echo disk > /sys/power/state And rebooted. I did not get back the previous session. Next I will try echo platform > /sys/power/disk; echo disk > /sys/power/state

Well, that did worse. Not only did it not let me resume the hibernation, but also I got this during reboot: [ 32.149600] EXT4-fs (sda3): re-mounted. Opts: (null) [ 32.232881] systemd-journald[368]: Received request to flush runtime journal from PID 1 [ 32.497403] Installing knfsd (copyright (C) 1996 okir(a)monad.swb.de). [ 32.765992] systemd-journald[368]: File /var/log/journal/d54673d37ad54447b2210def292ebe90/system.journal corrupted or uncleanly shut down, renaming and replacing. Also, I am losing files!!! Sorry for this long listing, but I think something is seriously wrong with the hibernation code. I am unable to file a bug, due to so called tainted kernel. # grep inode messages boot* messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098865 (uid=1008, gid=1008, mode=0100600, size=48) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098857 (uid=1008, gid=1008, mode=0100600, size=4096) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098855 (uid=1008, gid=1008, mode=0100600, size=4096) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098830 (uid=1008, gid=1008, mode=0100600, size=16384) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098853 (uid=1008, gid=1008, mode=0100600, size=18168) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098837 (uid=1008, gid=1008, mode=0100600, size=64) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943816 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942844 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098849 (uid=1008, gid=1008, mode=0100600, size=29832) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523934 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523933 (uid=1008, gid=1008, mode=0100600, size=8692) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390754 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522429 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522375 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62259569 (uid=1008, gid=1008, mode=0100644, size=264) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523066 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522206 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390757 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390752 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098865 (uid=1008, gid=1008, mode=0100600, size=48) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098857 (uid=1008, gid=1008, mode=0100600, size=4096) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098855 (uid=1008, gid=1008, mode=0100600, size=4096) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098830 (uid=1008, gid=1008, mode=0100600, size=16384) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098853 (uid=1008, gid=1008, mode=0100600, size=18168) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098837 (uid=1008, gid=1008, mode=0100600, size=64) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943816 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942844 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098849 (uid=1008, gid=1008, mode=0100600, size=29832) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523934 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523933 (uid=1008, gid=1008, mode=0100600, size=8692) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390754 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522429 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522375 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62259569 (uid=1008, gid=1008, mode=0100644, size=264) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523066 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522206 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390757 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390752 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098850 (uid=1008, gid=1008, mode=0100600, size=456) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942959 (uid=1008, gid=1008, mode=0100700, size=239927296) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40898790 (uid=0, gid=0, mode=0100755, size=81504) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897456 (uid=0, gid=0, mode=0100755, size=63048) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908353 (uid=0, gid=0, mode=0100755, size=185752) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916867 (uid=0, gid=0, mode=0100755, size=387672) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913008 (uid=0, gid=0, mode=0100755, size=111472) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40902843 (uid=0, gid=0, mode=0100755, size=65920) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40902383 (uid=0, gid=0, mode=0100755, size=89464) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920691 (uid=0, gid=0, mode=0100755, size=34504) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40914419 (uid=0, gid=0, mode=0100755, size=175976) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908632 (uid=0, gid=0, mode=0100755, size=338840) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40896553 (uid=0, gid=0, mode=0100755, size=96456) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911582 (uid=0, gid=0, mode=0100755, size=627928) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908837 (uid=0, gid=0, mode=0100755, size=115912) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40906510 (uid=0, gid=0, mode=0100755, size=2079656) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897387 (uid=0, gid=0, mode=0100755, size=71200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40906717 (uid=0, gid=0, mode=0100755, size=262264) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907720 (uid=0, gid=0, mode=0100755, size=220688) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40909908 (uid=0, gid=0, mode=0100755, size=525432) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907678 (uid=0, gid=0, mode=0100755, size=671392) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 41028132 (uid=0, gid=0, mode=0100755, size=33032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40909564 (uid=0, gid=0, mode=0100755, size=242224) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920718 (uid=0, gid=0, mode=0100755, size=664896) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920666 (uid=0, gid=0, mode=0100755, size=853632) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905199 (uid=0, gid=0, mode=0100755, size=2351000) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900617 (uid=0, gid=0, mode=0100755, size=370712) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920760 (uid=0, gid=0, mode=0100755, size=33024) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40910141 (uid=0, gid=0, mode=0100755, size=131800) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905494 (uid=0, gid=0, mode=0100755, size=274496) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912424 (uid=0, gid=0, mode=0100755, size=77240) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40903076 (uid=0, gid=0, mode=0100755, size=479136) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908015 (uid=0, gid=0, mode=0100755, size=100728) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40917345 (uid=0, gid=0, mode=0100755, size=133752) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40918978 (uid=0, gid=0, mode=0100755, size=89232) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897222 (uid=0, gid=0, mode=0100755, size=32992) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913910 (uid=0, gid=0, mode=0100755, size=247760) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913606 (uid=0, gid=0, mode=0100755, size=45328) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40909477 (uid=0, gid=0, mode=0100755, size=235504) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915090 (uid=0, gid=0, mode=0100755, size=77232) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920708 (uid=0, gid=0, mode=0100755, size=55888) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920680 (uid=0, gid=0, mode=0100755, size=32976) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911789 (uid=0, gid=0, mode=0100755, size=80976) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40898973 (uid=0, gid=0, mode=0100755, size=168096) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915837 (uid=0, gid=0, mode=0100755, size=121472) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915472 (uid=0, gid=0, mode=0100755, size=599032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916996 (uid=0, gid=0, mode=0100755, size=733760) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913952 (uid=0, gid=0, mode=0100755, size=223488) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913315 (uid=0, gid=0, mode=0100755, size=93512) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900754 (uid=0, gid=0, mode=0100755, size=168352) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920614 (uid=0, gid=0, mode=0100755, size=207928) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920431 (uid=0, gid=0, mode=0100755, size=125120) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171990 (uid=0, gid=0, mode=0100755, size=135632) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171989 (uid=0, gid=0, mode=0100755, size=1125576) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171988 (uid=0, gid=0, mode=0100755, size=49432) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171986 (uid=0, gid=0, mode=0100755, size=195040) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171985 (uid=0, gid=0, mode=0100755, size=70176) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171984 (uid=0, gid=0, mode=0100755, size=325408) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171983 (uid=0, gid=0, mode=0100755, size=22888) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171980 (uid=0, gid=0, mode=0100755, size=228048) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900713 (uid=0, gid=0, mode=0100755, size=37072) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171973 (uid=0, gid=0, mode=0100755, size=63296) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171971 (uid=0, gid=0, mode=0100755, size=60848) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52170845 (uid=0, gid=0, mode=0100755, size=221200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920818 (uid=0, gid=0, mode=0100755, size=117256) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916599 (uid=0, gid=0, mode=0100755, size=23536) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911632 (uid=0, gid=0, mode=0100755, size=165712) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907352 (uid=0, gid=0, mode=0100755, size=81944) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913640 (uid=0, gid=0, mode=0100755, size=990992) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171976 (uid=0, gid=0, mode=0100755, size=231256) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52170680 (uid=0, gid=0, mode=0100755, size=2070056) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916310 (uid=0, gid=0, mode=0100755, size=46336) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40914463 (uid=0, gid=0, mode=0100755, size=247264) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907777 (uid=0, gid=0, mode=0100755, size=883064) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920664 (uid=0, gid=0, mode=0100755, size=344384) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920611 (uid=0, gid=0, mode=0100755, size=200872) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920608 (uid=0, gid=0, mode=0100755, size=372392) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920602 (uid=0, gid=0, mode=0100755, size=522792) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920601 (uid=0, gid=0, mode=0100755, size=157032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40914170 (uid=0, gid=0, mode=0100755, size=791256) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52168456 (uid=0, gid=0, mode=0100755, size=123912) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907116 (uid=0, gid=0, mode=0100755, size=289576) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920663 (uid=0, gid=0, mode=0100755, size=36444072) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40904020 (uid=0, gid=0, mode=0100755, size=511104) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911869 (uid=0, gid=0, mode=0100755, size=36432) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912401 (uid=0, gid=0, mode=0100755, size=94536) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897806 (uid=0, gid=0, mode=0100755, size=14320) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915103 (uid=0, gid=0, mode=0100755, size=153648) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40895927 (uid=0, gid=0, mode=0100755, size=193720) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920771 (uid=0, gid=0, mode=0100755, size=58888) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905364 (uid=0, gid=0, mode=0100755, size=24808) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40896985 (uid=0, gid=0, mode=0100755, size=157168) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920768 (uid=0, gid=0, mode=0100755, size=319352) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920405 (uid=0, gid=0, mode=0100755, size=140624) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920764 (uid=0, gid=0, mode=0100755, size=35440) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40895414 (uid=0, gid=0, mode=0100755, size=47520) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913029 (uid=0, gid=0, mode=0100755, size=67376) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900038 (uid=0, gid=0, mode=0100755, size=19576) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40895981 (uid=0, gid=0, mode=0100755, size=333112) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 42992468 (uid=0, gid=0, mode=0100755, size=516712) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905209 (uid=0, gid=0, mode=0100755, size=227488) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905487 (uid=0, gid=0, mode=0100755, size=244824) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40906327 (uid=0, gid=0, mode=0100755, size=846008) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40902521 (uid=0, gid=0, mode=0100755, size=47424) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 41422841 (uid=0, gid=0, mode=0100755, size=163552) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40919332 (uid=0, gid=0, mode=0100755, size=25032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915114 (uid=0, gid=0, mode=0100755, size=7150024) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915112 (uid=0, gid=0, mode=0100755, size=773568) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900834 (uid=0, gid=0, mode=0100755, size=39744) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920694 (uid=0, gid=0, mode=0100755, size=114000) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 41422840 (uid=0, gid=0, mode=0100755, size=256704) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920699 (uid=0, gid=0, mode=0100755, size=271944) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40901166 (uid=0, gid=0, mode=0100755, size=438472) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920670 (uid=0, gid=0, mode=0100755, size=259992) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920657 (uid=0, gid=0, mode=0100755, size=4856688) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920655 (uid=0, gid=0, mode=0100755, size=816408) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920651 (uid=0, gid=0, mode=0100755, size=58672) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920645 (uid=0, gid=0, mode=0100755, size=1250040) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920644 (uid=0, gid=0, mode=0100755, size=642184) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920634 (uid=0, gid=0, mode=0100755, size=175984) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920633 (uid=0, gid=0, mode=0100755, size=61216) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40904342 (uid=0, gid=0, mode=0100755, size=52704) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916456 (uid=0, gid=0, mode=0100755, size=3045200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920678 (uid=0, gid=0, mode=0100755, size=552168) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912331 (uid=0, gid=0, mode=0100755, size=1491544) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098909 (uid=1008, gid=1008, mode=0100600, size=120) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098869 (uid=1008, gid=1008, mode=0100600, size=245) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943836 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942439 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098858 (uid=1008, gid=1008, mode=0100600, size=696) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523929 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523910 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390752 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390754 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390751 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098865 (uid=1008, gid=1008, mode=0100600, size=48) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098857 (uid=1008, gid=1008, mode=0100600, size=4096) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098855 (uid=1008, gid=1008, mode=0100600, size=4096) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098830 (uid=1008, gid=1008, mode=0100600, size=16384) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098853 (uid=1008, gid=1008, mode=0100600, size=18168) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098837 (uid=1008, gid=1008, mode=0100600, size=64) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943816 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942844 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 06:59:36 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098849 (uid=1008, gid=1008, mode=0100600, size=29832) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523934 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523933 (uid=1008, gid=1008, mode=0100600, size=8692) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390754 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522429 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522375 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62259569 (uid=1008, gid=1008, mode=0100644, size=264) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523066 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522206 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390757 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390752 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 13:00:10 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098850 (uid=1008, gid=1008, mode=0100600, size=456) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942959 (uid=1008, gid=1008, mode=0100700, size=239927296) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40898790 (uid=0, gid=0, mode=0100755, size=81504) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897456 (uid=0, gid=0, mode=0100755, size=63048) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908353 (uid=0, gid=0, mode=0100755, size=185752) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916867 (uid=0, gid=0, mode=0100755, size=387672) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913008 (uid=0, gid=0, mode=0100755, size=111472) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40902843 (uid=0, gid=0, mode=0100755, size=65920) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40902383 (uid=0, gid=0, mode=0100755, size=89464) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920691 (uid=0, gid=0, mode=0100755, size=34504) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40914419 (uid=0, gid=0, mode=0100755, size=175976) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908632 (uid=0, gid=0, mode=0100755, size=338840) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40896553 (uid=0, gid=0, mode=0100755, size=96456) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911582 (uid=0, gid=0, mode=0100755, size=627928) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908837 (uid=0, gid=0, mode=0100755, size=115912) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40906510 (uid=0, gid=0, mode=0100755, size=2079656) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897387 (uid=0, gid=0, mode=0100755, size=71200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40906717 (uid=0, gid=0, mode=0100755, size=262264) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907720 (uid=0, gid=0, mode=0100755, size=220688) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40909908 (uid=0, gid=0, mode=0100755, size=525432) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907678 (uid=0, gid=0, mode=0100755, size=671392) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 41028132 (uid=0, gid=0, mode=0100755, size=33032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40909564 (uid=0, gid=0, mode=0100755, size=242224) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920718 (uid=0, gid=0, mode=0100755, size=664896) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920666 (uid=0, gid=0, mode=0100755, size=853632) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905199 (uid=0, gid=0, mode=0100755, size=2351000) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900617 (uid=0, gid=0, mode=0100755, size=370712) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920760 (uid=0, gid=0, mode=0100755, size=33024) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40910141 (uid=0, gid=0, mode=0100755, size=131800) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905494 (uid=0, gid=0, mode=0100755, size=274496) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912424 (uid=0, gid=0, mode=0100755, size=77240) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40903076 (uid=0, gid=0, mode=0100755, size=479136) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40908015 (uid=0, gid=0, mode=0100755, size=100728) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40917345 (uid=0, gid=0, mode=0100755, size=133752) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40918978 (uid=0, gid=0, mode=0100755, size=89232) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897222 (uid=0, gid=0, mode=0100755, size=32992) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913910 (uid=0, gid=0, mode=0100755, size=247760) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913606 (uid=0, gid=0, mode=0100755, size=45328) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40909477 (uid=0, gid=0, mode=0100755, size=235504) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915090 (uid=0, gid=0, mode=0100755, size=77232) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920708 (uid=0, gid=0, mode=0100755, size=55888) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920680 (uid=0, gid=0, mode=0100755, size=32976) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911789 (uid=0, gid=0, mode=0100755, size=80976) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40898973 (uid=0, gid=0, mode=0100755, size=168096) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915837 (uid=0, gid=0, mode=0100755, size=121472) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915472 (uid=0, gid=0, mode=0100755, size=599032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916996 (uid=0, gid=0, mode=0100755, size=733760) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913952 (uid=0, gid=0, mode=0100755, size=223488) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913315 (uid=0, gid=0, mode=0100755, size=93512) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900754 (uid=0, gid=0, mode=0100755, size=168352) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920614 (uid=0, gid=0, mode=0100755, size=207928) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920431 (uid=0, gid=0, mode=0100755, size=125120) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171990 (uid=0, gid=0, mode=0100755, size=135632) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171989 (uid=0, gid=0, mode=0100755, size=1125576) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171988 (uid=0, gid=0, mode=0100755, size=49432) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171986 (uid=0, gid=0, mode=0100755, size=195040) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171985 (uid=0, gid=0, mode=0100755, size=70176) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171984 (uid=0, gid=0, mode=0100755, size=325408) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171983 (uid=0, gid=0, mode=0100755, size=22888) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171980 (uid=0, gid=0, mode=0100755, size=228048) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900713 (uid=0, gid=0, mode=0100755, size=37072) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171973 (uid=0, gid=0, mode=0100755, size=63296) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171971 (uid=0, gid=0, mode=0100755, size=60848) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52170845 (uid=0, gid=0, mode=0100755, size=221200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920818 (uid=0, gid=0, mode=0100755, size=117256) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916599 (uid=0, gid=0, mode=0100755, size=23536) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911632 (uid=0, gid=0, mode=0100755, size=165712) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907352 (uid=0, gid=0, mode=0100755, size=81944) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913640 (uid=0, gid=0, mode=0100755, size=990992) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52171976 (uid=0, gid=0, mode=0100755, size=231256) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52170680 (uid=0, gid=0, mode=0100755, size=2070056) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916310 (uid=0, gid=0, mode=0100755, size=46336) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40914463 (uid=0, gid=0, mode=0100755, size=247264) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907777 (uid=0, gid=0, mode=0100755, size=883064) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920664 (uid=0, gid=0, mode=0100755, size=344384) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920611 (uid=0, gid=0, mode=0100755, size=200872) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920608 (uid=0, gid=0, mode=0100755, size=372392) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920602 (uid=0, gid=0, mode=0100755, size=522792) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920601 (uid=0, gid=0, mode=0100755, size=157032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40914170 (uid=0, gid=0, mode=0100755, size=791256) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 52168456 (uid=0, gid=0, mode=0100755, size=123912) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40907116 (uid=0, gid=0, mode=0100755, size=289576) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920663 (uid=0, gid=0, mode=0100755, size=36444072) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40904020 (uid=0, gid=0, mode=0100755, size=511104) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40911869 (uid=0, gid=0, mode=0100755, size=36432) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912401 (uid=0, gid=0, mode=0100755, size=94536) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40897806 (uid=0, gid=0, mode=0100755, size=14320) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915103 (uid=0, gid=0, mode=0100755, size=153648) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40895927 (uid=0, gid=0, mode=0100755, size=193720) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920771 (uid=0, gid=0, mode=0100755, size=58888) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905364 (uid=0, gid=0, mode=0100755, size=24808) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40896985 (uid=0, gid=0, mode=0100755, size=157168) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920768 (uid=0, gid=0, mode=0100755, size=319352) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920405 (uid=0, gid=0, mode=0100755, size=140624) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920764 (uid=0, gid=0, mode=0100755, size=35440) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40895414 (uid=0, gid=0, mode=0100755, size=47520) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40913029 (uid=0, gid=0, mode=0100755, size=67376) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900038 (uid=0, gid=0, mode=0100755, size=19576) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40895981 (uid=0, gid=0, mode=0100755, size=333112) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 42992468 (uid=0, gid=0, mode=0100755, size=516712) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905209 (uid=0, gid=0, mode=0100755, size=227488) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40905487 (uid=0, gid=0, mode=0100755, size=244824) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40906327 (uid=0, gid=0, mode=0100755, size=846008) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40902521 (uid=0, gid=0, mode=0100755, size=47424) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 41422841 (uid=0, gid=0, mode=0100755, size=163552) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40919332 (uid=0, gid=0, mode=0100755, size=25032) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915114 (uid=0, gid=0, mode=0100755, size=7150024) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40915112 (uid=0, gid=0, mode=0100755, size=773568) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40900834 (uid=0, gid=0, mode=0100755, size=39744) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920694 (uid=0, gid=0, mode=0100755, size=114000) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 41422840 (uid=0, gid=0, mode=0100755, size=256704) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920699 (uid=0, gid=0, mode=0100755, size=271944) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40901166 (uid=0, gid=0, mode=0100755, size=438472) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920670 (uid=0, gid=0, mode=0100755, size=259992) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920657 (uid=0, gid=0, mode=0100755, size=4856688) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920655 (uid=0, gid=0, mode=0100755, size=816408) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920651 (uid=0, gid=0, mode=0100755, size=58672) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920645 (uid=0, gid=0, mode=0100755, size=1250040) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920644 (uid=0, gid=0, mode=0100755, size=642184) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920634 (uid=0, gid=0, mode=0100755, size=175984) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920633 (uid=0, gid=0, mode=0100755, size=61216) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40904342 (uid=0, gid=0, mode=0100755, size=52704) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916456 (uid=0, gid=0, mode=0100755, size=3045200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920678 (uid=0, gid=0, mode=0100755, size=552168) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912331 (uid=0, gid=0, mode=0100755, size=1491544) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098909 (uid=1008, gid=1008, mode=0100600, size=120) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098869 (uid=1008, gid=1008, mode=0100600, size=245) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943836 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942439 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098858 (uid=1008, gid=1008, mode=0100600, size=696) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943687 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943670 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098970 (uid=1008, gid=1008, mode=0100600, size=1699840) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098946 (uid=1008, gid=1008, mode=0100600, size=2109440) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098926 (uid=1008, gid=1008, mode=0100600, size=120) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098922 (uid=1008, gid=1008, mode=0100600, size=284) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523929 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920644 (uid=0, gid=0, mode=0100755, size=642184) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920634 (uid=0, gid=0, mode=0100755, size=175984) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920633 (uid=0, gid=0, mode=0100755, size=61216) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40904342 (uid=0, gid=0, mode=0100755, size=52704) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40916456 (uid=0, gid=0, mode=0100755, size=3045200) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40920678 (uid=0, gid=0, mode=0100755, size=552168) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 40912331 (uid=0, gid=0, mode=0100755, size=1491544) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098909 (uid=1008, gid=1008, mode=0100600, size=120) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098869 (uid=1008, gid=1008, mode=0100600, size=245) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943836 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14942439 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 14:21:35 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098858 (uid=1008, gid=1008, mode=0100600, size=696) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943687 (uid=1008, gid=1008, mode=0100600, size=32768) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 14943670 (uid=1008, gid=1008, mode=0100600, size=33288) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098970 (uid=1008, gid=1008, mode=0100600, size=1699840) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098946 (uid=1008, gid=1008, mode=0100600, size=2109440) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098926 (uid=1008, gid=1008, mode=0100600, size=120) messages:Apr 13 14:37:13 localhost systemd-fsck: linuxBoot: Clearing orphaned inode 56098922 (uid=1008, gid=1008, mode=0100600, size=284) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523929 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62523910 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390752 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390754 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390751 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:22:07 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522375 (uid=1008, gid=1008, mode=0100644, size=32768) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62522125 (uid=1008, gid=1008, mode=0100600, size=70436) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390756 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390753 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390755 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390751 (uid=1008, gid=1008, mode=0100644, size=25708) messages:Apr 13 20:38:02 localhost systemd-fsck: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708) boot.log:[ 7.874815] systemd-fsck[269]: linuxBoot: Clearing orphaned inode 14943687 (uid=1008, gid=1008, mode=0100600, size=32768) boot.log:[ 7.875124] systemd-fsck[269]: linuxBoot: Clearing orphaned inode 14943670 (uid=1008, gid=1008, mode=0100600, size=33288) boot.log:[ 7.897111] systemd-fsck[269]: linuxBoot: Clearing orphaned inode 56098970 (uid=1008, gid=1008, mode=0100600, size=1699840) boot.log:[ 7.897515] systemd-fsck[269]: linuxBoot: Clearing orphaned inode 56098946 (uid=1008, gid=1008, mode=0100600, size=2109440) boot.log:[ 7.897845] systemd-fsck[269]: linuxBoot: Clearing orphaned inode 56098926 (uid=1008, gid=1008, mode=0100600, size=120) boot.log:[ 7.898064] systemd-fsck[269]: linuxBoot: Clearing orphaned inode 56098922 (uid=1008, gid=1008, mode=0100600, size=284) boot.log:[ 57.156781] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62522375 (uid=1008, gid=1008, mode=0100644, size=32768) boot.log:[ 57.157510] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62522125 (uid=1008, gid=1008, mode=0100600, size=70436) boot.log:[ 57.173467] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62390756 (uid=1008, gid=1008, mode=0100644, size=25708) boot.log:[ 57.173760] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62390753 (uid=1008, gid=1008, mode=0100644, size=25708) boot.log:[ 57.173945] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62390755 (uid=1008, gid=1008, mode=0100644, size=25708) boot.log:[ 57.174156] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62390751 (uid=1008, gid=1008, mode=0100644, size=25708) boot.log:[ 57.174629] systemd-fsck[619]: /dev/sdb3: Clearing orphaned inode 62390671 (uid=1008, gid=1008, mode=0100644, size=25708)

Reply

Heinz Diehl

Tuesday, 14 April Tue, 14 Apr

1:44 a.m.

On 14.04.2015, jd1008 wrote:

Also, I am losing files!!! Sorry for this long listing, but I think something is seriously wrong with the hibernation code.

Does S2R work for you? Anyway, I have debugged some S2D problems in the last months, and my gut feel says you're most probably right. The machines that struggled to wake up properly from S2D hibernated/resumed all flawlessly running Win7. And of course your fs gets corrupted when your machine can't properly restore the image from disk. In case you want to try further: my own tests point all somehow to the SMP kernel code. So does your system resume properly with "maxcpus=1" passed to the kernel? See also https://bugzilla.kernel.org/show_bug.cgi?id=95231 Doesn't look like anybody cares..

Reply

poma

4:44 a.m.

On 14.04.2015 08:44, Heinz Diehl wrote:

On 14.04.2015, jd1008 wrote: > Also, I am losing files!!! Sorry for this long listing, but I think > something is seriously wrong with the hibernation code. Does S2R work for you? Anyway, I have debugged some S2D problems in the last months, and my gut feel says you're most probably right. The machines that struggled to wake up properly from S2D hibernated/resumed all flawlessly running Win7. And of course your fs gets corrupted when your machine can't properly restore the image from disk. In case you want to try further: my own tests point all somehow to the SMP kernel code. So does your system resume properly with "maxcpus=1" passed to the kernel? See also https://bugzilla.kernel.org/show_bug.cgi?id=95231

Bug 95231 - System fails to suspend from hibernation https://bugzilla.kernel.org/show_bug.cgi?id=95231 Heinz, can your machine *suspend* from hibernation? :)

Doesn't look like anybody cares..

Both Suspend to RAM & Disk functionality are highly dependent on hardware in use. Nice to see that you discuss it here, but if you really want to solve it, at least to try: http://vger.kernel.org/vger-lists.html

Reply

JD

10:26 a.m.

On 04/14/2015 12:44 AM, Heinz Diehl wrote:

On 14.04.2015, jd1008 wrote: > Also, I am losing files!!! Sorry for this long listing, but I think > something is seriously wrong with the hibernation code. Does S2R work for you? Anyway, I have debugged some S2D problems in the last months, and my gut feel says you're most probably right. The machines that struggled to wake up properly from S2D hibernated/resumed all flawlessly running Win7. And of course your fs gets corrupted when your machine can't properly restore the image from disk. In case you want to try further: my own tests point all somehow to the SMP kernel code. So does your system resume properly with "maxcpus=1" passed to the kernel? See also https://bugzilla.kernel.org/show_bug.cgi?id=95231 Doesn't look like anybody cares..

So, use maxcpus=1 during first boot and 2nd boot?

Reply

Heinz Diehl

2:39 p.m.

On 14.04.2015, jd1008 wrote:

So, use maxcpus=1 during first boot and 2nd boot?

The machine is a quadcore XEON, reducing it to a single-core is not really something I want.

Reply

John Schmitt

3:57 p.m.

Using maxcpus=1 in your grub command line is an ugly work-around, I agree. However, if your machine is waking up from sleep or hibernate, using maxcpus=1 on your grub command line is going to apply only until your frozen system image (that is, the image of your running kernel that was running on all CPUs) is loaded and run. That is my understanding of the mechanism. The bug appears to be in the process of unfreezing your system image with multiple processors. On Tue, Apr 14, 2015 at 12:39 PM, Heinz Diehl <htd+ml(a)fritha.org> wrote:

On 14.04.2015, jd1008 wrote: > So, use maxcpus=1 during first boot and 2nd boot? The machine is a quadcore XEON, reducing it to a single-core is not really something I want. -- users mailing list users(a)lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org

Reply

Heinz Diehl

4:18 p.m.

On 14.04.2015, John Schmitt wrote:

Using maxcpus=1 in your grub command line is an ugly work-around, I agree.

It simply doesn't work..

However, if your machine is waking up from sleep or hibernate, using maxcpus=1 on your grub command line is going to apply only until your frozen system image (that is, the image of your running kernel that was running on all CPUs) is loaded and run. That is my understanding of the mechanism.

..exactly because of what you describe here. You're completely right.

The bug appears to be in the process of unfreezing your system image with multiple processors.

Resuming from S2D fails about 3-4 times out of 10, so it could be a race condition somewhere in the SMP or timer-related code, which I'm not at all familiar with. There are quite a few bug reports out there reporting different resume hangs which also resolve by passing maxcpus=1 to the kernel. Didn't try with sched-clock ticks on (CONFIG_NO_HZ=n), and I'm afraid I won't debug this issue any further, since every failure to resume causes fs corruption. On that account, a "git bisect" is not really feasible either. So most probably I'll leave it at that and have to accept that S2D does not work properly here (which is really annoying when you have opened a lot of papers and documents while writing e.g. an article and would like to continue your work where you left the evening before..).

Reply

Rick Stevens

5:30 p.m.

On 04/14/2015 02:18 PM, Heinz Diehl wrote:

On 14.04.2015, John Schmitt wrote: > Using maxcpus=1 in your grub command line is an ugly work-around, I agree. It simply doesn't work.. > However, if your machine is waking up from sleep or hibernate, using > maxcpus=1 on your grub command line is going to apply only until your > frozen system image (that is, the image of your running kernel that was > running on all CPUs) is loaded and run. That is my understanding of the > mechanism. ..exactly because of what you describe here. You're completely right. > The bug appears to be in the process of unfreezing your system > image with multiple processors. Resuming from S2D fails about 3-4 times out of 10, so it could be a race condition somewhere in the SMP or timer-related code, which I'm not at all familiar with. There are quite a few bug reports out there reporting different resume hangs which also resolve by passing maxcpus=1 to the kernel. Didn't try with sched-clock ticks on (CONFIG_NO_HZ=n), and I'm afraid I won't debug this issue any further, since every failure to resume causes fs corruption. On that account, a "git bisect" is not really feasible either. So most probably I'll leave it at that and have to accept that S2D does not work properly here (which is really annoying when you have opened a lot of papers and documents while writing e.g. an article and would like to continue your work where you left the evening before..).

Can you check and see what your actual swap space is? The new Fedora seems to set up a swap space that's 50% of your memory space. If that's what you've got, then a suspend to disk is going to die as it uses swap to save an image of your memory and all you have is half the space you need. Bad news. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Millihelen (n): The amount of beauty required to launch one ship. - ----------------------------------------------------------------------

Reply

JD

6:38 p.m.

Thank you John. Is anyone working on this bug? I did not have this problem in 3.17 and prior. On 04/14/2015 02:57 PM, John Schmitt wrote:

Using maxcpus=1 in your grub command line is an ugly work-around, I agree. However, if your machine is waking up from sleep or hibernate, using maxcpus=1 on your grub command line is going to apply only until your frozen system image (that is, the image of your running kernel that was running on all CPUs) is loaded and run. That is my understanding of the mechanism. The bug appears to be in the process of unfreezing your system image with multiple processors. On Tue, Apr 14, 2015 at 12:39 PM, Heinz Diehl <htd+ml(a)fritha.org <mailto:htd+ml@fritha.org>> wrote: On 14.04.2015, jd1008 wrote: > So, use maxcpus=1 during first boot and 2nd boot? The machine is a quadcore XEON, reducing it to a single-core is not really something I want. -- users mailing list users(a)lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org

Reply

JD

6:43 p.m.

On 04/14/2015 04:30 PM, Rick Stevens wrote:

On 04/14/2015 02:18 PM, Heinz Diehl wrote: > On 14.04.2015, John Schmitt wrote: > >> Using maxcpus=1 in your grub command line is an ugly work-around, I >> agree. > > It simply doesn't work.. > >> However, if your machine is waking up from sleep or hibernate, using >> maxcpus=1 on your grub command line is going to apply only until your >> frozen system image (that is, the image of your running kernel that was >> running on all CPUs) is loaded and run. That is my understanding of >> the >> mechanism. > > ..exactly because of what you describe here. You're completely right. > >> The bug appears to be in the process of unfreezing your system >> image with multiple processors. > > Resuming from S2D fails about 3-4 times out of 10, so it could be a race > condition somewhere in the SMP or timer-related code, which I'm not > at all > familiar with. There are quite a few bug reports out there reporting > different > resume hangs which also resolve by passing maxcpus=1 to the kernel. > Didn't try > with sched-clock ticks on (CONFIG_NO_HZ=n), and I'm afraid I won't > debug this > issue any further, since every failure to resume causes fs > corruption. On that > account, a "git bisect" is not really feasible either. So most > probably I'll > leave it at that and have to accept that S2D does not work properly > here (which > is really annoying when you have opened a lot of papers and documents > while > writing e.g. an article and would like to continue your work where > you left > the evening before..). Can you check and see what your actual swap space is? The new Fedora seems to set up a swap space that's 50% of your memory space. If that's what you've got, then a suspend to disk is going to die as it uses swap to save an image of your memory and all you have is half the space you need. Bad news.

I have 16GB swap, and 8GB RAM. So, what you suspect is not the case.

Reply

Joe Zeff

7:07 p.m.

On 04/14/2015 04:43 PM, jd1008 wrote:

I have 16GB swap, and 8GB RAM. So, what you suspect is not the case.

It probably wouldn't hurt to check how much of your RAM and swap are available: free -h It's probably not an issue, and you needn't post the results unless there's something odd about them, but there's always the chance that you'll find something new.

Reply

JD

7:31 p.m.

On 04/14/2015 06:07 PM, Joe Zeff wrote:

On 04/14/2015 04:43 PM, jd1008 wrote: > > I have 16GB swap, and 8GB RAM. > > So, what you suspect is not the case. It probably wouldn't hurt to check how much of your RAM and swap are available: free -h It's probably not an issue, and you needn't post the results unless there's something odd about them, but there's always the chance that you'll find something new.

$ free -h total used free shared buff/cache available Mem: 7.8G 1.6G 5.2G 9.3M 950M 5.9G

Reply

Joe Zeff

7:36 p.m.

On 04/14/2015 05:31 PM, jd1008 wrote:

On 04/14/2015 06:07 PM, Joe Zeff wrote: > On 04/14/2015 04:43 PM, jd1008 wrote: >> >> I have 16GB swap, and 8GB RAM. >> >> So, what you suspect is not the case. > > It probably wouldn't hurt to check how much of your RAM and swap are > available: > > free -h > > It's probably not an issue, and you needn't post the results unless > there's something odd about them, but there's always the chance that > you'll find something new. $ free -h total used free shared buff/cache available Mem: 7.8G 1.6G 5.2G 9.3M 950M 5.9G

The last line of the output is dedicated to Swap; is there any reason you left it off?

Reply

JD

7:59 p.m.

On 04/14/2015 06:36 PM, Joe Zeff wrote:

On 04/14/2015 05:31 PM, jd1008 wrote: > > > On 04/14/2015 06:07 PM, Joe Zeff wrote: >> On 04/14/2015 04:43 PM, jd1008 wrote: >>> >>> I have 16GB swap, and 8GB RAM. >>> >>> So, what you suspect is not the case. >> >> It probably wouldn't hurt to check how much of your RAM and swap are >> available: >> >> free -h >> >> It's probably not an issue, and you needn't post the results unless >> there's something odd about them, but there's always the chance that >> you'll find something new. > $ free -h > total used free shared buff/cache > available > Mem: 7.8G 1.6G 5.2G 9.3M 950M 5.9G > The last line of the output is dedicated to Swap; is there any reason you left it off?

I thought I had grabbed it. :) $ free -h total used free shared buff/cache available Mem: 7.8G 1.6G 5.2G 9.3M 950M 5.9G Swap: 15G 0B 15G

Reply

3299

days inactive

3301

days old

users@lists.fedoraproject.org

Manage subscription

16 comments

6 participants

tags (0)

participants (6)

Heinz Diehl
JD
Joe Zeff
John Schmitt
poma
Rick Stevens