Re: [2.2.11] mount process blocked in nfs mount

Alan Cox (alan@lxorguk.ukuu.org.uk)
Mon, 16 Aug 1999 11:44:25 +0100 (BST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Benjamin Herrenschmidt: "Re: New resources - pls, explain :-("
Previous message: Alan Cox: "Re: New resources - pls, explain :-("
Next in thread: Christoph Rohland: "Re: [2.2.11] mount process blocked in nfs mount"
Reply: Christoph Rohland: "Re: [2.2.11] mount process blocked in nfs mount"

> 10:14:45.665972 uscd02.32779 > 155.56.95.75.1011: . ack 134 win 10136 <nop,nop,timestamp 559235892 58201> (DF)
> 10:14:45.666285 uscd02.32779 > 155.56.95.75.1011: F 65:65(0) ack 134 win 10136 <nop,nop,timestamp 559235892 58201> (DF)
> 10:14:45.666485 155.56.95.75.1011 > uscd02.32779: . ack 66 win 32120 <nop,nop,timestamp 58201 559235892> (DF)

The mount protocol finishes

> 10:14:45.734686 155.56.95.75.14708860 > uscd02.nfs: 128 getattr [|nfs]
> 10:14:46.427902 155.56.95.75.14708860 > uscd02.nfs: 128 getattr [|nfs]
> 10:14:47.827923 155.56.95.75.14708860 > uscd02.nfs: 128 getattr [|nfs]
> 10:14:50.627991 155.56.95.75.14708860 > uscd02.nfs: 128 getattr [|nfs]

The sun is ignoring requests for attributes.. so it keeps trying. At least
thats how this appears to read. Incorrect firewalling ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Benjamin Herrenschmidt: "Re: New resources - pls, explain :-("
Previous message: Alan Cox: "Re: New resources - pls, explain :-("
Next in thread: Christoph Rohland: "Re: [2.2.11] mount process blocked in nfs mount"
Reply: Christoph Rohland: "Re: [2.2.11] mount process blocked in nfs mount"