http://bugzilla.opensuse.org/show_bug.cgi?id=1063638
http://bugzilla.opensuse.org/show_bug.cgi?id=1063638#c32
Gabor Katona changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |katonag@gmail.com
--- Comment #32 from Gabor Katona ---
I am also struggling with this bug. It happened several times in the past and I
also face it at this very moment.
The current story: Balancing started yesterday rendering my notebook unusable
(no disk IO but high CPU). Tried a hard reset (again, I have done it in the
past also). The result is a non bootable system, it stops in emergency mode,
root is readonly. Unfortunately I am familiar with this, it happened sevaral
times (although not always). For me the repair is the following. Repeat the
boot-shutdown sequence several times (10, 20, 30, who knows) and once magic,
the system boots. This is what happened yesterday evening. I let the notebook
run whole night for more than 12 hours. But still 50% was left from balancing.
I had to remove the charging to take to work but unfortunately it tried to
sleep. After resume it rebooted (erratic BIOS bug) and started all over,
readonly root, several reboots and now it is "working", which means that btrfs
eats 100% CPU and doesn't respond to btrfs balance cancel.
What should I do to avoid this forever? Should I disable quota? OK, but please
provide info on what to change in snapper (ranges as I read, but how). Or
should I reinstall without using btrfs?
It is simply unacceptable for me that a file system renders a system unusable
for 10-20 hours. Especially when there are file systems that do not do this.
Two remarks:
1. Opensuse should not use btrfs as default. Or not with quotas if this is the
reason. Currently opensuse with btrfs is not even beta, it is unusable.
2. Btrfs doc says that balancing is safe. Well, this is actually totally false.
Balancing is quite unsafe. Maybe someone should change it in the docs.
My system is Tumbleweed with latest updates.
--
You are receiving this mail because:
You are on the CC list for the bug.