On Sun, Feb 28, 2010 at 12:35:31AM +0100, Iustin Pop wrote: > Hi, > > I can confirm this is not a configuration issue, but a regression. I > keep nfs-kernel-server version 1.2.0-4.1 pinned on my server, since > that's a known working version. The current version in unstable > (1.2.1-3) is broken.
I have just tried plain upstream versions: - 1.2.0: crossmount works fine - 1.2.1: broken - 1.2.2: broken As such, this seems to be a regression in upstream behaviour. My possibly wrong investigations trace it to upstream commit bc0a6ab03089fc1ea4fea26ed9635c2cc918b01b, which should fix some problems with crossmnt and fsid; however, it seems to uncover other issues. Reverting the write_secinfo changes in this patch make 1.2.1 work again (but I get then the 1.2.0 message of "qword_eol: fflush failed"). I'll forward this upstream. iustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
