Re: Re: [qubes-users] Re: Write-error on swap-device after having a full storage

[Steve Coleman]

On 2020-01-23 04:08, Vít Šesták wrote:
*APL external email warning: *Verify sender 
qubes-users+bncbct5hvg33eerbeofuxyqkgqeaao4...@googlegroups.com before 
clicking links or attachments


Thank you! This has allowed me to mount the volume to a DVM, which has 
allowed me to fix the issue. Just running fsck in the DVM was enough to 
fix the issue.


Maybe I should create an issue (or find an existing one) for that.


Maybe we should just wrap that set of commands into a script to make it 
quick and easy?


Something like:

$ qvm-mount-lvm-image AppVM remote-mount-point thin-pool-volume-name1

Being a belt and suspenders kind, I would use it on a regular basis just 
to grab a diff for any changes to the persistent areas like /rw/usrLocal 
in specific internet facing VMs after shutdown.


If you ever have an AppVM get hacked, there are only so many places that 
offer persistence within an AppVM, so I would like to launch a dispvm 
every so often just to roll through each private volume to hash check 
that set of directories and compare the new checksums to any prior 
stored values.  This way when something touches the /usr/local I will 
know about it.


It would also be a good idea to measure places like the users special 
areas like .config/ .local/bin looking specifically for executables that 
might be launched automatically without the users own knowledge.



Regards,
Vít Šesták 'v6ak'


--
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3c01c7e5-1c42-4b7d-5ff8-631c7fde37e0%40jhuapl.edu.

Re: [qubes-users] Re: Write-error on swap-device after having a full storage

[Vít Šesták]

Thank you! This has allowed me to mount the volume to a DVM, which has 
allowed me to fix the issue. Just running fsck in the DVM was enough to fix 
the issue.

Maybe I should create an issue (or find an existing one) for that.

Regards,
Vít Šesták 'v6ak'

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/084a8fe5-9fee-4273-ac7d-ebcd66d7eeaf%40googlegroups.com.

Re: [qubes-users] Re: Write-error on swap-device after having a full storage

[Steve Coleman]

On 2020-01-22 12:22, Vít Šesták wrote:
*APL external email warning: *Verify sender 
qubes-users+bncbct5hvg33eerbs4julyqkgqezk4s...@googlegroups.com before 
clicking links or attachments


I have tried to debug it further. Unfortunately, I am unable to attach 
the VM's drive to a DVM:


$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device 
'mapper/qubes_dom0-vm--debian--10n--root'


How can I do that?


Would this help?

How to mount LVM image
https://www.qubes-os.org/doc/mount-lvm-image/



Regards,
Vít Šesták 'v6ak'

--
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 qubes-users+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6e388d39-6ef4-4035-80be-23b7e9d1eab6%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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c1083eec-9f7e-df0a-3af0-c8dd5a56b67f%40jhuapl.edu.

[qubes-users] Re: Write-error on swap-device after having a full storage

[Vít Šesták]

I have tried to debug it further. Unfortunately, I am unable to attach the 
VM's drive to a DVM:

$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device 
'mapper/qubes_dom0-vm--debian--10n--root'

How can I do that?

Regards,
Vít Šesták 'v6ak'

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/6e388d39-6ef4-4035-80be-23b7e9d1eab6%40googlegroups.com.

[qubes-users] Re: Write-error on swap-device after having a full storage

[Vít Šesták]

I have tried to debug it further. Unfortunately, I am unable to attach the 
VM's drive to a DVM:

$ qvm-block attach disp1163 dom0:mapper/qubes_dom0-vm--debian--10n--root
qvm-block: error: backend vm 'dom0' doesn't expose device 
'mapper/qubes_dom0-vm--debian--10n--root'

How can I do that?

Regards,
Vít Šesták 'v6ak'

On Wednesday, January 22, 2020 at 1:43:00 PM UTC+1, Vít Šesták wrote:
>
> Hello,
> I have done this:
>
> 1. Started a template VM update.
> 2. It seems to have run out of space during the update.
> 3. I extended the storage.
>
> Expected result: After extending the storage, it works again.
>
> Actual result: I can boot neither the VM nor the related Template-based 
> VMs. When I try to do so, it switches to emergency mode and I cannot do 
> anything with the VM. It shuts down quickly.
>
> Excerpt from the log:
>  
> https://gist.github.com/v6ak/6685d7b6b686076ff9486bd60d2950e0
>
> This is very strange. The swap file is created again and again on start, 
> isn't it? So, there cannot be no relict from the last run, can it?
>
> Other TemplateVMs work correctly.
>
> Regards,
> Vít Šesták 'v6ak'
>

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7eb29a3c-e40a-4e92-86ae-27f7294c7027%40googlegroups.com.