[Gluster-users] cannot write file when gluster 3.6 client mount volume of gluster 3.3

[Justin Clift]

On 25/09/2014, at 10:29 AM, panpan feng wrote:
> hi , Dear experts of gluster,
>      today I have met a problem.   I  install  glusterfs 3.6 beta1 at client  , and mount a volume which 
> servered by glusterfs 3.3 server,  the mount operation success. And I can read file successfully. But
> write operation will failed with error "E72 Close error on swap file".  There are many strange message in log file
> 
> 
> [2014-09-25 05:44:17.659510] W [graph.c:344:_log_if_unknown_option] 0-maintain4-quota: option 'timeout' is not recognized
> 
> [2014-09-25 05:45:26.022305] I [MSGID: 109018] [dht-common.c:715:dht_revalidate_cbk] 0-maintain4-dht: Mismatching layouts for /StorageReport, gfid = 00000000-0000-0000-0000-000000000000
> [2014-09-25 05:45:26.022616] I [dht-layout.c:754:dht_layout_dir_mismatch] 0-maintain4-dht: /StorageReport: Disk layout missing, gfid = 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.022673] I [dht-layout.c:754:dht_layout_dir_mismatch] 0-maintain4-dht: /StorageReport: Disk layout missing, gfid = 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.022973] I [dht-layout.c:754:dht_layout_dir_mismatch] 0-maintain4-dht: /StorageReport: Disk layout missing, gfid = 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.023216] I [dht-layout.c:754:dht_layout_dir_mismatch] 0-maintain4-dht: /StorageReport: Disk layout missing, gfid = 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.023430] I [dht-layout.c:754:dht_layout_dir_mismatch] 0-maintain4-dht: /StorageReport: Disk layout missing, gfid = 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.059022] I [afr-self-heal-metadata.c:41:__afr_selfheal_metadata_do] 0-maintain4-replicate-1: performing metadata selfheal on 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.059208] I [afr-self-heal-metadata.c:41:__afr_selfheal_metadata_do] 0-maintain4-replicate-2: performing metadata selfheal on 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.059238] I [afr-self-heal-metadata.c:41:__afr_selfheal_metadata_do] 0-maintain4-replicate-0: performing metadata selfheal on 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.059281] I [afr-self-heal-metadata.c:41:__afr_selfheal_metadata_do] 0-maintain4-replicate-3: performing metadata selfheal on 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.059594] I [afr-self-heal-metadata.c:41:__afr_selfheal_metadata_do] 0-maintain4-replicate-4: performing metadata selfheal on 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.059783] I [afr-self-heal-metadata.c:41:__afr_selfheal_metadata_do] 0-maintain4-replicate-5: performing metadata selfheal on 4f8abc71-b771-4fc3-b7fa-42ef0ea09dc5
> [2014-09-25 05:45:26.112882] I [dht-layout.c:663:dht_layout_normalize] 0-maintain4-dht: Found anomalies in /StorageReport (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
> [2014-09-25 05:45:26.112903] I [dht-selfheal.c:1065:dht_selfheal_layout_new_directory] 0-maintain4-dht: chunk size = 0xffffffff / 188817468 = 0x16
> [2014-09-25 05:45:26.112915] I [dht-selfheal.c:1103:dht_selfheal_layout_new_directory] 0-maintain4-dht: assigning range size 0x294420dc to maintain4-replicate-4
> [2014-09-25 05:45:26.112928] I [dht-selfheal.c:1103:dht_selfheal_layout_new_directory] 0-maintain4-dht: assigning range size 0x294420dc to maintain4-replicate-5
> [2014-09-25 05:45:26.112937] I [dht-selfheal.c:1103:dht_selfheal_layout_new_directory] 0-maintain4-dht: assigning range size 0x294420dc to maintain4-replicate-0
> [2014-09-25 05:45:26.112945] I [dht-selfheal.c:1103:dht_selfheal_layout_new_directory] 0-maintain4-dht: assigning range size 0x294420dc to maintain4-replicate-1
> [2014-09-25 05:45:26.112952] I [dht-selfheal.c:1103:dht_selfheal_layout_new_directory] 0-maintain4-dht: assigning range size 0x294420dc to maintain4-replicate-2
> [2014-09-25 05:45:26.112960] I [dht-selfheal.c:1103:dht_selfheal_layout_new_directory] 0-maintain4-dht: assigning range size 0x294420dc to maintain4-replicate-3
> The message "I [MSGID: 109018] [dht-common.c:715:dht_revalidate_cbk] 0-maintain4-dht: Mismatching layouts for /StorageReport, gfid = 00000000-0000-0000-0000-000000000000" repeated 5 times between [2014-09-25 05:45:26.022305] and [2014-09-25 05:45:26.023456]
> [2014-09-25 05:45:26.130803] I [MSGID: 109036] [dht-common.c:6221:dht_log_new_layout_for_dir_selfheal] 0-maintain4-dht: Setting layout of /StorageReport with [Subvol_name: maintain4-replicate-0, Err: -1 , Start: 1384661432 , Stop: 2076992147 ], [Subvol_name: maintain4-replicate-1, Err: -1 , Start: 2076992148 , Stop: 2769322863 ], [Subvol_name: maintain4-replicate-2, Err: -1 , Start: 2769322864 , Stop: 3461653579 ], [Subvol_name: maintain4-replicate-3, Err: -1 , Start: 3461653580 , Stop: 4294967295 ], [Subvol_name: maintain4-replicate-4, Err: -1 , Start: 0 , Stop: 692330715 ], [Subvol_name: maintain4-replicate-5, Err: -1 , Start: 692330716 , Stop: 1384661431 ],
> 
> What Can I do to fix this problem?

Interesting.  The guys will definitely want to look at this next week. :)

Regards and best wishes,

Justin Clift

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift