This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 143739 - Incorrect available disk space determination in some cases
Summary: Incorrect available disk space determination in some cases
Status: VERIFIED FIXED
Alias: None
Product: installer
Classification: Unclassified
Component: NBI (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: dlipin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-13 11:04 UTC by igor_nikiforov
Modified: 2008-08-14 09:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description igor_nikiforov 2008-08-13 11:04:17 UTC 
If installation location coincides with one of file system roots then / will be used as root for it and available disk
space will be determined incorrectly. I.e., we are going to install NetBeans to /mnt/test directory which is one of the
file system roots. It's capacity is 200 MB that is not enough for installation, but installer uses / file system root to
check free space available and allows installation to /mnt/test. Of course, it will fail. Summing it up,
FileUtils.getRoot(...) method algorithm is not greedy enough to get the right root in some cases.
Comment 1 dlipin 2008-08-13 18:23:53 UTC 
Please provide more info. at least, please attach installation log file, /proc/mounts, output of "df -k" and "mount" 
commands.
Any test case to reproduce with the exact steps... afaik all the methods works correctly.
is there any system that I can check that scenario?
Comment 2 dlipin 2008-08-13 20:56:58 UTC 
Oh... sorry, I read your description the second time and got the issue.
I`ll check - likely the fix is trivial...
Comment 3 dlipin 2008-08-13 21:10:50 UTC 
Fixed: http://hg.netbeans.org/main/rev/e14e5e8ac4cc

Igor, please verify ASAP.

Thanks for reporting the issue! Good catch!
Comment 4 igor_nikiforov 2008-08-14 09:12:02 UTC 
I've verified the fix. Everything seems to be fine. Thanks.