Back to bug 1000992

Who When What Removed Added
krishnan parthasarathi 2013-08-27 04:54:46 UTC CC kparthas
Assignee amarts kdhananj
krishnan parthasarathi 2013-08-27 05:08:54 UTC Status NEW POST
Krutika Dhananjay 2013-08-29 09:10:41 UTC Status POST MODIFIED
Krutika Dhananjay 2013-09-03 05:55:05 UTC Status MODIFIED ON_QA
Vivek Agarwal 2013-10-03 08:57:54 UTC Keywords ZStream
Fixed In Version glusterfs-3.4.0.33rhs-1
Gowrishankar Rajaiyan 2013-10-03 10:00:39 UTC CC grajaiya
QA Contact sdharane saujain
Vivek Agarwal 2013-10-08 08:44:54 UTC Fixed In Version glusterfs-3.4.0.33rhs-1 glusterfs-3.4.0.34rhs
Saurabh 2013-10-08 12:55:31 UTC Status ON_QA VERIFIED
Krutika Dhananjay 2013-10-09 09:13:56 UTC Doc Text Cause:
The auto variable used to hold the quota limits was not initialised and hence held junk value, which was subsequently written to the xattr of the directory.

Consequence:
The junk value is written to the glusterfs.quota.limit-set xattr in the backend for the directory on which it is desired to set the hard limit. The same junk value is therefore displayed in the output of 'quota list'.

Fix:
Initialised the auto variable to all zeroes before using it.

Result:
Now the correct value of the soft-limit is displayed in the output of 'quota list'.
Vivek Agarwal 2013-11-08 08:51:59 UTC Priority unspecified high
Krutika Dhananjay 2013-11-12 10:52:43 UTC Doc Text Cause:
The auto variable used to hold the quota limits was not initialised and hence held junk value, which was subsequently written to the xattr of the directory.

Consequence:
The junk value is written to the glusterfs.quota.limit-set xattr in the backend for the directory on which it is desired to set the hard limit. The same junk value is therefore displayed in the output of 'quota list'.

Fix:
Initialised the auto variable to all zeroes before using it.

Result:
Now the correct value of the soft-limit is displayed in the output of 'quota list'.
Cause:
This bug results from not initialising variables appropriately before using them.

Consequence:
The junk value is written to the glusterfs.quota.limit-set xattr in the backend for the directory on which it is desired to set the hard limit. The same junk value, therefore, gets displayed in the output of 'quota list'.

Fix:
Initialised the local variable to all zeroes before using it.

Result:
Now the correct value of the soft-limit is displayed in the output of 'quota list'.
errata-xmlrpc 2013-11-27 15:33:28 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2013-11-27 10:33:28 UTC
John Skeoch 2016-01-19 06:12:43 UTC CC mzywusko

Back to bug 1000992