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.
Bug 1696876 - stratisd does not properly update the MDV when a filesystem is extended
Summary: stratisd does not properly update the MDV when a filesystem is extended
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: stratisd
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: mulhern
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-05 20:19 UTC by Todd Gill
Modified: 2021-09-06 15:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:04:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3414 0 None None None 2019-11-05 21:05:23 UTC

Description Todd Gill 2019-04-05 20:19:01 UTC 
Description of problem:

When stratisd extends the thin device, it does not update the MDV.  When the system is rebooted - stratisd reconstructs the DM table with the wrong length.  The problem causes the filesystem to fail mounting.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Create a pool with more than 1TB
2. Create a filesystem in the pool - mount it
3. Write more than 1TB to the filesystem
4. Reboot
5. Attempt to mount the filesystem

Actual results:

Filesystem fails to mount - fail to read superblock

Expected results:

Filesystem mounts cleanly

Additional info:

https://github.com/stratis-storage/stratisd/issues/1474
Comment 1 mulhern 2019-04-17 13:21:24 UTC 
upstream issue: https://github.com/stratis-storage/stratisd/issues/1474.
Comment 3 Jakub Krysl 2019-07-31 07:33:34 UTC 
# rpm -qa stratisd
stratisd-1.0.4-2.el8.x86_64

# lsblk
NAME                                                                                        MAJ:MIN RM   SIZE RO TYPE    MOUNTPOINT
sda                                                                                           8:0    0   9.1T  0 disk
└─stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-physical-originsub                     253:0    0   9.1T  0 stratis
  ├─stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-thinmeta                        253:1    0   9.3G  0 stratis
  │ └─stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-thinpool-pool                      253:3    0   9.1T  0 stratis
  │   └─stratis-1-c6ad7e9f3415498899dba1e15feb1ec6-thin-fs-277a28d0ede943daab9bbaf0b7a8761b 253:5    0     2T  0 stratis /root/stratis
  ├─stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-thindata                        253:2    0   9.1T  0 stratis
  │ └─stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-thinpool-pool                      253:3    0   9.1T  0 stratis
  │   └─stratis-1-c6ad7e9f3415498899dba1e15feb1ec6-thin-fs-277a28d0ede943daab9bbaf0b7a8761b 253:5    0     2T  0 stratis /root/stratis
  └─stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-mdv                             253:4    0    16M  0 stratis

# stratis fs
Pool Name  Name  Used      Created            Device            UUID
test       fs    1.05 TiB  Jul 29 2019 14:56  /stratis/test/fs  277a28d0ede943daab9bbaf0b7a8761b

# dmsetup table
stratis-1-c6ad7e9f3415498899dba1e15feb1ec6-thin-fs-277a28d0ede943daab9bbaf0b7a8761b: 0 4294967296 thin 253:3 0
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-thinpool-pool: 0 19513270272 thin-pool 253:1 253:2 2048 8425322 3 skip_block_zeroing no_discard_passdown error_if_no_space
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-physical-originsub: 0 19532865536 linear 8:0 8192
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-thindata: 0 1572864 linear 253:0 65536
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-thindata: 1572864 19511697408 linear 253:0 21168128
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-mdv: 0 32768 linear 253:0 1638400
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-thinmeta: 0 32768 linear 253:0 0
stratis-1-private-c6ad7e9f3415498899dba1e15feb1ec6-flex-thinmeta: 32768 19496960 linear 253:0 1671168


Rebooting the system does not cause any issues on mounting any more.
Comment 6 errata-xmlrpc 2019-11-05 21:04:23 UTC 
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-2019:3414
Note You need to log in before you can comment on or make changes to this bug.