> Did both the client and server have the same IP addresses before the > reboot? Yes. > If not, the Linux client's nfs_client_id4.id SetClientID argument > will be different (it has the client/side IP# in it). nfs_client_id4.id > isn't supposed to change for a given client when it is rebooted. > That will make the FreeBSD NFSv4 server see "new client" (which is not in the > stablerestart file used to avoid certain reboot edge conditions) and > will not give it a grace period. > This is the only explanation I can think of for the NFS4ERR_NO_GRACE > reply shortly after the reboot. I checked some other clients and they all receive the NFS4ERR_NO_GRACE response from the server. It's not unique for the clients that hang. I was unable to reproduce this is a minimal test configuration. Perhaps the nfs-stablerestart file is corrupt on the server? I checked strings nfs-stablerestart and I see a lot of duplicate entries. In total there are ~10000 lines but we only have ~50 clients. Most clients have 3 types of entries: Linux NFSv4.0 a.b.c.d/e.f.g.h tcp Linux NFSv4.0 a.b.c.d/e.f.g.h tcp* Linux NFSv4.0 a.b.c.d/e.f.g.h tcp+ Again, thanks a lot for looking into this. Bram. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
