https://bugs.kde.org/show_bug.cgi?id=508845
--- Comment #5 from stellarpower <[email protected]> --- So even for e.g. security patches, are you saying it's up to the package maintainers to cherry-pick lines and merge those in? There aren't occasions where something is severe enough to go back to previous branches and cut a new release for downstream to take up? Just wanting to understand if that is the case as this would differ from some other projects. As of now it's been running for 24 hours for a 600G filesystem, and PM still at 0% complete with no output. I see some occasional disc activity from the check process but mostly sitting with stable RAM on 100% CPU and 0 for the disc. Was this normal for your systems? I get that it's been fixed in later releases but, in any case as an end user, most distros are a year or so behind and this has caused me pretty significant headaches. I have in effect had to take the day off work and do some housekeeping because there's nothing I can really do without my machine waiting for this (hopefully) to run to completion, all for the sake of seeing if a partition can be grown before attempting it. I asked on btrfs reddit what it was doing and (perhaps unsurprisingly) the replies ignored the real question and are mostly just never to run check --repair or you should always have had a backup image before attempting, so without any baseline will just have to see if it's been damaged or not. So I hope somebody somewhere can apply the patch, and would also be worried on the behalf of anyone who uses an older version of PM if it causes them worse issues. Usually when I have a dig out a live USB it's not likely to be that recent as I am only using it for occasional rescues, and that's when you'd definitely want your partition manager not to introduce further problems. -- You are receiving this mail because: You are watching all bug changes.
