Hi, about this bug report I found more clues about the problem.
Now I think it happens when updating the OpenAFS client and a kernel with a new ABI. I had a machine running buster with kernel 4.19.0-10-amd64 with a pending update to ABI 11 and a backport of openafs 1.8.6. This time I "apt install openafs-client openafs-modules-dkms" and later "apt upgrade" and everything was fine and working as expected. I have more machines needing update to v10.6 that I will use to chase down the exact circumstances that OpenAFS may stop working during an upgrade. Kind regards Jose M Calhariz On Sun, Aug 30, 2020 at 05:28:15PM -0700, Benjamin Kaduk wrote: > Hi Jose, > > Sorry that I missed this when it first came in. > A couple notes inline, if you still remember much about the original > report... > > On Sat, Aug 08, 2020 at 06:32:07PM +0100, Jose M Calhariz wrote: > > Package: openafs-client > > Version: 1.8.6-1~dsi10+1 > > Severity: normal > > > > Hi, > > > > I have made a "private backport" of openafs software from bullseye to > > buster. So this means is the first time for me that I am upgrading > > openafs client 1.8.x on live systems. Where in the past this worked > > To clarify: are you upgrading from 1.6.x to 1.8.x, or merely updating from > one 1.8.x version to a newer 1.8.x version? > > > without problems for openafs 1.4 and 1.6, now the openafs client stops > > working and I need to do a reboot. > > > > What I am requesting is that if possible to do a live upgrade of the > > software and the client does not stop working even if it is necessary > > to work with the old software until a reboot. > > What you are requesting is what is supposed to happen, so I'm unpleasantly > surprised to hear that it is not happening. > > Once I hear back about the problematic scenario I can try to reproduce in a > local VM. > > Thanks, > > Ben > -- -- Porque critica o que não entende (Sepultura)
signature.asc
Description: PGP signature
