Bug 1564983
Summary: | The mount-vfs failed to mount the logical volume | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | YongkuiGuo <yoguo> |
Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.6 | CC: | ptoscano |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libguestfs-1.38.1-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 07:45:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1551055 | ||
Bug Blocks: |
Description
YongkuiGuo
2018-04-09 06:09:18 UTC
> [ 11.893586] traps: guestfsd[190] general protection ip:5583dc66da83 sp:7ffcc869b910 error:0 in guestfsd[5583dc585000+1c2000]
/init: line 244: 190 Segmentation fault $cmd
Ouch.
A one line reproducer (which works upstream too) is:
$ guestfish -v -x -N lvfs mount-vfs "" ext2 /dev/VG/LV /
Upstream fix: https://github.com/libguestfs/libguestfs/commit/07ead43cbbf0bbc69a00e4a5df1a9642fd75cbf4 Fix backported in 1.38.1. Verified with packages: libguestfs-1.38.1-1.el7.x86_64 Steps: 1. On rhel7.5 host #guestfish -v -x -N lvfs mount-vfs "" ext2 /dev/VG/LV / --------------------------------------------------------- ... command: mount '-t' 'ext2' '/dev/VG/LV' '/sysroot//' [ 2.570310] EXT4-fs (dm-0): mounting ext2 file system using the ext4 subsystem [ 2.573742] EXT4-fs (dm-0): mounted filesystem without journal. Opts: (null) guestfsd: => mount_vfs (0x4b) took 0.01 secs libguestfs: trace: mount_vfs = 0 ... --------------------------------------------------------- No error pops up. So verified this bug. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3021 |