Bug 876679

Summary:	32bit support in Fuse, related to special option nfs.enable-ino32
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Scott Haines <shaines>
Component:	fuse	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED ERRATA	QA Contact:	Anush Shetty <ashetty>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0	CC:	aavati, csaba, cww, divya, gluster-bugs, grajaiya, joe, mhergaar, mkranz, ndevos, rhs-bugs, shaines, storage-doc, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Patch, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Add support for clients mounting Red Hat Storage volumes that are not able to use 64-bit inodes. Reason: Some clients and applications are not able to use 64-bit inodes and can therefore not utilize native mountpoints from Red Hat Storage. Result (if any): The Red Hat Storage native client now accepts the "enable-ino32" mount-option that causes the filesystem to present 32-bit inodes instead of 64-bit ones. See https://access.redhat.com/knowledge/solutions/201483 for a more complete description.	Story Points:	---
Clone Of:	850352	Environment:
Last Closed:	2013-03-28 22:26:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	850352
Bug Blocks:

Comment 3 Divya 2013-02-12 10:40:36 UTC

Niels,

This bug has been added to Update 4 errata. Could you provide your inputs in doc text field which will enable me to update errata??

Thanks,
Divya

Comment 4 Niels de Vos 2013-02-12 11:41:52 UTC

Doc Text updated, please check and update if needed. It contains a reference to
https://access.redhat.com/knowledge/solutions/201483 which may or may not be
suitable.

Comment 9 Anush Shetty 2013-03-04 10:13:33 UTC

Moving it to verified with glusterfs-fuse-3.3.0.5rhs-43.el6rhs.x86_64

Comment 11 errata-xmlrpc 2013-03-28 22:26:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0691.html