Bug 1357357
Summary: | Data loss after RHGS node reboot | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Neha <nerawat> |
Component: | heketi | Assignee: | Luis Pabón <lpabon> |
Status: | CLOSED ERRATA | QA Contact: | Neha <nerawat> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.1 | CC: | annair, hchiramm, lpabon, madam, mliyazud, nerawat, rcyriac, rhs-bugs, sankarshan, sashinde |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS Container Converged 1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-04 04:52:16 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: | |||
Bug Blocks: | 1332128 |
Description
Neha
2016-07-18 04:32:47 UTC
This doesn't look like a Heketi bug, right? Moved it to RHGS GlusterFS container Pointed out by Humble and Ashiq, Heketi needs to use /dev/mapper/... device nodes in the fstab. Luis, Also merge this PR(https://github.com/heketi/heketi/pull/440) to update templates. With latest build: rhgs-server-docker-3.1.3-13 rhgs3-rhgs-volmanager-rhel7-3.1.3-12 Don;t see data loss , also fstab path is changed to /dev/mapper.. cat /var/lib/heketi/fstab /dev/mapper/vg_5d59ca08593a21a0b5932315de85c919-brick_2b982a20aff0c7db0c1874463d44478b /var/lib/heketi/mounts/vg_5d59ca08593a21a0b5932315de85c919/brick_2b982a20aff0c7db0c1874463d44478b xfs rw,inode64,noatime,nouuid 1 2 /dev/mapper/vg_5d59ca08593a21a0b5932315de85c919-brick_9298bd4e5943fdb859cce104643f9cb7 /var/lib/heketi/mounts/vg_5d59ca08593a21a0b5932315de85c919/brick_9298bd4e5943fdb859cce104643f9cb7 xfs rw,inode64,noatime,nouuid 1 2 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://rhn.redhat.com/errata/RHBA-2016-1498.html |