Linux-kernel mailing list archive 1999-23,: Re: knfs-1.2.2a strange behaviour

# Re: knfs-1.2.2a strange behaviour

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 6 Jun 1999 16:28:54 +0100 (BST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Rainer Wiener: "Soundcard Database"
- Previous message: Jochen Heuer: "[2.3.5ac1]: Oops during insmod BusLogic"
- Next in thread: Joerg Dorchain: "Re: knfs-1.2.2a strange behaviour"
- Reply: Joerg Dorchain: "Re: knfs-1.2.2a strange behaviour"

> IMHO this is a bug in either the nfs client or the server, as this can
> lead to serious crashes. If it hadn't been an nfs-filesystem. there would

The NFS server causing the ext2 errors is a real bug. Definitely

> have a 'text file busy' error preventing my from overwriting a running
> file. Deleting removes the inode, but keeps the old text file as long as
> the program is running. Is it possible to implement this in nfs, or is
> there a contradiction to the stateless nature of nfs?

It isnt sanely possible with NFS, NFS is stateless. You normally get bus
error (core dumped) on all platforms on the binary swapped underneath NFS
case

You should _not_ have got ext2 warnings as well however

-
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: Rainer Wiener: "Soundcard Database"
- Previous message: Jochen Heuer: "[2.3.5ac1]: Oops during insmod BusLogic"
- Next in thread: Joerg Dorchain: "Re: knfs-1.2.2a strange behaviour"
- Reply: Joerg Dorchain: "Re: knfs-1.2.2a strange behaviour"