[Bugs] [Bug 1235990] quota: marker accounting miscalculated when renaming a file on with write is in progress

bugzilla at redhat.com bugzilla at redhat.com
Thu Jul 2 11:26:50 UTC 2015


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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11425 committed in release-3.7 by Raghavendra
G (rgowdapp at redhat.com) 
------
commit 2bf6e683e88517c1b2c6c8b13ab681bfdb0acacc
Author: vmallika <vmallika at redhat.com>
Date:   Thu Jun 25 14:58:50 2015 +0530

    quota: marker accounting goes bad with rename while writing a file

    This is a backport of http://review.gluster.org/#/c/11403/

    > With below test-case, marker accounting becomes bad:
    > 1) Create a volume with 1 brick
    > 2) fuse mount
    > 3) on one terminal write some data
    >    dd if=/dev/zero of=f1 bs=1M count=500 oflag=sync
    > 4) on another terminal execute below rename operation while the write is
    > still in progress
    >     for i in {1..50}; do
    >         ii=`expr $i + 1`;
    >         mv f$i f$ii;
    >     done
    >
    > remove-xattr is already on while doing rename operation,
    > we should not be doing again in background when reducing the
    > parent size.
    >
    > Change-Id: I969a64bb559e2341315928b55b99203e9ddee3f2
    > BUG: 1235195
    > Signed-off-by: vmallika <vmallika at redhat.com>
    > Reviewed-on: http://review.gluster.org/11403
    > Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    > Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    > Tested-by: Gluster Build System <jenkins at build.gluster.com>
    > Tested-by: Raghavendra G <rgowdapp at redhat.com>

    Change-Id: Ic37c7f7bd74093ee7e155b305834dbc1fdd24b10
    BUG: 1235990
    Signed-off-by: vmallika <vmallika at redhat.com>
    Reviewed-on: http://review.gluster.org/11425
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>

-- 
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=nIdQ7lVs0c&a=cc_unsubscribe


More information about the Bugs mailing list