Hi Jeffrey-
Ah, that probably explains it, I do not have afsd running. The reason I
don't is because I can't get it to stop crashing the system again.
Here's the stack trace from the kernel panic:
KDB(0)> stack
pvthread+01A700 STACK:
[F100C04BDE30]afs_mount+0001F0 (F1000A03E0251110, F1000A03E038947C,
F100C04BDC40)
[F100C04B4D30]vfs_mount+90 (F1000A03E0251110, F1000A03E038947C)
[00014D70].hkey_legacy_gate+4C ()
[006155AC]vfs_mount+2C (??, ??)
[00701D7C]smount+0004FC (??)
[00702AC8]vmount+000248 (??, ??)
[3888]mfspurr_sc_flih01+E4 ()
[10001918]10001918 ()
[10001E90]10001E90 ()
[1000597C]1000597C ()
[10001518]10001518 ()
[10001068]__start+68 ()
KDB(0)>
I've most often seen this when the entry in /etc/vfs isn't correct, but it
most certainly is, and as I mentioned, this was working before. I recompiled
from the latest source and blew away the original binaries.
I was wondering if the cache or the AFS volumes were corrupt, so I blew them
all away also and re-created them.
$ df -k
Filesystem1024-blocks Free %UsedIused %Iused Mounted on
/dev/hd4 425984193972 55%1215221% /
/dev/hd2 3768320 84288 98%5869659% /usr
/dev/hd9var655360218032 67% 689312% /var
/dev/hd3 163840134072 19% 239 1% /tmp
/dev/hd1 6291456706136 89% 1378 1% /home
/dev/hd11admin 1310721306921%5 1% /admin
/proc - -- - - /proc
/dev/hd10opt 3145728 1651220 48%33565 9% /opt
/dev/livedump 2621442617761%4 1% /var/adm/ras/livedump
/dev/projectlv31457280 297605686%47824 1% /project
/dev/cachelv65536 49008 26% 1583 2% /usr/vice/cache
$ cat /opt/openafs/etc/openafs/cacheinfo
/afs:/usr/vice/cache:5
I feel like I'm missing something simple...
Thank you.
-Ben
From: Jeffrey E Altman
Sent: Wednesday, May 3, 2023 9:38 AM
To: Ben Huntsman; [email protected]
Subject: Re: [OpenAFS] More Kerberos + Windows issues
On 5/3/2023 11:45 AM, Ben Huntsman
([email protected]<mailto:[email protected]>) wrote:
Setting tokens. adUser @ mydomain.com
aklog: a pioctl failed while setting tokens for cell mydomain.com
pioctl issue usually means no cache manager is running
