Opened 17 years ago
Closed 17 years ago
#1928 closed bug (fixed)
Initializing of a partition only succeeds if it's no BFS partition already
| Reported by: | axeld | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/alpha1 |
| Component: | Kits/Storage Kit | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
If you have a BFS partition that you want to initialize again using DriveSetup, it will fail with B_ERROR.
The reason is that "initialize" itself is only called when the partition type differs, which is apparently not the case here. Calling the other methods just fail.
Change History (3)
comment:1 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 17 years ago
Note:
See TracTickets
for help on using tickets.
Situation improved with hrev24419: the initialization job is now created, but _kern_initialize_partition() now returns B_BUSY.