problems with nfs+TCP - Resource temporarily unavailable
sten at blinkenlights.nl
Thu May 26 03:45:54 PDT 2005
On Thu, 26 May 2005, Bernd Walter wrote:
> On Thu, May 26, 2005 at 01:03:25AM +0200, Oliver Lehmann wrote:
>> I tried the same with an other nfs server (using dill as nfs server this
>> time - system description is in my 1st mail, same mount options like /
>> mnt/files). And guess what? dill rebooted immediate... dd came never
>> back, gave no output
>> dill's dmesg shows me:
>> fatal kernel trap:
>> trap entry = 0x4 (unaligned access fault)
>> faulting va = 0xfffffc0006b6f44d
>> opcode = 0x28
>> register = 0x5
>> pc = 0xfffffc0000541e08
>> ra = 0xfffffc0000541df4
>> sp = 0xfffffe000a0f9b70
>> usp = 0x11ffea80
>> curthread = 0xfffffc000f91ee10
>> pid = 343, comm = nfsd
> This is absolutely known - TCP/nfs has bugs in realigning packets.
> Don't use TCP on strong aligned architectures.
Still a pr with a proper backtrace would be nice.
Or does one exist already ?
"There is a crack in everything, that's how the light gets in."
Leonard Cohen - Anthem
More information about the freebsd-stable