From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14815 invoked from network); 6 Sep 2021 15:07:10 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 6 Sep 2021 15:07:10 -0000 Received: from mail-io1-f46.google.com ([209.85.166.46]) by 4ess; Mon Sep 6 10:59:13 -0400 2021 Received: by mail-io1-f46.google.com with SMTP id m11so9042130ioo.6 for <9front@9front.org>; Mon, 06 Sep 2021 07:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=wEv9+ND0bC6A1jpwSwFqFz3VzUod7lOhVmeAGvYqmv4=; b=Ljte8+MekTsE8H8GB7xH71gc1QIqPrFjKZtm323ls1reW/xIbFEC/d+4J1Pv2aSbfH KeWCLZsmNw7zBvZ77P25sc5kWDyiEFWhOFQpoN70v+ra/k+ow3Q8E24VGJx0C5wsnPFI mSPVQN+gSap77CPQZZxZhcd4WwHfkWAO+Et9AkJV0CDv0IZuo2/yBFiyPye3Api6DyXF IfKpaMw3RGqjNzqMl9924xQ3HZCzLQcG2KMeWh0jnca2iaWCUU+cZuhYnZC02CShfZur yuYGja9acWJs2zd8D6Ea4DC56oMOcJ3eJ8QCZ8fqCbPwh/ntjrzz86y4BFkbrwceHQTB /H0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=wEv9+ND0bC6A1jpwSwFqFz3VzUod7lOhVmeAGvYqmv4=; b=Av4azQFGfZmZADisLLtHjPNJXZqsAxIx8Td6t2s8+Hlc3h+qXwGOZwRqfOJcCd86By V9A8R+Ikb6qSPQu+i8Xz7PqeYCjt2JXgIsm69Ncuav9hIJ6orRqZBGUOwr11GR33NAFG NNcBEuYodCC82JifcFGEs4eH0xdQNSMlBhngSyQqcQc1W3aj/Yz1rXv1OU9RWncWS7N9 Qlxsk9GyVBzr1XkILkL9DjygLN+E9iWFny4BTFUseo5X8x5hrcr18819WfwCGVUBBsMb 3O8cK0m/2rPOoyiVbUpqUxDsXqOLSuPCEeCM4DP49KcXBqi9uHGp9zCmLZ3/fxTQpMKG DkYQ== X-Gm-Message-State: AOAM531Sjs3H95Ux4q5sgW3zinhfsY9Av9ZndI5+K62hqIXG0p7ZqSQ5 hKkqY0RbjujSK0e8yVMzeFn7t4g6ueNTI3QFxf/pEr5N X-Google-Smtp-Source: ABdhPJyHm/qISMC5ko8AgjlvoJf+Wl3dhxGMM/R06j8vwN8lPxyLgJI0Oy0J3Hvkt4Ig2NLS6wUSLlfHyQV0e5JyCpk= X-Received: by 2002:a05:6638:348e:: with SMTP id t14mr11433295jal.66.1630940343103; Mon, 06 Sep 2021 07:59:03 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: mrowczok Date: Mon, 6 Sep 2021 16:58:52 +0200 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: method component-scale replication high-performance layer Subject: Re: [9front] rconnect via aan reliability patch Reply-To: 9front@9front.org Precedence: bulk hey, some days ago i tested ftp server to see what speeds capable is 9front virtual machine, i'm using old installment - i wanted to test it on fresh system before posting on net/irc but maybe it is related somehow downloading file from ftp client on another pc manages to broke all connectivity on guest system, drawterm is unable to connect, 9p disk service is down. strange thing is that displaying netstat output on guest/cpu lags on certain moment. testing was done with 650mb file and can be reproduced. Stuff: guest: cwfs from 2016 kernel recompiled in august 2019. host: vmware workstation 15.5.5 build-16285975 Qualcomm/Atheros e2200 PCI-E Gigabit Ethernet Controller (with jumbo frames 9KB MTU) =C5=9Br., 1 wrz 2021 o 11:24 napisa=C5=82(a): > > > Write does not block. Read does. > > i know. > > > In the case with read errors, the aanserver end did everything > > before aanclient starts to read the address, and somehow the channel > > has hung up before the read. > > yeah, but we really need to figure out why. we might have a bug > in the tcp stack here, or you might just have some mtu issues > in your network. > > i'm not going to blindly change protocols to tamper over mysterious > tcp connection problems. > > > The extra read in aanserver blocks the aanserver at that point and > > wait for the OK signal from aanclient before continuing. > > yes, i understand that. > > > The thing I don't understand is that what actually makes the channel > > hang up. Do you have any suggestions as to how to debug this issue? > > i never had these issues. is it reproducable for you? > > we can start by making packet captures with snoopy or wireshark. > > if it is sporadic, we could also try to provoke it by doing the > exact opposite to your patch and delaying the client with a sleep > maybe? it could also be possible that it is closed my ourselfs > somehow by accident. > > -- > cinap