[Bugs] [Bug 1760399] WORMed files couldn't be migrated during rebalancing

[bugzilla at redhat.com]

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



--- Comment #2 from Mohit Agrawal <moagrawa at redhat.com> ---
Hi,

   Yes he is right.To know about the client at server xlators we check the pid
value if pid 
   is negative it means the fop request has come from an internal client
otherwise request has
   come from an external client.    

    Below are the total defined pid's those we use as a internal pid

    >>>>>>>>>>>>>>>>>>>>>

    GF_CLIENT_PID_MAX = 0,
    GF_CLIENT_PID_GSYNCD = -1,
    GF_CLIENT_PID_HADOOP = -2,
    GF_CLIENT_PID_DEFRAG = -3,
    GF_CLIENT_PID_NO_ROOT_SQUASH = -4,
    GF_CLIENT_PID_QUOTA_MOUNT = -5,
    GF_CLIENT_PID_SELF_HEALD = -6,
    GF_CLIENT_PID_GLFS_HEAL = -7,
    GF_CLIENT_PID_BITD = -8,
    GF_CLIENT_PID_SCRUB = -9,
    GF_CLIENT_PID_TIER_DEFRAG = -10,
    GF_SERVER_PID_TRASH = -11,
    GF_CLIENT_PID_ADD_REPLICA_MOUNT = -12

    >>>>>>>>>>>>>>>>>>>>>>>>

    To avoid the client_pid assign to internal pid we have to put some
conditional checks in 
    set_fuse_mount_options so that user would not be able to assign any defined
internal 
    pid to the fuse process and on the server-side we need to validate pid
value should be less than 0 
    and greater than -12.

    I have included a raw patch(specific to worm xlator only) but the same we
need to 
    update in other xlator also.  I will upload the complete patch.

Thanks,
Mohit Agrawal

-- 
You are receiving this mail because:
You are on the CC list for the bug.