search for: 1564071

Displaying 3 results from an estimated 3 matches for "1564071".

2018 Apr 23
4
Problems since 3.12.7: invisible files, strange rebalance size, setxattr failed during rebalance and broken unix rights
...user reported at least 4 broken directories with some invisible files. The files are at the bricks and don't start with a dot, but aren't visible in "ls". Clients still can interact with them by using the explicit path. More information: https://bugzilla.redhat.com/show_bug.cgi?id=1564071 And since this update gluster reported for the rebalance of >16900 PB (Petabyte!) of data for one of our 2 server, when using ?gluster volume rebalance $myvolume status?. The time looks right, but the size of transfered files is absurd. The rebalance was with 3.12.6 in March 2018. The last reba...
2018 Apr 23
0
Problems since 3.12.7: invisible files, strange rebalance size, setxattr failed during rebalance and broken unix rights
...st 4 broken > directories with some invisible files. The files are at the bricks and > don't start with a dot, but aren't visible in "ls". Clients still can > interact with them by using the explicit path. > More information: https://bugzilla.redhat.com/show_bug.cgi?id=1564071 I will continue the analysis for this issue in the bug. > > > And since this update gluster reported for the rebalance of >16900 PB > (Petabyte!) of data for one of our 2 server, when using ?gluster volume > rebalance $myvolume status?. The time looks right, but the size of &gt...
2018 Apr 23
0
Problems since 3.12.7: invisible files, strange rebalance size, setxattr failed during rebalance and broken unix rights
...st 4 broken > directories with some invisible files. The files are at the bricks and > don't start with a dot, but aren't visible in "ls". Clients still can > interact with them by using the explicit path. > More information: https://bugzilla.redhat.com/show_bug.cgi?id=1564071 > > And since this update gluster reported for the rebalance of >16900 PB > (Petabyte!) of data for one of our 2 server, when using ?gluster volume > rebalance $myvolume status?. The time looks right, but the size of > transfered files is absurd. The rebalance was with 3.12.6 in M...