Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 518530

Summary:	Please build coda module
Product:	Red Hat Enterprise Linux 5	Reporter:	Adam Goode <adam>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.4	CC:	bgilbert, rwheeler
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-09 15:28:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Goode 2009-08-20 19:00:44 UTC

Description of problem:
The coda module, which is required to run the coda userspace, is not built. Please consider enabling this. Now that CMU has a site license to Red Hat Enterprise Linux 5, our group would like to use coda with it.

The coda userspace is in Fedora and will likely be enabled for EPEL if the kernel module is shipped.

Note that the coda module is a filesystem driver and won't do anything if /coda is not mounted, which will not occur if the coda userspace is not installed.

Comment 1 Ric Wheeler 2009-09-09 15:28:39 UTC

We don't have any current plans to build and support the coda kernel module. We do support FUSE - any chance to redo your coda user space as a fuse fs?

Comment 2 Adam Goode 2009-09-09 16:26:28 UTC

Hmm, I suppose it is possible to do it as FUSE, but that would definitely be much slower and less featureful than it is currently. Right now, files from coda are cached locally and the coda kernel module just passes the file operations down to the underlying filesystem code, so once a file is open, there is no userspace<->kernel<->userspace roundtrip. FUSE would introduce this roundtrip.