Red Hat Bugzilla – Bug 489798
Autofs broken for non-nfs network file systems
Last modified: 2010-10-23 04:17:37 EDT
Description of problem: As of autofs-4.1.3-234.x86_64, we are no longer able to use autofs to mount volumes on our Panasas StorageCluster using our PanFS kernel driver. Version-Release number of selected component (if applicable): autofs-4.1.3-234.x86_64 How reproducible: Upgrade from any previous version of autofs to autofs-4.1.3-234. Automount maps that previously worked with mappings like this no longer work. Steps to Reproduce: 1. Update to autofs-4.1.3-234.x86_64 2. Create or use an existing automount map like this: mount1 -fstype=panfs panfs://panfs/path/to/mount1 3. Actual results: /var/log/messages entry: Feb 2 08:53:35 machine automount[9453]: host panfs: lookup failure 1 Feb 2 08:53:35 machine automount[9453]: failed to mount /panfs/path/to/mount1 Expected results: The automount should succeed, and has on previous versions of automount. Additional info: Am currently able to work around this issue by downgrading to the autofs provided by RHEL 4.0u5. The issue seems to come from the following lines of code in autofs-4.1.3-pass-colon-escape-to-nfs-mount-module.patch: - if (!strcmp(fstype, "nfs")) { + if (strstr(fstype, "nfs")) {
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Created attachment 335890 [details] Diff of update to patch colon escape of bug 428454 I've made this change to the original patch and made a scratch build. It is located in /mnt/redhat/brewroot/scratch/ikent/task_1732239 and is revision 237.bz498798.1. Could we get this to the customer for testing please.
We're awaiting testing feedback.
The test kernel does correct the issue, and mounts work as expected. Thanks, Internal Status set to 'Waiting on Engineering' This event sent from IssueTracker by bhamrick issue 275420
Fixed in version 4.1.3-238.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0991.html