[Bugs] [Bug 1129939] NetBSD port

bugzilla at redhat.com bugzilla at redhat.com
Thu May 7 11:37:59 UTC 2015


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



--- Comment #331 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10411 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit aa938247e19afa419476fb2d0b7cb2d054c6dd47
Author: Emmanuel Dreyfus <manu at netbsd.org>
Date:   Wed Apr 29 15:52:37 2015 +0200

    Tests: use a portable way to flush kernel cache

    On Linux, kernel cache can be flushed using
    echo 3 > /proc/sys/vm/drop_caches

    This non-portable approach can be replaced by an on-purpose
    failed attempt to unmount: if the mount point is the current
    directory and umount is called, the kernel will flush inodes
    until it realize it cannot complete the operation because
    root of filesystem is busy:
    ( cd $M0 ; umount $M0 )

    Unfortunately this does not flush everything. Entries may
    still be present in the kenrel FUSE cache. Using $GFS to
    mount the filesystem ensure --entry-timeout=0 and clears
    this problem.

    Some stall information may also remain in glusterfs caches,
    and that may have to be adressed by appropriate volume option.
    For instance tests/bugs/rpc/bug-954057.t needs to disable
    performance.stat-prefetch. Qtherwise, root's new credentials
    are not evaluated after root-quash is enabled. The test could
    also be done with performance.stat-prefetch enabled using
    various tricks: copying the file to read, creating a hard link
    on it, or just waiting long enough for metadata cache to expire.

    BUG: 1129939
    Change-Id: I54929e899d55c04dcd9d947809133549f01fd0e1
    Signed-off-by: Emmanuel Dreyfus <manu at netbsd.org>
    Reviewed-on: http://review.gluster.org/10411
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Bugs mailing list