Comment # 266 on bug 1063638 from
(In reply to Samuel DENIS from comment #265)
> Hello,
> 
> I think I am facing this bug with a recent MicroOS install on a really low
> power laptop (a Xiaomi Mi Air 12.5" from 2016). I makes this computer
> totally freeze.
> My only solution is to force power off and restart it, but it doesn't let me
> a lot of time to take any action after reboot (even un recovery mode)
> because the computer freezes quickly.

Unfortunately, latest kernels already have a proper way to skip the heavy
workload at balance time.

So it's unlikely that's the cause.

> 
> I have something like 5 snapshots (I had more but I was able to remove some
> once), maybe 6 or 7. I don't think this is a huge amount of snapshots,
> correct me if I'm wrong.
> 
> I tried to disable quota by running `sudo btrfs quota disable /` but I have
> a "readonly filesystem" error.

This looks like the root cause, by somehow your fs is already corrupted, thus
it looks like your freeze is caused by some kernel crash.

> 
> I leads me to two questions:
> 
> * are quotas required for MicroOS (especially Snapper)?
> * if no, how can I disable quotas?
> 
> Thanks for your help!

Do you have any dmesg when the read-only happens? It's better to open another
BZ for your bug though.


You are receiving this mail because: