#3151 closed bug (fixed)
KDL when copying data between 2 BFS partitions.
| Reported by: | bga | Owned by: | nobody |
|---|---|---|---|
| Priority: | critical | Milestone: | R1/beta2 |
| Component: | System/Kernel | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | olive@…, richienyhus@…, HubertNG@… | |
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description (last modified by )
This may be related to the problme reported on #3150.
I installed Haiku from scratch again to yet another 70 Gb partition and went to move the data from the problematic partition (described on the ticket mentioned above) to the new partition. I was copying my Media folder (with several MP3 files) when I got the attached KDL.
Although it may be related to the other bug mentioned above, there are 2 things that I think are interesting:
1 - The problematic folder described on the other ticket was not involved in this copy at all.
2 - The KDL was in the low resource handler.
Attachments (1)
Change History (14)
by , 16 years ago
comment:1 by , 16 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 16 years ago
| Cc: | added |
|---|
comment:3 by , 16 years ago
| Cc: | added |
|---|
comment:4 by , 16 years ago
comment:6 by , 16 years ago
| Cc: | added |
|---|
comment:7 by , 15 years ago
Reminder: this ticket is blocking alpha 1. Is it still as important, or can it be reassigned to another milestone?
comment:8 by , 15 years ago
| Milestone: | R1/alpha1 → R1 |
|---|---|
| Priority: | blocker → critical |
If it hasn't been fixed yet, it's at least very rare now, so that it's no blocker for the alpha anymore.
comment:10 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:11 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
"Probably fixed" 9 years ago and nobody has seen it since, it seems.
comment:12 by , 5 years ago
| Milestone: | R1 → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Do you remember if you unmounted a volume inbetween?
Because the only fragile looking code in the VFS in this regard is in fs_unmount(); all other code goes through the standard reference counting, and should be safe.