Red Hat Bugzilla – Bug 428437
Add GFS2 recognition and reporting to "file" command
Last modified: 2011-01-28 09:46:29 EST
Add equivalent reporting to file command as found with ext and other file
[root@localhost ~]# file -s /dev/hda1
/dev/hda1: Linux rev 1.0 ext3 filesystem data (needs journal recovery)
Here's a start :)
0x10000 belong 0x01161970 GFS2 Filesystem
>0x10024 belong x (blocksize %d,
>0x10060 string >\0 lockproto %s)
[root@bear-05 ~]# file -s -m ./magic /dev/sdb3
/dev/sdb3: GFS2 Filesystem (blocksize 4096, lockproto lock_nolock)
OK. I like bugs like this one. :)
FWIW, adding the other text string, locktable, might be good too. I'm sure the
GFS2 guys can let you know which pieces of information are most useful.
(.... and maybe a good time to add GFS recognition too? (in addition to GFS2))
Or, ignore the scope creep. Up to you ;)
Tomas, is there any reason why this cannot be resolved now that 5.3 is open?
Rob, Kevin: please can you set the requested flags on this bug?
We're updating file to recognize ext4 as well, so good to batch these up for 5.3.
Has this been fixed for "file" in upstream or fedora yet? No downstream-only
fixes please... :) I assume Tomas will send it upstream, I guess.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Tomas, what is the current status of this? Can we resolve this one now?
Created attachment 313581 [details]
example gfs2 filesystem
following commands were used to create this small sample:
dd if=/dev/zero of=gfs2filesystem bs=1024 count=10000
mkfs.gfs2 -O -J 8 -r 32 -p lock_nolock gfs2filesystem
gfs2-utils package necessary
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.