Hi, on 2 different servers, running 7.1-stable + zfs, I get this error rather frequently: Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1936028704) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1869363744) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1667787057) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (976040755) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1953459488) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1348825156) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (0) from nfs server sunfire:/dist Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1647208041) from nfs server sunfire:/dist in this case the server is running Freebsd-7.0-stable, but I also get it when the server is a netapp. is there a connection? thanks, danny
On 2009-Feb-06 08:32:27 +0200, Danny Braniss <danny@cs.huji.ac.il> wrote:>on 2 different servers, running 7.1-stable + zfs, I get this >error rather frequently: > >Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from >nfs server sunfire:/distI gather warhol-00 is running 7.1-S+ZFS. How recent a 'stable' is it? Where does ZFS fit in? Is sunfire:/dist mountpoint in a local ZFS or is a local ZFS mountpoint inside the sunfire:/dist mount? Do you get the same problems without any ZFS mounts? Is this a TCP or UDP NFS mount? What happens if you switch protocols? What NIC are you using and are you seeing any network errors? Are you able to capture a protocol trace showing the transaction including erroneous packet? -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090206/eb9fd300/attachment.pgp
I'm reposting this to hackers, and there is some more info.> Hi, > on 2 different servers, running 7.1-stable + zfs, I get this > error rather frequently: > > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1936028704) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1869363744) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1667787057) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (976040755) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1953459488) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1348825156) from > nfs server sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (0) from nfs server > sunfire:/dist > Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1647208041) from > nfs server sunfire:/dist > > in this case the server is running Freebsd-7.0-stable, but I also get it when > the server is a > netapp. > > is there a connection? > > thanks, > dannygoing through the logs, after it happened again, I got a glimps of this: Feb 6 18:00:13 warhol-00.cs.huji.ac.il kernel: bce0: discard frame w/o leading ethernet header (len 0 pkt len 0) Feb 6 18:00:19 klee-05.cs.huji.ac.il kernel: nfs: server warhol-00 not responding, timed out ... Feb 6 19:00:00 warhol-00.cs.huji.ac.il amd[715]: More than a single value for /defaults in hesiod.local Feb 6 19:00:00 warhol-00.cs.huji.ac.il amd[715]: Unknown $ sequence in "rhost:=${RHOST};type:=nfsl;fs:=${FS};rfs:=$huldig<C0>#^ZM-^KoM- abase" Feb 6 19:00:00 warhol-00.cs.huji.ac.il kernel: impossible packet length (2068989523) from nfs server sunfire:/dist which seems to point fingers at bce... danny
On 2009-Feb-08 10:45:13 +0200, Danny Braniss <danny@cs.huji.ac.il> wrote:>Feb 6 18:00:13 warhol-00.cs.huji.ac.il kernel: bce0: discard frame w/o >leading ethernet header (len 0 pkt len 0)...>Feb 6 19:00:00 warhol-00.cs.huji.ac.il amd[715]: Unknown $ sequence in >"rhost:=${RHOST};type:=nfsl;fs:=${FS};rfs:=$huldig<C0>#^ZM-^KoM- abase" >Feb 6 19:00:00 warhol-00.cs.huji.ac.il kernel: impossible packet length >(2068989523) from nfs server sunfire:/dist > >which seems to point fingers at bce...It does rather suggest that bce is not behaving. What happens if you turn off checksum off-loading? This should make the kernel drop the corrupt packets instead of trying to process them. If practical, you could also try (temporarily) plugging in a different NIC. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20090208/3c54a215/attachment.pgp