#11753 closed bug (fixed)
BFS fails initializing 1.9TB size volume (KDL assert)
Reported by: | kushalsingh007 | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta4 |
Component: | File Systems/BFS | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Initializing a new partition of size 1992294MB caused a KDL assert while formatting the disk and creation partition failed.
Attachments (1)
Change History (10)
by , 10 years ago
Attachment: | Screenshot.png added |
---|
comment:1 by , 10 years ago
Overall, there is several uint32 -> int32 cast in bfs kernel add-on code, fNumBits in AllocationGroup being one exemple.
Here, the assert should be fixed to work on uint32, but there is other place to fix similar issue most probably.
Time to offer a 3TB disk to Axel :)
comment:2 by , 10 years ago
Description: | modified (diff) |
---|---|
Summary: | Partitioning fails at 1.9TB size due to KDL assert → BFS fails initializing 1.9TB size volume (KDL assert) |
comment:3 by , 10 years ago
No need for an actual disk, this can easily be tested in a virtual machine with a sparse HD image.
comment:4 by , 8 years ago
What block size has been used? I've definitely initialized a 3 TB BFS volume already in the past. Has anybody tried to reproduce the issue?
comment:7 by , 2 years ago
Nice catch! Must be an issue with a smaller block size, as this didn't even happen with 8 TB BFS volumes.
comment:8 by , 2 years ago
Well an oversight it seems, the log start can now be in another allocation group. https://review.haiku-os.org/c/haiku/+/5420
Screenshot for the bug has added.