| Summary: | partitionmanager crashed on start | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | Pavel ALexeev (aka Pahan-Hubbitus) <pahan> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | mustafa1024m, teo |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 1.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kpmcore/20bb8eba7ec9c57da4e24415e54a3b84909744c1 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Pavel ALexeev (aka Pahan-Hubbitus)
2015-09-29 18:49:08 UTC
This is also triggered in Calamares, it seems to be a KPMcore issue triggered by the presence of a Btrfs volume. We got a full backtrace at https://calamares.io/bugs/browse/CAL-355 Git commit 20bb8eba7ec9c57da4e24415e54a3b84909744c1 by Andrius Štikonas.
Committed on 18/02/2016 at 13:39.
Pushed by stikonas into branch 'master'.
Get btrfs used capacity from btrfs filesystem show --raw
It's output looks like:
Label: 'test' uuid: d23f3138-c8ea-449e-9155-015ce4f6e2e6
Total devices 1 FS bytes used 131072
devid 1 size 981467136 used 252706816 path /dev/sdb1
FS bytes used number is actual data on btrfs volume. However,
to resize successfully we need to know actual space used by data
and metadata. That's why we read size from devid (i.e. 252706816).
Btrfs volumes can span over multiple devices, so we must make sure
that we are reading devid corresponding to the correct device node.
M +2 -2 src/fs/btrfs.cpp
http://commits.kde.org/kpmcore/20bb8eba7ec9c57da4e24415e54a3b84909744c1
*** Bug 351423 has been marked as a duplicate of this bug. *** |