On 2018-07-31 10:46, Philipp Kern wrote:
On 2018-07-31 09:24, Philipp Kern wrote:
I buy the argument for attached removable file systems. It looks like
today fstrim iterates over /proc/self/mountinfo and trims all
non-pseudo/non-netfs. On the other hand enough guides on the internet
say that to
On 2018-07-31 09:24, Philipp Kern wrote:
I buy the argument for attached removable file systems. It looks like
today fstrim iterates over /proc/self/mountinfo and trims all
non-pseudo/non-netfs. On the other hand enough guides on the internet
say that to have a working system with an SSD, you wan
On 16.03.2018 03:58, Christoph Anton Mitterer wrote:
> As cruncher already noted, TRIM/discard may have an influence on the
> security of encrypted devices.
> But... per default, dm-crypt (respectively cryptsetup) sets the devices
> to ignore any trim commands and not pass it down to lower layers (
Hey.
Just adding my 2 cents on this.
As cruncher already noted, TRIM/discard may have an influence on the
security of encrypted devices.
But... per default, dm-crypt (respectively cryptsetup) sets the devices
to ignore any trim commands and not pass it down to lower layers (
--allow-discards opti
Package: util-linux
Version: 2.31.1-0.4
Followup-For: Bug #889668
Hi
Goal: Not running fstrim automatically
I have no idea how this is normally handled, but the fstrim.timer/service
should NOT be enabled by default (or at least use maybe /etc/default/fstrim to
have the setting unchanged after ev
Package: util-linux
Version: 2.30.2-0.3
Severity: normal
Please install /usr/share/doc/util-linux/examples/fstrim.timer as
/usr/lib/systemd/system/fstrim.timer instead.
There is no need to enable it by default, but please install the file so
it will be available for users who want to enable it.
6 matches
Mail list logo
