Closed Bug 512994 Opened 16 years ago Closed 16 years ago

Deleting / recreating the updates/0 directory puts the filesystem into a weird state

Categories

(Toolkit :: Application Update, defect, P1)

1.9.2 Branch
ARM
Windows CE
defect

Tracking

()

RESOLVED FIXED
mozilla1.9.2b1
Tracking Status
status1.9.2 --- beta1-fixed

People

(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)

References

Details

Attachments

(1 file)

I've seen this happen a lot in emulators and also on the Tegra. When the dir is deleted and immediately recreated the dir can't be opened or deleted without restarting the OS.
Attached patch patch rev1Splinter Review
There doesn't seem to be a good reason to do this on any platform.
Assignee: nobody → robert.bugzilla
Status: NEW → ASSIGNED
Attachment #397023 - Flags: review?(dtownsend)
(In reply to comment #1) > Created an attachment (id=397023) [details] > patch rev1 > > There doesn't seem to be a good reason to do this on any platform. There doesn't seem to be a good reason NOT to do this on all platforms.
(In reply to comment #1) > There doesn't seem to be a good reason to do this on any platform. Please excuse the hand wavyness, but is the handling of status files, mar's, etc robust enough that we'll be OK without wiping updates/0 frequently ?
We already enumerate the files in the dir and delete them one by one with the exception of the last update log which was copied (now moved) to the parent dir. If we have trouble deleting them individually we'll have trouble deleting the directory as well.
Attachment #397023 - Flags: review?(dtownsend) → review+
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a1
Unrelated to NT ghosting a deleted directory until all its handles are closed?
Likely something along those lines. I found that exiting Firefox on the Tegra or exiting Fennec on an emulator didn't fix it and the OS had to be restarted. I talked with dougt about it and filed bug 513051 to try to find the underlying issue.
Attachment #397023 - Flags: approval1.9.2?
Attachment #397023 - Flags: approval1.9.2? → approval1.9.2+
Keywords: fixed1.9.2
Target Milestone: mozilla1.9.3a1 → mozilla1.9.2b1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: