On Sunday, January 7, 2018 at 11:36:41 PM UTC+1, Marek Marczykowski-Górecki
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On Sun, Jan 07, 2018 at 12:45:58PM -0800, Roy Bernat wrote:
> > On Sunday, 7 January 2018 22:30:39 UTC+2, Andrew David Wong wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA512
> > >
> > > On 2018-01-07 12:48, Roy Bernat wrote:
> > > > Hi All ,
> > > >
> > > > What is the best practice to trim disk inside qubes 4 .
> > > >
> > > > the qvm-trim-template dont exist anymore .
> > > >
> > > > R
> > > >
> > >
> > > You can use the `fstrim` command in the TemplateVM:
> > >
> > > $ sudo fstrim -v /
> >
> > Hi
> >
> > fstrim: /: the discard operation is not supported
>
> Strange, it should work. And on my system it works...
>
> Anything special in your configuration? Have you chosen non standard
> partitioning or such?
> Maybe you don't have LVM thin based storage? You can check that for the
> template using (adjust template name):
>
> qvm-volume ls fedora-26
>
> The storage pool used will be in the first column, for example:
>
> POOL:VOLUME VMNAME VOLUME_NAME
> REVERT_POSSIBLE
> linux-kernel:4.9.56-21 fedora-26 kernel No
> lvm:qubes_dom0/vm-fedora-26-private fedora-26 private No
> lvm:qubes_dom0/vm-fedora-26-root fedora-26 root No
> lvm:qubes_dom0/vm-fedora-26-volatile fedora-26 volatile No
>
> Here you see "lvm" pool.
>
> If you want, you can dig further: qvm-pool -i lvm
>
> name lvm
> driver lvm_thin
> size 486585401344
> thin_pool pool00
> usage 347665269260
> volume_group qubes_dom0
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -----BEGIN PGP SIGNATURE-----
>
> iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpSoNgACgkQ24/THMrX
> 1yzwzgf/Wl7+PDptZ0i9HN5viuSmQk0W5EeBawQ9CIJHseCGAqPLLvRToSRPBF9f
> vRPZv7HHAf0xoY7TPnBygjUAgb+u30rbGdpFafBwDugyzy8ojDLZvOZXgxaOiegn
> M27tjwX6i6Wpc83gh+HwIB4ARJua2gBOS0ULDXJBZZ4y1WoVN0fvr3RiDRGWhpYH
> 1QutmKGR4Cwz0D1KoEP1qhCiew9BQ2NS1SSCk4dgncZcAnnSCrLR+9WDmirZRl2U
> 2AbxMdFXMvFfsmXCiTyq/dw3H0N9c6Litq0KPcowkXxhXx24vQo7fjLJGKpFrOEv
> KuN+RRcMchphkF87AoVASm+G0rTzLA==
> =DGsq
> -----END PGP SIGNATURE-----
Out of curiosity I checked my own system too (I'm running LVM, not LVM Thin).
"
[user@fedora-26 ~]$ sudo fstrim -v /
fstrim: /: the discard operation is not supported
[user@fedora-26 ~]$
"
"
user@debian-8:~$ sudo fstrim -v /
fstrim: /: the discard operation is not supported
user@debian-8:~$
"
Dom0 was pretty much identical as the two examples above too.
Is LVM Thin the preferred FS-format on Qubes 4 over regular LVM?
Also, possibly this might be because I'm using LVM and not LVM Thin, but I get
python errors when I execute "qvm-pool -i lvm" in dom0. The command does not
exist in fedora-26 or debian-8 template. But I guess it must be a dom0 specific
command. Below is the python error from dom0.
[user@dom0 ~]$ qvm-pool -i lvm
Traceback (most recent call last):
File "/usr/bin/qvm-pool", line 5, in <module>
sys.exit(main())
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_pool.py", line
146, in main
args = parser.parse_args(args, app=app)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/__init__.py", line
387, in parse_args
action.parse_qubes_app(self, namespace)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/__init__.py", line
312, in parse_qubes_app
pools = [app.pools[name] for name in pool_names]
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/__init__.py", line
312, in <listcomp>
pools = [app.pools[name] for name in pool_names]
File "/usr/lib/python3.5/site-packages/qubesadmin/base.py", line 309, in
__getitem__
raise KeyError(item)
KeyError: 'lvm'
[aki@dom0 ~]$
So I'm guessing the solution would possibly be to re-install it all, but
instead pick LVM-Thin as the FS-format? I'll gladly sign up to be up for being
a guinea-pig and re-install Qubes 4 on LVM-Thin instead of LVM, (additional
difference would be Qubes RC-2 fully updated to Qubes RC-4), to test it out if
it makes a difference. Or maybe use Qubes RC-2 again for accuracy if it
matters? Albeit I'm unsure if there is any value in such a test, and or whether
systemdata is needed from before/after re-install.
--
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/3d093e9a-c5b4-4107-a695-e9a6d2eada09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
