[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 bugzilla at redhat.com
Thu Dec 31 10:11:30 UTC 2015


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



--- Comment #12 from Joseph Elwin Fernandes <josferna at redhat.com> ---
(In reply to Joseph Elwin Fernandes from comment #11)
> (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.

I was able to reproduce this issue. Looking into it. Requesting you to create a
new bug for this issue.

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


More information about the Bugs mailing list