> On Jan 16, 2018, at 2:13 PM, markus.suva...@gmail.com wrote: > > >>> I don't have any partitios available but I can give up >>> swap and format that partition to ext4 and give a try. > > This time cache partition file system is ext4. Shortened version of > journalctl: > https://drive.google.com/file/d/1GTc3ZxnILxIbyroN_mlbeLs72O66YQ_y/view?usp=shari > ng > > It seems that I can reproduce this quite easily. I just log out gnome session.
Thanks for this. From your journalctl excerpt: … tammi 16 20:31:45 z600.station.com systemd[3023]: Received SIGRTMIN+24 from PID 3448 (kill). tammi 16 20:31:45 z600.station.com tracker-miner-fs.desktop[2885]: OK tammi 16 20:31:45 z600.station.com gdm-password][2403]: pam_unix(gdm-password:session): session closed for user masu tammi 16 20:31:45 z600.station.com systemd[1]: Stopped User Manager for UID 0. tammi 16 20:31:45 z600.station.com systemd[1]: Removed slice User Slice of root. tammi 16 20:31:45 z600.station.com kernel: afs: disk cache read error in CacheItems slot 98197 off 7855780/8000020 code -4/80 tammi 16 20:31:45 z600.station.com kernel: openafs: afs_InvalidateAllSegments tdc count <panic> … it seems quite likely that SIGRTMIN+24 is the signal that interrupted the OpenAFS disk cache read (code -4 is EINTR). I’ve seen cases before where user-defined signals have caused trouble for OpenAFS, but I can’t rememeber the details at the moment, nor what was done to solve the problem. But I imagine that your environment requires this signal, and thus OpenAFS may need mods to cope with it. — Mark Vitale OpenAFS release team
