[Bugs] [Bug 1297280] tar on a glusterfs mount displays " file changed as we read it" even though the file was not changed
bugzilla at redhat.com
bugzilla at redhat.com
Mon Aug 13 12:49:08 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1297280
Arie Skliarouk <skliarie+redhat-bugzilla at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |skliarie+redhat-bugzilla at gm
| |ail.com
--- Comment #17 from Arie Skliarouk <skliarie+redhat-bugzilla at gmail.com> ---
The bug is still relevant on glusterfs 3.13 (as shipped in ubuntu PPA).
I traced it to different timestamps of file replicas (it looks like glusterfs
returns timestamp of the real file from local node):
stat on the first replica:
root at tframe0-atl:~# stat
/mnt/opsfs/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz
/mnt/opsfs-tf0/BRICK/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz
File: '/mnt/opsfs/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz'
Size: 19090142 Blocks: 37286 IO Block: 131072 regular file
Device: 8ah/138d Inode: 9964002487893152032 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 999/ ops) Gid: ( 999/ ops)
Access: 2018-08-13 00:00:03.059002452 +0000
Modify: 2018-07-06 13:28:10.768794322 +0000
Change: 2018-07-06 13:28:14.340859975 +0000
Birth: -
File: '/mnt/opsfs-tf0/BRICK/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz'
Size: 19090142 Blocks: 37296 IO Block: 4096 regular file
Device: fc02h/64514d Inode: 1187765 Links: 2
Access: (0664/-rw-rw-r--) Uid: ( 999/ ops) Gid: ( 999/ ops)
Access: 2018-08-13 00:00:03.059002452 +0000
Modify: 2018-07-06 13:28:10.768794322 +0000
Change: 2018-07-06 13:28:14.340859975 +0000
Birth: -
stat on the second replica:
root at tframe1-atl:~# stat
/mnt/opsfs/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz
/mnt/opsfs-tf0/BRICK/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz
File: '/mnt/opsfs/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz'
Size: 19090142 Blocks: 37286 IO Block: 131072 regular file
Device: b8h/184d Inode: 9964002487893152032 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 999/ ops) Gid: ( 999/ ops)
Access: 2018-07-06 13:28:07.736870120 +0000
Modify: 2018-07-06 13:28:10.768794322 +0000
Change: 2018-07-06 13:28:14.340980075 +0000
Birth: -
stat: cannot stat
'/mnt/opsfs-tf0/BRICK/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz': No such
file or directory
root at tframe1-atl:~# stat
/mnt/opsfs/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz
/mnt/opsfs-tf1/BRICK/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz
File: '/mnt/opsfs/db/CMTS/CMTS_MnB-101824/CMTS_MnB-101824.tar.gz'
Size: 19090142 Blocks: 37286 IO Block: 131072 regular file
Device: b8h/184d Inode: 9964002487893152032 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 999/ ops) Gid: ( 999/ ops)
Access: 2018-07-06 13:28:07.736870120 +0000
Modify: 2018-07-06 13:28:10.768794322 +0000
Change: 2018-07-06 13:28:14.340980075 +0000
Birth: -
After I reset timestamp of real file to be the same, the tar stopped
complaining.
IMHO, glusterfs must self-heal the timestamp in such cases.
--
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=0anrh27864&a=cc_unsubscribe
More information about the Bugs
mailing list