[OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown

[Michal Svamberg]

Hi,
Thank for the link. The problem is that the clients have the same UUID
because they have the same SID. This problem is seen at hosts.dump
(kill -XCPU <pid_of_fileserver>) near the line with string
"lock:ffffffff", for example:
---cut---
ip:360de493 port:7001 hidx:251 cbid:16297 lock:ffffffff last:1159945605 active:1
159940686 down:0 del:0 cons:0 cldel:32
         hpfailed:0 hcpsCall:1159943657 hcps [ -211] [ 330de493 3a0de493 370de49
3 360de493 430de493 440de493 3e0de493 420de493 3d0de493 470de493 320de493 480de4
93 490de493 450de493 340de493 3f0de493 350de493 410de493 400de493 3c0de493] hold
s: 3bf69000000000000 slot/bit: 0/1
---cut---

The IP addresses of wrong configurated clients are in line with
'hpfailed'. After reconfiguration all affected stations the meltdown
doesn't appear any more.

I have a question about this problem, do you consider about new option
with maximum clients with the same UUID that can connected to
fileserver? Or write warning message to FileLog (without debug)?
By my opinion it is not good if clients are able to shutdown a server.

Thanks for answer,
Michal Svamberg.

On 10/10/06, Derrick J Brashear <shadow@dementia.org> wrote:
> On Tue, 10 Oct 2006, Michal Svamberg wrote:
>
> > We upgraded file servers to 1.4.1 (built  2006-05-05) but not solve meltdown.
> >
> get a backtrace when the fileserver is not responding.
>
> on a whim, you might also try this patch:
> http://grand.central.org/rt/Ticket/Display.html?id=19461
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>