Hi,
While testing 3.5.0-0.1.beta1, came across a bug where file is loosing
flock after add-brick operation. BZ 1055037 is reported for this.
NFS logs from GlusterNode:
[2014-01-18 00:08:37.491971] I [dht-layout.c:727:dht_layout_dir_mismatch]
0-volume2-dht: / - disk layout missing
[2014-01-18 00:08:37.492021] I [dht-common.c:635:dht_revalidate_cbk]
0-volume2-dht: mismatching layouts for /
[2014-01-18 00:08:38.133383] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:08:43.440709] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:08:48.748983] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:08:54.057329] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:08:59.365631] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:09:04.673750] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:09:09.981897] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:09:15.291648] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:09:20.599540] W [nlm4.c:1747:nlm4svc_unlock] 0-nfs-NLM: NLM in
grace period
[2014-01-18 00:09:25.909534] W [nlm4.c:1690:nlm4_unlock_resume] 0-nfs-NLM:
nlm_get_uniq() returned NULL
[2014-01-18 00:09:25.909611] W [nlm4.c:1704:nlm4_unlock_resume] 0-nfs-NLM:
unable to unlock_fd_resume
Thanks,
Lala
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
