[Bugs] [Bug 1291566] first file created after hot tier full fails to create, but gets database entry and later ends up as a stale erroneous file (file with ???????????)

[bugzilla at redhat.com]

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



--- Comment #11 from Joseph Elwin Fernandes <josferna at redhat.com> ---
(In reply to nchilaka from comment #8)
> Following is my finding on the latest build(where the fix is supposed to be
> availbale):[root at zod dummy]# rpm -qa|grep gluster
> glusterfs-api-3.7.5-13.el7rhgs.x86_64
> glusterfs-client-xlators-3.7.5-13.el7rhgs.x86_64
> glusterfs-server-3.7.5-13.el7rhgs.x86_64
> glusterfs-3.7.5-13.el7rhgs.x86_64
> glusterfs-cli-3.7.5-13.el7rhgs.x86_64
> glusterfs-debuginfo-3.7.5-12.el7rhgs.x86_64
> glusterfs-libs-3.7.5-13.el7rhgs.x86_64
> glusterfs-fuse-3.7.5-13.el7rhgs.x86_64
> [root at zod dummy]# 
> 
> 
> I used the same steps to validate and found the following
> observations/issues:
> (refer the steps mentioned at the beginning) 
> 1) at step 3 and 4, now when I create a file and it exceeds the disk
> capacity previously it used to fail out after the disk limit is hit saying
> input/output error, But now I don't see that happening, instead the mount
> point hangs there. A CLEAR CASE OF REGRESSION

  Suggest you to create a new bug for this.

> 
> 2)Keeping the state as it is, I opened another terminal of same client and
> now tried step 5  and following is what i see:
>   a) the database entry is made for the file even though file create fails
> as below:
> [root at rhs-client1 bztest]# touch x1
> touch: cannot touch ‘x1’: No space left on device
> [root at rhs-client1 bztest]# ls
> gogy5  gogy7  gogy8  gony  leg1  leg2  leg3  leg4  leg5  new1  new2  new3 
> new4  tile1  tile2  tile3  tile4  x10  x2  x3  x4  x5  x6  x7  x8  x9
> 
> ====>database entry is there <========================
> 
> >>>>>>>>>>>> HOTBRICK#2 <<<<<<<<==
> cd1833b2-abfe-446a-8090-87abba9a7a6c|1450961884|272248|0|0|0|0|0|0|0|0
> de8c1aad-8b0f-46dd-8890-9c6af4588b5e|1450962132|339551|0|0|0|0|0|0|0|0
> 5ba281ad-e194-4d75-a0b3-f68bd409020a|1450962204|62682|0|0|0|0|0|0|0|0
> cd1833b2-abfe-446a-8090-87abba9a7a6c|00000000-0000-0000-0000-
> 000000000001|new1|0|0
> de8c1aad-8b0f-46dd-8890-9c6af4588b5e|00000000-0000-0000-0000-
> 000000000001|x2|0|0
> 5ba281ad-e194-4d75-a0b3-f68bd409020a|00000000-0000-0000-0000-
> 000000000001|x1|0|0
> ###############################
> Thu Dec 24 18:37:48 IST 2015
> /dummy/brick101/bztest_hot:
> 
> 
> 
> b)however, I don't see the file getting created.
> 
> 
> Conclusion: It is a partial fix

 This is a clear issue of recording in the wind path and not the unwind path.
This cannot be fixed right now as it would require substantial code change in
CTR. Even this bug https://bugzilla.redhat.com/show_bug.cgi?id=1289118 was
deferred for the same reason.

-- 
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=XcgPTb7bWu&a=cc_unsubscribe