Quoting [email protected]:
Qubes 4.1 (in development) has added a warning (in addition to the current
lvm space usage warning) for lvm metadata usage above a threshold. 4.0
doesn't have the metadata nearing full warning, and that's what tends to
cause these types of thinpool issues.
In addition to the warning, Qubes 4.1 is also doubling (vs. the lvm default
value) the amount of space set aside for lvm thinpool metadata which will
substantially reduce the chances of ever hitting this issue under 4.1.
Brendan
PS - above is not helpful for recovering this machine, of course. However,
recovery from this can be very difficult and even after recovery not
guaranteed to recover all the data. The Qubes devs are aware of this and
very much want to avoid these issues in the next release.
Hm, yes, this does not help:/
What about running fstrim on the ssd and try booting again?
@brendan: I've seen that you had some thoughts about lvm in some postings,
so would you care to elaborate/brainstorm on the situation i
described, you know, every input is valuable right now :)
--
You received this message because you are subscribed to the Google
Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/54c72ea0-be0b-4414-bc01-7fee409b7c73%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20200311023413.Horde.IOwm_GtrdCIkVGTGfYLkNA1%40webmail.df.eu.
