problems with nfs+TCP - Resource temporarily unavailable
ticso at cicely12.cicely.de
Thu May 26 03:58:35 PDT 2005
On Thu, May 26, 2005 at 12:45:50PM +0200, Sten Spans wrote:
> 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 ?
Not that I know.
I did know exactly when this happens years ago.
The backtrace as such will not help you as the panic happens much
later than the cause.
IIRC the basic problem was that the realignment code only fixes
a single missalignment, while theres a chance for more then one.
Verify nfs_realign in nfsserver and nfsclient to get an idea.
If you are interested - I've found a (non-working) patch that I wrote
for it, but the intention of it should be clear.
B.Walter BWCT http://www.bwct.de
bernd at bwct.de info at bwct.de
More information about the freebsd-stable