On 23/05/2019 23.23, Stephen Berman wrote:
On Thu, 23 May 2019 22:28:41 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 23/05/2019 22.05, Stephen Berman wrote:
On Thu, 23 May 2019 18:49:13 +0200 "Carlos E. R." <> wrote:
On 23/05/2019 13.53, Stephen Berman wrote:
On Thu, 23 May 2019 13:40:06 +0200 "Carlos E. R." <> wrote:
On 23/05/2019 13.33, Stephen Berman wrote: > On Thu, 23 May 2019 13:18:43 +0200 "Carlos E. R." <> wrote:>>> The root > file system for Leap is ext4 (on the same machine I also > installed TW on btrfs). ps afxu | grep -i btrfs shows this:
...
And apparently, you have it mounted.
Yes.
Unlucky.
Yes, me would have, perhaps, umounted it before starting the procedure, because /I/ knew about this possible problem. I reported it months ago on a virtual machine, but we could not reproduce it and find out what caused it (it happens randomly, and so far, not to the people that can study it).
Why would a normal person umount other partitions, there is no reason really. And the install procedure /might/ install things appropriate for those mounts or apply configs or who knows.
Yes, as I wrote in my followup to Patrick Shanahan, I've done online upgrades with other mounted partitions, but never btrfs partitions. After I looked through the bug reports, I thought it was rather irresponsible that no mention of this is on the upgrade web page, which I was following.
Yes, there should be a note; maybe few people have seen this problem and the people writing them were not aware. You could open a bugzilla on that documentation or release notes issue.
Since the issue has been known for so long, even if it's not reliably reproducible, and still wasn't deemed worth mentioning on the upgrade page, I doubt opening a bug it will change that. But maybe I'll try anyway.
Yes, someone has to ask the note to be written. I could have been me, but I forgot. The thing is, you can do it a thousand times and it doesn't happen, so you think it has disappeared, and then another person says it happened to him :-(
Next time, umount it with the option "--lazy", then wait patiently.
"lsof" may tell you what program is using it.
Thanks. Live and learn.
Welcome. Yes, it is called experience. I have experienced a bunch of disasters. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)