Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
For example,
mke2fs doesn't support xfs, it should give a meaningful error message when you specified xfs, but not gives ext3
Version-Release number of selected component (if applicable):
libguestfs-1.22.2-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. create a disk with xfs
[root]# guestfish -N fsfs
><fs> quit
2.
[root]# eval `guestfish --listen`
[root]# guestfish --remote -x -- -add test1.img
[root]# guestfish --remote -x -- -alloc journalname 50M
[root]# guestfish --remote -x -- -run
[root]# guestfish --remote -- -mke2journal 1024 /dev/sdb
[root]# guestfish --remote -- -mke2fs-J xfs 1024 /dev/sda /dev/sdb
[root]# vfs_type=`guestfish --remote -- -vfs-type /dev/sda`
[root]# echo $vfs_type
ext3
Actual results:
Got ext3 type
Expected results:
Give a error message
Additional info:
Comment 1Richard W.M. Jones
2013-06-26 10:13:27 UTC
One line reproducer:
$ guestfish -N part -N part mke2journal 1024 /dev/sda1 : mke2fs-J xfs 1024 /dev/sdb1 /dev/sda1
$ echo $?
0
The mke2fs-J command should give an error instead of succeeding.
Comment 2Richard W.M. Jones
2013-07-05 14:54:28 UTC
Verified with libguestfs-1.22.6-16.el7.x86_64
# guestfish -N part -N part mke2journal 1024 /dev/sda1 : mke2fs-J xfs 1024 /dev/sdb1 /dev/sda1
libguestfs: error: mke2fs_J: xfs: not a valid extended filesystem type
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: For example, mke2fs doesn't support xfs, it should give a meaningful error message when you specified xfs, but not gives ext3 Version-Release number of selected component (if applicable): libguestfs-1.22.2-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. create a disk with xfs [root]# guestfish -N fsfs ><fs> quit 2. [root]# eval `guestfish --listen` [root]# guestfish --remote -x -- -add test1.img [root]# guestfish --remote -x -- -alloc journalname 50M [root]# guestfish --remote -x -- -run [root]# guestfish --remote -- -mke2journal 1024 /dev/sdb [root]# guestfish --remote -- -mke2fs-J xfs 1024 /dev/sda /dev/sdb [root]# vfs_type=`guestfish --remote -- -vfs-type /dev/sda` [root]# echo $vfs_type ext3 Actual results: Got ext3 type Expected results: Give a error message Additional info: