Bug 208999

Summary: gfs_fsck must handle selinux extended attributes
Product: Red Hat Enterprise Linux 5 Reporter: Ryan O'Hara <rohara>
Component: gfs2-utilsAssignee: Ryan O'Hara <rohara>
Status: CLOSED CURRENTRELEASE QA Contact: GFS Bugs <gfs-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-23 01:00:23 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 Ryan O'Hara 2006-10-02 21:26:22 UTC
Description of problem:

When running gfs_fsck against a GFS(1) filesystem that contains files with
SELinux extended attribute, the fsck complains/removes the xattrs.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a gfs filesystem on a machine that has SELinux enabled.
2. Create some files on GFS filesystem.
3. Unmount and run gfs_fsck.
  
Actual results:

Starting pass1c
EA (selinux) type is invalid (3 > 2).
Removing EA located in block #46.
EA (selinux) type is invalid (3 > 2).
Removing EA located in block #48.

Expected results:
Normal fsck behavior.

Additional info:
Must have SELinux enabled and a correct policy installed.

Comment 1 Ryan O'Hara 2006-10-02 21:39:56 UTC
Fixed. Needed to defined GFS_EATYPE_SECURITY and increment GFS_EATYPE_LAST so
that gfs_fsck will recognize SELinux extended attributes.



Comment 2 Rob Kenna 2006-10-03 12:52:29 UTC
Moved over to RHEL5 as it effects R5 platform support.  Kevin, add an ACK.

Comment 3 Kiersten (Kerri) Anderson 2006-10-03 14:16:55 UTC
Devel ACK

Comment 5 RHEL Program Management 2006-12-23 01:00:23 UTC
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.