Posted by: h4ck@lyst | December 6, 2008

Fedora 10 aka cambridge

Finally installed fedora 10 on my laptop, 3 other desktops and a server.
Initial response was its good, faster boot up, lesser configuration required to get it up and running with our various network services.
The installation on the server was a nice experience. Why? Coz I ran into a major bug 🙂
other bz ids include 466534, 466071

I was getting this error

Volume group ‘VolGroup00″ not found.
Unable to access resume device (/dev/VolGroup01/LogVol01)
Mount: error mounting /dev/root on /sysroot as ext3: No such file or directory

More details here

Basically F10 initrd does not wait long enough for the disk scans to complete, with many scsi and raid cards.
And then found a work around involving rebuilding the initrd using mkintrd command.

boot in using your install media, then go to the recovery option.
then at the prompt
mkinitrd -f –with=scsi_wait_scan /boot/initrd-{filename as in ls of /boot} {the-rest-of-file-name-without-initrd-and-img}
see man mkinitrd

Then this got me booted into fedora happily.
Next was setting up the network. It was pretty simple and straight forward on the clients which used DHCP. Just had a lil problem with one of the clients having two network cards. But the server had three network interfaces. And for some strange reasons it just wont work! The network gui would overwritr the subnet mask with the provided gateway value always! So used the tui to get it up and running!

Installing ldap was pretty simple this time.
NFS was pretty straight forward also but right now am running into some problems regarding file locking with java. It says

” Error reading configuration: An error occurred while locking file “/web
team/anshu/.eclipse/org.eclipse.platform_3.4.0_155965261/configuration/org.eclipse.osgi/.manager/.fileTableLock”: “No locks available”. A common reason is that the file system or Runtime Environment does not support file locking for that location. Please choose a different location, or disable file locking passing “-Dosgi.locking=none” as a VM argument.

Well the nfslock is working fine on both server and client. rpc.mountd is running fine! And I checked it by tring to open two instances of openoffice from the same nfs share. The second instance promptly told me that another instance was running, and this implies that the file locking is working fone for it. Though open office failed to report the user and the client machine on which the other instance was running this time, something that it used to do efficiently in the previous versions! Maybe there indeed is a file locking problem 😦

While looking for the answer to this problem, I ran into a ver good explanation of what was the stale nfs lock error that we had been facing all this time..

“If the kernel crashes (or the power cord gets pulled) on an NFS client machine, theoretically when you reboot the client machine it will notify the NFS server that it has rebooted and all previously-held locks should be released. However, many operating systems including Red Hat Linux 7.2 do not properly do this; so you will have stale locks after a crash.”

and some more info from the same post..
” If you have an NFS-mounted home directory, you must be running an rpc.statd/rpc.lockd setup on both NFS client and NFS server, so that file locking works. On Red Hat Linux, this means the “nfslock” service must be running. Enable it permanently with the chkconfig tool – see its manual page. Turn it on or off at any given time with service nfslock start or service nfslock stop. You must be root to do this.”

Interesting. So now I now know something about the stale nfs errors!
Lets see how soon do I manage to get over with this problem.
workaround found thanks to #eclipse @ freenode
eclipse -vmargs -Dosgi.locking=none
Now lets see how to put it so that I dont ahve to type it all the time. Maybe an alias. 😦

The music play is a bit choppy in the beginning of the songs. Amarok splash screen looks nice. gtkpod has better features. More as and when I keep usiing fedora 10 aka cambridge all the more 🙂


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s


%d bloggers like this: