Hide Forgot
Description of problem: when partition formatted to ext2 nautilus properties tab shows ext2 udisks --show-info /dev/sde2 |grep type type: ext2 type: 0x83 Version-Release number of selected component (if applicable): nautilus-2.28.4-18.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.format partition as ext2 2.mount it via nautilus 3.right click and properties Actual results: ext3/ext4 type shown Expected results: should be ext2 Additional info:
(In reply to comment #0) > Description of problem: > when partition formatted to ext2 nautilus properties tab shows ext2 ah..this should be tab shows ext3/ext4
So, found this related commit: http://git.gnome.org/browse/glib/commit/gio/glocalfile.c?id=25ff8ee7486c7bdf1612d3554fc1d7d91daedfa6 And tested myself: created an empty file, called mke2fs on it, and got this output: > $ tune2fs -l test.bin > tune2fs 1.42 (29-Nov-2011) > ... > Filesystem magic number: 0xEF53 > Filesystem revision #: 1 (dynamic) > Filesystem features: ext_attr resize_inode dir_index filetype sparse_super > ... So there's no journal and plain mount command autodetects ext2. But it looks like the filesystem is indeed ext3 without journalling (ext2 mode?). Pure ext2 filesystem should have the 0xEF51 magic number. Could you please check on your side? (In reply to comment #0) > Description of problem: > when partition formatted to ext2 nautilus properties tab shows ext2 > udisks --show-info /dev/sde2 |grep type > type: ext2 > type: 0x83 This is just a partition type. And udisks is not used for file:// URI scheme. And that's probably the culprit here - we show filesystem type information based on physical filesystem data, not showing the actual mode the fs is mounted as. As long as other filesystems use different magic numbers for their versions, this is only the case for ext{2,3,4,5?}. > $ mount > /tmp/test.bin on /tmp/te type ext2 (rw,relatime,errors=continue,user_xattr,acl) > $ gvfs-info -f file:///tmp/te > filesystem::type: ext3/ext4 Could you also please output of this command?
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.