Read-only file system in applVM

[Franz]

Hello,

Trying to save a long document I got an error.

So tried to open a new document to copy there the content of the older. But it gives an error: read only file system.

Any idea why this applVM now decided to be a read only file system? and if  is there a fix other than rebooting?

Best

Fran

[Chris Laprise]

It probably means there is a logical inconsistency (corruption) in that
filesystem, or it filled-up. You can avoid the latter by expanding the
Private storage max size in the VM's settings.

--

Chris Laprise, tas...@posteo.net
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

[Franz]

On Mon, Oct 9, 2017 at 9:36 PM, Chris Laprise <tas...@posteo.net> wrote:

On 10/09/2017 08:48 AM, Franz wrote:

Hello,

Trying to save a long document I got an error.

So tried to open a new document to copy there the content of the older. But it gives an error: read only file system.

Any idea why this applVM now decided to be a read only file system? and if  is there a fix other than rebooting?
Best
Fran

It probably means there is a logical inconsistency (corruption) in that filesystem, or it filled-up. You can avoid the latter by expanding the Private storage max size in the VM's settings.

It should be corruption, because there is plenty of space.

Anyway I had to reboot and after that it worked again even if an alert of Python not working appears.

Is there some way to fix corruption cases?

Best

fran

[Chris Laprise]

On 10/10/2017 02:31 AM, Franz wrote:
>
>
> On Mon, Oct 9, 2017 at 9:36 PM, Chris Laprise <tas...@posteo.net
> <mailto:tas...@posteo.net>> wrote:
>
> On 10/09/2017 08:48 AM, Franz wrote:
>
> Hello,
>
> Trying to save a long document I got an error.
>
> So tried to open a new document to copy there the content of
> the older. But it gives an error: read only file system.
>
> Any idea why this applVM now decided to be a read only file
> system? and if  is there a fix other than rebooting?
> Best
> Fran
>
>
> It probably means there is a logical inconsistency (corruption) in
> that filesystem, or it filled-up. You can avoid the latter by
> expanding the Private storage max size in the VM's settings.
>
>
> It should be corruption, because there is plenty of space.
>
> Anyway I had to reboot and after that it worked again even if an alert
> of Python not working appears.
>
> Is there some way to fix corruption cases?
> Best
> fran
>

Using 'fsck' on it might fix it. Before doing that, you may have to
re-mount the volume as read-only; or you could use qvm-block to attach
the private.img to a dispVM and then run fsck /dev/xvdi .

[Franz]

The second seems easier, but the same I am confused. Is there a tutorial somewhere?

Best

Fran

[Chris Laprise]

On 10/11/2017 11:00 AM, Franz wrote:
>
>
> On Tue, Oct 10, 2017 at 2:18 PM, Chris Laprise <tas...@posteo.net
> <mailto:tas...@posteo.net>> wrote:
>
> On 10/10/2017 02:31 AM, Franz wrote:
>
>
>
> On Mon, Oct 9, 2017 at 9:36 PM, Chris Laprise
> <tas...@posteo.net <mailto:tas...@posteo.net>

I can explain the steps. You may wish to backup your appVM before
continuing.

1. Start a dispVM (I'll call it disp1). Your appVM should not be running.

2. In dom0 run 'qvm-block -A /var/lib/qubes/appvms/yourappvm/private.img'
Substitute 'yourappvm' in above command with the name of your appVM.

3. In disp1 run 'sudo fsck /dev/xvdi'

After fsck finishes you can shutdown disp1 and try to use your appVM. Or
you can also use disp1 to explore the disk volume and copy data out of
it (e.g. 'sudo mount /dev/xvdi /somedir; qvm-copy destvm
/somedir/somefile').

[Chris Laprise]

Correction: This command should be 'qvm-block -A disp1
dom0:/var/lib/qubes/appvms/yourappvm/private.img'

[Franz]

Many thanks, it seems easy enough. I ordered some backup medium to backup everything before trying.

Best

Fran

--

Chris Laprise, tas...@posteo.net
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fb249663-15fd-bfa3-569c-5dd13eba0454%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[Foppe de Haan]

> PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

just for my information: why not just run that from dom0 directly (e.g. sudo fsck /var/lib/qubes/appvms/bla/bla.img)? is there a security risk involved with the invocation of fsck?

[Chris Laprise]

Actually, yes there is a risk.

--

Chris Laprise, tas...@posteo.net
https://twitter.com/ttaskett

[Foppe de Haan]

btw, when I try this (qvm-block method) in R4.0-rc1, I get 'backend vm 'dom0' doesn't expose device '/var/lib/qubes/etc/etc.img'.