[Bugs] [Bug 1229267] Snapshots failing on tiered volumes (with EC)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1229267

SATHEESARAN <sasundar at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |ASSIGNED
                 CC|                            |sasundar at redhat.com
              Flags|                            |needinfo?(rkavunga at redhat.c
                   |                            |om)



--- Comment #5 from SATHEESARAN <sasundar at redhat.com> ---
(In reply to Mohammed Rafi KC from comment #3)
> I tried to reproduce this issue with latest master code. I'm able to create
> snapshots during an ongoing I/O on mount.
> 
> My test scenario
> 
> 
> volume :>>>>
> 
> Volume Name: patchy
> Type: Tier
> Volume ID: 358a6e6a-c0a2-4e3d-8260-2b83ac28c4b5
> Status: Started
> Number of Bricks: 6
> Transport-type: tcp
> Hot Tier :
> Hot Tier Type : Distribute
> Number of Bricks: 2
> Brick1: 10.70.43.110:/d/backends/3/patchy_snap_mnt
> Brick2: 10.70.43.100:/d/backends/3/patchy_snap_mnt
> Cold Tier:
> Cold Tier Type : Disperse
> Number of Bricks: 1 x (3 + 1) = 4
> Brick3: 10.70.43.100:/d/backends/1/patchy_snap_mnt
> Brick4: 10.70.43.110:/d/backends/1/patchy_snap_mnt
> Brick5: 10.70.43.100:/d/backends/2/patchy_snap_mnt
> Brick6: 10.70.43.110:/d/backends/2/patchy_snap_mnt
> Options Reconfigured:
> cluster.tier-promote-frequency: 10
> cluster.tier-demote-frequency: 10
> cluster.write-freq-threshold: 0
> cluster.read-freq-threshold: 0
> performance.io-cache: off
> performance.quick-read: off
> features.ctr-enabled: on
> performance.readdir-ahead: on
> 
> 
> 
> on mount point>>
> tar -xvf /root/linux-4.1.2.tar.xz
> 
> on server (during I/O)>>
> 
> for i in {1..100} ; do  gluster snapshot create snap$i patchy
> no-timestamp;done;


Rafi,

Moving to bug ON_QA would be valid only if there was an issue, that was fixed
with a patch, and the patch was available on a certain build( as mentioned in
FIXED-IN-VERSION )

If this issue is not reproducible, this bug should be closed as CLOSED -
WORKSFORME.

If there was really a issue, and that was fixed, then provide the patch URL,
and once the patch is available in the build, update FIXED-IN-VERSION and move
this bug to ON_QA

I am moving this bug to ASSIGNED, as there were no new builds available

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=95JLeGko1I&a=cc_unsubscribe