![](https://seccdn.libravatar.org/avatar/eab7d1c20079e86159e7fc85a12ada68.jpg?s=120&d=mm&r=g)
On Thu, 23 May 2019 09:39:50 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
* Stephen Berman <stephen.berman@gmx.net> [05-23-19 08:16]:
On Thu, 23 May 2019 13:58:39 +0200 "Aaron Digulla" <digulla@hepe.com> wrote:
On Thursday, May 23, 2019 13:14 CEST, Stephen Berman <stephen.berman@gmx.net> wrote:
(3821/4940) Installing: btrfsmaintenance-0.4.2-lp151.1.1.noarch .....................<48%>==============================[-]
Check which processes are running. It's quite possible that the installer script has started some btrfs maintenance (balancing and scrubbing).
Does that apply to a non-root partition? As I mentioned in another reply, Leap is on ext4 but I also have TW on btfs and it's mounted under Leap.
Depending on many factors, this can take half an hour or more. In the mean time, you should see a lot of I/O to your disks.
I don't think there is a lot of I/O, going by the top info I posted in another reply. And the hangup is now more than 90 minutes. Can I safely kill the btrfs-maintenance process? Should I first unmount the btrfs partition? And if I can't?
you probably cannot umount the partition as it will be busy. a reboot would be the only solution. but do you really need that drastic a solution? is the process causing you that much difficulty that you cannot allow it to continue for an hour or two?
I waited 2.5 hours and, since programs in the running system were becoming unusable due to the incomplete installation, decided to kill the btrfs-maintenance process, and immediately the installation proceeded and finished, and I rebooted into Leap 15.1 and it seems to be fine. However,...
next time you do an "install", leave any not absolutely required processes to be added after the install is completed when you can revert changes safely and easily w/o harm, ie: mounting a partition not necessary for the install (easy to add after install completed).
Yes this was a mistake. I've done online upgrades of previous openSUSE installations and if memory serves other systems were mounted and there were no problems, so it didn't occur to me to do otherwise now. But I've also never had a system on btrfs before. After the upgrade to 15.1 completed, I decided to remove the TW mount point, but the YaST partitioner wouldn't let me do it, saying the partition is busy. In my ignorance of btrfs I thought deleting the subvolumes might help, since these are also listed in /etc/fstab. And indeed, after deleting them, I could unmount the partition. But trying to boot TW failed with the error "file `/@/.snapshots/1/snapshot/boot/vmlinuz-5.1.3-1-default' not found." Evidently, deleting the subvolumes in the YaST partitioner blew TW away: I can mount the partition in Leap, but it is virtually empty (it contains the directories /boot, /etc and /usr, but the only nondirectory file is /etc/snapper/configs/root), and running btrfs restore on the unmounted partition saves these files and nothing else. So I have to reinstall TW. Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org