Red Hat Bugzilla – Bug 171548
Cannot use my 5.6 TB holding disk: it has negative size
Last modified: 2015-01-07 19:11:03 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.7.10-1.3.2 Description of problem: Moving to a new machine with more disk space, amanda broke because it could not use the new holding disk: "amcheck" reports negative free space size. Version-Release number of selected component (if applicable): amanda-2.4.4p3-1.x86_64 How reproducible: Always Steps to Reproduce: 1. blah... 2. 3. Actual Results: -bash-3.00$ /usr/sbin/amcheck -s daily Amanda Tape Server Host Check ----------------------------- WARNING: holding disk /amanda_daily_holding: only -2147483648 KB free (4284481536 KB requested) amcheck-server: slot 5: date X label daily0005 (new tape) NOTE: skipping tape-writable test Tape daily0005 label ok Server check took 0.068 seconds -bash-3.00$ df -k /amanda_daily_holding Filesystem 1K-blocks Used Available Use% Mounted on /dev/md2 5382870976 1264819472 4016416084 24% /home1 Additional info: amanda-2.4.5 rebuilt from sources shows the same problem. The wrong size of the holding disk seems to be caused by an overflow(?) in common-src/statfs.c. After replacing: -bash-3.00$ diff statfs.c statfs.c~ 130c130 < #define scale(r,s) ( (r) == -1? -1 : ((double)(r)*(double)(s)/1024.0) ) --- > #define scale(r,s) ( (r) == -1? -1 : (int)((r)*(double)(s)/1024.0) ) The problem goes away and amanda works fine.
The component this request has been filed against is not planned for inclusion in the next update. The decision is based on weighting the priority and number of requests for a component as well as the impact on the Red Hat Enterprise Linux user-base: other components are considered having higher priority and the number of changes we intend to include in update cycles is limited.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.