I have looked for any other reports on this particular issue and cannot find any. Please point me to the correct workaround if it exists.
I've set up a liveUSB key for Fedora 9 and Fedora 10 on a 4GB USB key with a 2GB persistent overlay using the LiveUSB Creator. After running _some_ updates (nothing big, around 50MB) and changing some configurations, I begin getting an error for some files: "Stale NFS Handler". The file will not open. In this past trial, I tried opening /etc/resolv.conf because I was getting an IP address assigned via DHCP; before running updates, I could ping inside and outside the network. After running updates, it would not ping anything using the FQDN, prompting me to look at the /etc/resolv.conf file which threw the stale NFS handler error. This is merely an example since I've had other files unrelated to networking to throw the same error.
Are there any workarounds for this?
Thanks! Tom King ------- "Concern for man and his fate must always form the chief interest of all technical endeavors. Never forget this in the midst of your diagrams and equations." --Albert Einstein
On Tue, Dec 16, 2008 at 01:51:59PM -0600, Thomas King wrote:
I have looked for any other reports on this particular issue and cannot find any. Please point me to the correct workaround if it exists.
I've set up a liveUSB key for Fedora 9 and Fedora 10 on a 4GB USB key with a 2GB persistent overlay using the LiveUSB Creator. After running _some_ updates (nothing big, around 50MB) and changing some configurations, I begin getting an error for some files: "Stale NFS Handler". The file will not open. In this past trial, I tried opening /etc/resolv.conf because I was getting an IP address assigned via DHCP; before running updates, I could ping inside and outside the network. After running updates, it would not ping anything using the FQDN, prompting me to look at the /etc/resolv.conf file which threw the stale NFS handler error. This is merely an example since I've had other files unrelated to networking to throw the same error.
Are there any workarounds for this?
I'm not quite sure really... this sounds like there is some corruption going on in the overlay for some reason. It sounds like the problem could lie with the device-mapper that handles the overlay itself. Since I'm not very familiar with that code, I don't know of any workarounds. If you're still hitting this problem, I'd recommend bugging the device-mapper guys.
luke
liveusb-creator@lists.stg.fedorahosted.org
-
Luke Macken -
Thomas King