[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] NFS configuration question



On Tue, 2005-07-12 at 10:14 +0200, Birger Wathne wrote:
> Eric Kerin wrote:
> 
> > On Tue, 2005-07-12 at 03:09 +0200, Birger Wathne wrote:
> > 
> >>I did a make install and service rgmanager stop/start.
> >>
> >>Now, status checks seem to work. After exportfs -r all file systems 
> >>eventually reappear.
> >>
> > 
> > 
> > Good to hear that fixed the monitoring for you.
> > 
> 
> Do you want the bad news as well?
> 
> The > 14 character long export path bug is still there in the FC4 branch.
> If the exported path is > 14 characters it will always fail status check and 
> get reexported. This is because exportfs breaks lines after the exported 
> path if it is long. I think exportfs shouldn't do this, but I guess the 
> cluster software will have to work around it.
> 
> The line that fails is:
> exportfs | grep -q "^${OCF_RESKEY_path}\ .*${OCF_RESKEY_target}"
> 
> A proper fix would be a filter to remove the offending line breaks. My quick 
> and dirty (and far less portable) fix is to use this instead:
> 
> grep -q "^${OCF_RESKEY_path}[   ]*${OCF_RESKEY_target}(" /var/lib/nfs/etab

Isn't this fixed in STABLE?

	#
	# Status check fix from Birger Wathne:
	# * Exports longer than 14 chars have line breaks inserted, which
	#   broke the way the status check worked.
	#
	exportfs -v | tr -d "\n" | sed -e 's/([^)]*)/\n/g' | grep -q \
		"^${OCF_RESKEY_path}[\t ]*.*${OCF_RESKEY_target}"
	rv=$?

Looks like *you* fixed it already!  I thought the FC4 branch is dead,
but do you want me to put it in the -FC4 branch anyway?

-- Lon


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]