Bug 785568 - Marking source with lowest UID fails
Summary: Marking source with lowest UID fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-29 16:01 UTC by Shwetha Panduranga
Modified: 2013-02-22 10:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-22 10:43:16 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
Output of testcase run on a nfs mount (12.26 KB, application/octet-stream)
2012-01-29 16:01 UTC, Shwetha Panduranga
no flags Details

Description Shwetha Panduranga 2012-01-29 16:01:01 UTC
Created attachment 558181 [details]
Output of testcase run on  a nfs mount

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Create a replicate volume with 2 bricks
Start the volume
Mount to volume from the client

Steps to Reproduce:
1.create a file from the mount point
2.change ownership of the file to <someuser>
3.From one of the bricks, change the ownership of the file to <root>
4.ls <filename> from mount point
  
Actual results:
    glusterfs mount:-
 From the mount point, the ownership changes is not reflected for the first time . It still shows the old ownership details. In the backend, on both the bricks the ownership changes has been reflected.

    nfs mount:-
        The changes are reflected on the mount point. But the changes is not reflected on the other brick. 

Expected results:
The ownership of the file should be <root> as seen from the both the bricks and the mount point. 

Additional info: Output of the above testcase from a glusterfs mountpoint:(automation framework logs)

2012-01-27 15:00:30,124 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'client1: Executing Command: cd /mnt/replicate1 ;echo Hello World. testcase: Self-heal - Success Ownership differs > test'
2012-01-27 15:00:45,840 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'client1: Executing Command: cd /mnt/replicate1 ;chown qa:qa test'
2012-01-27 15:01:02,114 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'client1: Executing Command: cd /mnt/replicate1 ;ls -l test'
2012-01-27 15:01:18,402 DEBUG  : /home/shwetha/Testing/automation/libs/utils/atfutils.py print_stdout 94 - '-rw-r--r--. 1 qa qa 61 Jan 27 04:29 test
'

2012-01-27 15:01:18,404 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'server1: Executing Command: cd /export;chown root:root test'
2012-01-27 15:01:34,036 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'server1: Executing Command: cd /export;ls -l test'
2012-01-27 15:01:49,727 DEBUG  : /home/shwetha/Testing/automation/libs/utils/atfutils.py print_stdout 94 - '-rw-r--r--. 1 root root 61 Jan 27 04:29 test
'

2012-01-27 15:01:49,728 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'server2: Executing Command: cd /export;ls -l test'
2012-01-27 15:02:05,814 DEBUG  : /home/shwetha/Testing/automation/libs/utils/atfutils.py print_stdout 94 - '-rw-r--r--. 1 qa qa 61 Jan 27 04:29 test
'
2012-01-27 15:02:05,815 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'client1: Executing Command: cd /mnt/replicate1 ;ls -l test'
2012-01-27 15:02:22,099 DEBUG  : /home/shwetha/Testing/automation/libs/utils/atfutils.py print_stdout 94 - '-rw-r--r--. 1 qa qa 61 Jan 27 04:29 test
'
2012-01-27 15:02:22,100 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'server1: Executing Command: cd /export;ls -l test'
2012-01-27 15:02:38,323 DEBUG  : /home/shwetha/Testing/automation/libs/utils/atfutils.py print_stdout 94 - '-rw-r--r--. 1 root root 61 Jan 27 04:29 test
'
2012-01-27 15:02:38,325 DEBUG  : /home/shwetha/Testing/automation/libs/utils/hostutils.py execute_command 193 - 'server2: Executing Command: cd /export;ls -l test'
2012-01-27 15:02:53,859 DEBUG  : /home/shwetha/Testing/automation/libs/utils/atfutils.py print_stdout 94 - '-rw-r--r--. 1 root root 61 Jan 27 04:29 test

Comment 1 Vijay Bellur 2012-05-18 07:29:06 UTC
Removing target milestone 3.3.0 as the problem observed is a side effect of caching.

Comment 2 Pranith Kumar K 2013-02-22 10:43:16 UTC
Shwetha,
        you could try mounting the volume with
glusterfs --entry-timeout=0 --attribute-timeout=0 -s $H0 --volfile-id=$V0 $M0 --direct-io-mode=enable
Disable stat-prefetch for the volume. This should disable all the caching so that the changes performed on the brick will be visible on the mount point.

Pranith


Note You need to log in before you can comment on or make changes to this bug.