Branch build 2000-10-13-09MN6: NT4 Overview: No alert appears during migration if the system is out of disk space. Regression since this was a problem and was fixed in bug# 36249. The following is what occured which prompted me to check for disk space: - I was in mail, created a new account and noticed that no expander widget appeared next to the account level. - Exited and tried to migrate another profile. The conversion window appeared and quickly disappeared. Navigator never opened so it appeared that migration didn't occur. - Exited again and restarted Profile Manager and attempted to create a new profile. I got as far as the Profile Manager window asking for the profile name. I entered the new name, selected the Finish button but the window never closed. Actual Results: After freeing up some disk space then everything worked. Expected Results: An alert should appear, especially during migration or creation of a profile, to warn that you are running out of disk space.
Setting to rtm because I would like more people looking at this for consideration.
Keywords: regression, rtm
The bug summary sounds innocuous. Are you saying (in the description) that you hang if you run out of space? If it's just a missing alert with no other ill-effects this isn't possibly an rtm candidate.
You're right that it does not crash but a novice user won't have a clue that they could be running low on disk space.
Well, in some instances (probably dependent on how much space is left on disk?) it will indeed bring up the alert telling you of the low disk space condition preventing migration. I suggest we release note this for the cases where it won't alert a user.
I'm not sure why you didn't get the message about there not being enough space to migrate on the second migration Ninoschka. Can you check to see if that profile exists in your Users50 tree? The reason I ask is that there may have been enough room to migrate a small profile but your disk is so full that some other operations (like those you were doing in Mail in the first place) may be affected by it.
Info Note: In my instances, when I migrated and DIDN'T get warned about low disk space, I'd just cleaned up user50 files and registry/mozregistry. So I did not have an existing profile in user50. I was extremely low on space, tried to migrate then didn't get any alert. I exited the profile picker/mgr dialog, then freed up 100K or so then tried again for the same profile without having cleaned up files/registry in between. Then I DID get the alert.
I think we have to release note this: "Sometimes Netscape 6 may appear to hang during profile migration if there is insufficient disk space. Free up space the the product should continue"
FYI, for clarification on release notes: No, it doesn't appear to hang. It just doesn't do anything. You can still use the profile manager, so it's not a hang-like state. It just sits there and doesn't give you any feedback and doesn't do anything.
This should be part of the general "We can't cope if you run out of disk space, sorry" relnote. Gerv
Whiteboard: [rtm-] → [rtm-] relnote-user
I tested this with build 2002020403 and got a message about being low on disk space- however it started the migration and proceeded to copy the files until it ran out of space instead of computing disk space requirements before the process started. I had to clean up disk, remove partially migrated profile, clean profiles etc - something a user may not know how to do changing assignee Bhuvan, if you are no longer handling migration- please reassign
Assignee: dbragg → racham
*** Bug 143026 has been marked as a duplicate of this bug. ***
Assignee: racham → sspitzer
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
the bug description should maybe be updated to reflect that this bug is about migration only or maybe the concept of having an alert about diskspace should be extended to the all application ?
3 years ago
This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE. If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.
No longer blocks: 1243899
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.