[OpenAFS-devel] 1.8.11pre1 client hanging on Linux 6.7

[Cheyenne Wills]

Typo in the instructions, sysrq_trigger -> sysrq-trigger, so the command
is:

  `echo t | sudo tee /proc/sysrq-trigger`

The output will be in dmesg=20

Having said that, I've not been able to duplicate the problem.  I
however notice a short hang when I lost contact with an afs server
that was not specified within the CellServDB.


[ 2721.299326] afs: Lost contact with volume location server
xxx.xx.xxx.xx in cell xxxxx.net (code -1)
[ 2722.629824] afs: volume location server xxx.xx.xxx.xx in
cell xxxxx.net is back up (code 0)

I'm running a vanilla 6.7 kernel with openafs-stable-1_8_x (which is
1.8.11pre1).


--=20
Cheyenne Wills
cwills@sinenomine.net



On Sun, 21 Jan 2024 11:36:33 -0800
"Benjamin Kaduk" <kaduk@mit.edu> wrote:
> On Sat, Jan 20, 2024 at 06:37:20PM +0100, Michael La=C3=9F wrote:
> > Hi all,
> >=20
> > I am testing the OpenAFS client version 1.8.11pre1 on Linux 6.7 and
> > cannot get it to work. The dynroot in /afs is filled but as soon as
> > I
>=20
> (Obligatory note that 1.8.11pre1 is still in the process of being
> published, though I do not expect the contents of it to change.)
>=20
> > try to access my test cell (/afs/fritz.box), the access just hangs
> > forever. The accessing program (such as ls) cannot be interrupted
> > until I force a network disconnect between my client and the
> > server. Going back to Linux 6.6.12 solves the issue.
> >=20
> > I'm not sure how to debug this further. This is what `cmdebug
> > localhost` shows on the client, while ls is hanging:
> >=20
> >=20
> > Lock afs_discon_lock status: (none_waiting, 1 read_locks(pid:0))
> > ** Cache entry @ 0xf4e11100 for 0.1.16777984.1 [dynroot]
> >     locks: (none_waiting, write_locked(pid:6924 at:599))
> >               20 bytes  DV            1  refcnt     2
> >     callback 00000000	expires 0
> >     0 opens	0 writers
> >     mount point
> >     states (0x5), stat'd, read-only
> >=20
> >=20
> > Do you have any idea what could cause this issue or how I could
> > debug this further?
>=20
> I would try `echo t | sudo tee /proc/sysrq_trigger` to get information
> about hung threads printed to the console.
>=20
> -Ben
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel