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.
DescriptionRobert Peterson
2017-08-17 13:51:31 UTC
Description of problem:
I got a set of GFS2 metadata from a customer, only to discover
the symlinks were all blank. That's because in gfs2_edit's
savemeta.c function get_gfs_struct_info it has:
(After a special case for saving directories)
else if (!inode->i_di.di_height && !block_is_systemfile(owner) &&
!S_ISDIR(inode->i_di.di_mode))
*gstruct_len = sizeof(struct gfs2_dinode);
So savemeta should also save the full contents for symlinks.
In this case, we can simply add something like:
&& !S_ISLNK(inode->i_di.di_mode))
Or some such.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1.ln -s /etc/fstab /mnt/gfs2/my_symlink
2.umount /mnt/gfs2
3.gfs2_edit savemeta <dev>
4.gfs2_edit restoremeta <dev>
Actual results:
Restored symlink has empty/zeroed contents.
Expected results:
Symlinks should be preserved for file system analysis.
Additional info:
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/RHBA-2018:0668
Description of problem: I got a set of GFS2 metadata from a customer, only to discover the symlinks were all blank. That's because in gfs2_edit's savemeta.c function get_gfs_struct_info it has: (After a special case for saving directories) else if (!inode->i_di.di_height && !block_is_systemfile(owner) && !S_ISDIR(inode->i_di.di_mode)) *gstruct_len = sizeof(struct gfs2_dinode); So savemeta should also save the full contents for symlinks. In this case, we can simply add something like: && !S_ISLNK(inode->i_di.di_mode)) Or some such. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.ln -s /etc/fstab /mnt/gfs2/my_symlink 2.umount /mnt/gfs2 3.gfs2_edit savemeta <dev> 4.gfs2_edit restoremeta <dev> Actual results: Restored symlink has empty/zeroed contents. Expected results: Symlinks should be preserved for file system analysis. Additional info: