[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Subtle NFS incompatibility with SunOS 4.1.1 on 68K
On Mar 17, 2020, at 4:33 PM, Jason Thorpe <thorpej%me.com@localhost> wrote:
> On Mar 17, 2020, at 3:59 PM, Chris Hanson <cmhanson%eschatologist.net@localhost> wrote:
>> Looks like the same issue, my system consistently passes -32 to write(4, ...) rather than -32768 but otherwise it's the same.
> Yah, that's completely weird why it would be passing a negative number to write(). Almost like it got a bad value from stat() or something?
Interesting that you mention that, since this is the output of df on my Sun-3:
Filesystem kbytes used avail capacity Mounted on
-1619144 -3584 -486024 65% /
-1619144 -3584 -486024 65% /usr
-1619144 -3584 -486024 65% /usr/kvm
-1619144 -3584 -486024 65% /usr/share/man
-1619144 -3584 -486024 65% /usr/local
-1619144 -3584 -486024 65% /home
I wonder if something is getting screwed up by the obvious integer overflows in computing filesystem size.
>>> Can you get a tcpdump of the failure from the RPI?
>> I'll try! I'll have to figure out how, but I expect it should be straightforward, right?
> On the RPI:
> sudo tcpdump -w nfs-fail.pcap port 2049
> ...ought to do it. Run that command on the RPI, attempt the test case on the Sun, ^C the tcpdump on the RPI, and the .pcap file should have a packet capture that can be easily sliced and diced in Wireshark.
I don't have WireShark handy, I can share the pcap with you if you want though. I figure I'll spare the rest of the list that 8KB attachment.
Main Index |
Thread Index |