Bug 234168 – GFS2's rgrp flags unused

Bug 234168 - GFS2's rgrp flags unused

Summary:	GFS2's rgrp flags unused

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	GFS-kernel (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Steve Whitehouse
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	235346 235931
	Show dependency tree / graph

Reported:	2007-03-27 11:33 EDT by Steve Whitehouse
Modified:	2007-11-30 17:12 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	2.6.20-1.2944
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-04-11 16:16:50 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Patch to fix this bug (853 bytes, patch) 2007-04-02 05:43 EDT, Steve Whitehouse	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Steve Whitehouse 2007-03-27 11:33:32 EDT

GFS2 has a set of rgrp flags defined as part of its on disk format. The most
important of these is: GFS2_RGF_NOALLOC. Currently the gfs2 rgrp code ignores
all of these flags.

We will eventually need to add an interface which allows setting of the flags,
but for now, just making sure that the NOALLOC flag is obeyed correctly is the
priority so that its there for future use.

Ben, CCing you on this one since you've just been working on a bug in a smilar
area of the code.

Comment 1 Steve Whitehouse 2007-04-02 05:43:39 EDT

Created attachment 151411 [details]
Patch to fix this bug

This fixes the bug. Although it doesn't deal with all the flags, I can't
currently see any reasonable use for the data/metadata flag (in fact, due to
the allocation policy of GFS2, its actually a non-inode/inode flag despite its
name). So the only one which is really important here is the "noalloc" flag.

Note You need to log in before you can comment on or make changes to this bug.