According to the LVM documentation, the thin pool will become read-only for
operations that require a change to metadata in the event of the metadata
volume becoming exhausted. It seems I was lucky enough to experience the
system failure prior to data loss occurring (although that would have cost
On Fri, April 13, 2018 12:33 am, Pablo Di Noto wrote:
> Ah! The joy! Now back to R4.0 without massive reinstall.
>
>
> Thanks Marek, awokd and techg...!
I think you taught me more than I helped on this one! Thanks for sharing
your resolution.
--
You received this message because you are
> > > > You could also try to revert to earlier revision using "qvm-volume
> > revert sys-net:private" for example.
>
> Will try that tonight.
>
Unfortunately, that was not possible for the service VMs.
For the only important AppVM that had -back and -back missing, the command
`qvm-block
Check for Meta% above 80%
On Thu, 12 Apr 2018 at 21:21 awokd wrote:
> On Thu, April 12, 2018 3:20 am, techgee...@gmail.com wrote:
> > On Wednesday, 11 April 2018 08:29:48 UTC+12, Pablo Di Noto wrote:
> >
> >> Hello,
> >>
> >>
> >> Any debugging tips?
> >>
> >
> > You have
> > > If, as I suspect, the root cause of your problem is a lack of metadata
> > > space on pool00; you can confirm this by typing "sudo lvs" into a
> > > console. You will then need to figure out a way to enlarge that metadata
> > > volume.
> >
> > Yes, you are right, the `pool00` volume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Apr 12, 2018 at 08:19:10AM -0700, Pablo Di Noto wrote:
> > techg...@gmail.com
> > If, as I suspect, the root cause of your problem is a lack of metadata
> > space on pool00; you can confirm this by typing "sudo lvs" into a console.
> >
On Thu, April 12, 2018 3:20 am, techgee...@gmail.com wrote:
> On Wednesday, 11 April 2018 08:29:48 UTC+12, Pablo Di Noto wrote:
>
>> Hello,
>>
>>
>> Any debugging tips?
>>
>
> You have almost exactly described my scenario.
>
>
> You can work around the TypeError exception by editing
>