Bug 189017 - magic doesn't know about OCFS or ASM
Summary: magic doesn't know about OCFS or ASM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: file
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Martin Bacovsky
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-14 19:09 UTC by Aaron Botsis
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 18:45:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch and specfile patch for RHEL3 (1.06 KB, patch)
2006-04-14 19:09 UTC, Aaron Botsis
no flags Details | Diff

Description Aaron Botsis 2006-04-14 19:09:46 UTC
Description of problem:

File's included magic doesn't know about Oracle Clustered Filesystem or Automated Storage Manager 
volumes.

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

All RHEL3

How reproducible:

Very.

Steps to Reproduce:
1. Create ASM or OCFS device/filesystem
2. Run file -s on the device
3.
  
Actual results:

File thinks it's "data"

Expected results:

File should know it's OCFS or ASM, like this:

/dev/sdr1:       Oracle ASM Volume, Disk Name: DISK7
/dev/sdaa1:      Oracle Clustered Filesystem, rev 1.2, label: orarega01, mountpoint: /oradata/orarega01


Additional info:

patch and specfile patch included for RHEL3

Comment 1 Aaron Botsis 2006-04-14 19:09:47 UTC
Created attachment 127758 [details]
patch and specfile patch for RHEL3

Comment 2 Radek Vokál 2006-04-21 11:43:23 UTC
Applied on rawhide, RHEL3 proposed list is currently closed, so I'll add this as
soon as new schedule for next update will be out. 

Comment 3 RHEL Program Management 2007-10-19 18:45:17 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.


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