By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1545

Summary:	tde-guidance: mountconfig does not handle LABEL correctly in fstab
Product:	TDE	Reporter:	Francois Andriot <albator78>
Component:	non-core programs	Assignee:	Francois Andriot <albator78>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, kb9vqf
Priority:	P5
Version:	3.5.13.2 [Trinity]
Hardware:	All
OS:	Other
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	tde-guidance 3.5.13.2 : fix handling of LABEL in fstab in mountconfig

Description Francois Andriot 2013-06-13 09:23:45 CDT

Hello, on RHEL/Fedora distributions, when using LABEL in fstab, the partition are labelled using the mount point directly.
E.g. fstab contains (example):
LABEL=/      /     ext4    defaults 1 1
LABEL=/usr   /usr  ext4    defaults 1 2

But alas, the "mountconfig" does not finds them. The partitions are shown in the list since they are mounted (present via /etc/mtab), but the fstab-related information are missing.
When replacing LABEL= with device names in fstab, it works correctly.
Example:
/dev/sda1    /     ext4    defaults 1 1
/dev/sda2    /usr     ext4    defaults 1 1

Comment 1 Francois Andriot 2013-06-13 09:26:47 CDT

Created attachment 1308 [details]
tde-guidance 3.5.13.2 : fix handling of LABEL in fstab in mountconfig

The root cause of the problem is that, when using filesystems labels containing "/" caracter, it is seen by hal as the "%" caracter.
(I dunno if this is an HAL bug or if this is a general problem with the "/" caracter in labels)

E.g:
 lshal|grep volume.label
 volume.label = %usr

The attached patch fixes this problem.
Also, it adds "support" for ext4 partitions.

Comment 2 Timothy Pearson 2013-06-13 16:20:29 CDT

Even though we don't really support guidance any longer (largely due to long-maintenance issues as the code is Python and relies on HAL in places), I see no harm in this patch.  Committed to GIT in hash 3b6ac8e.

Thanks for reporting, and for the patch!