Re: SOLVED Re: Disk corruption and performance issue.

From	Gremlin <scott-andrews@columbus.rr.com>
Newsgroups	linux.debian.user
Subject	Re: SOLVED Re: Disk corruption and performance issue.
Date	2024-02-26 22:00 +0100
Message-ID	<IbQeS-cPA4-3@gated-at.bofh.it> (permalink)
References	(1 earlier) <HYqUV-4qX4-3@gated-at.bofh.it> <HYDyN-4yGn-7@gated-at.bofh.it> <IbNTH-cOi1-5@gated-at.bofh.it> <IbOwp-cOKI-5@gated-at.bofh.it> <IbP97-cOXT-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 2/26/24 14:40, Tim Woodall wrote:
> On Mon, 26 Feb 2024, Gremlin wrote:
> 
>> Are you using systemd ?
> No, I'm not
> 
>> You should not be running trim in a container/virtual machine
> 
> Why not? That's, in my case, basically saying "you should not be running
> trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like
> to understand why. Enabling thin_provisioning and fstrim works and gets
> mapped to the underlying layers all the way down to the SSD.

I guest you didn't understand the systemd timer that runs fstrim on the 
host.

> 
> My underlying VG is less than 50% occupied, so I can trim the free space
> by creating a LV and then removing it again (I have issue_discards set)
> 
> FWIW, I did issue fstrim in the VMs with no visible issues at all.
> Perhaps I got lucky?
> 
>> Here is some info: https://wiki.archlinux.org/title/Solid_state_drive
> 
> I don't see VM or virtual machine anywhere on that page.
> 
> 

Exactly, and you should not be running it in a VM/container. Which BTW 
systemd will not run fstrim in a container.

The Host system takes care of it

Well you can keep shooting yourself in the butt as long as you wish,  I 
on the other hand tend not to do that as much I possibly can as I need 
to be able to set down at times.

Thread

Disk corruption and performance issue. Tim Woodall <debianuser@woodall.me.uk> - 2024-01-20 17:30 +0100
  Re: Disk corruption and performance issue. David Christensen <dpchrist@holgerdanske.com> - 2024-01-20 22:20 +0100
    Re: Disk corruption and performance issue. Tim Woodall <debianuser@woodall.me.uk> - 2024-01-21 11:50 +0100
      Re: Disk corruption and performance issue. gene heskett <gheskett@shentel.net> - 2024-01-21 19:00 +0100
      Re: Disk corruption and performance issue. David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 00:10 +0100
      SOLVED Re: Disk corruption and performance issue. Tim Woodall <debianuser@woodall.me.uk> - 2024-02-26 19:30 +0100
        Re: SOLVED Re: Disk corruption and performance issue. Gremlin <scott-andrews@columbus.rr.com> - 2024-02-26 20:10 +0100
          Re: SOLVED Re: Disk corruption and performance issue. Tim Woodall <debianuser@woodall.me.uk> - 2024-02-26 20:50 +0100
            Re: SOLVED Re: Disk corruption and performance issue. Gremlin <scott-andrews@columbus.rr.com> - 2024-02-26 22:00 +0100
              Re: SOLVED Re: Disk corruption and performance issue. Tim Woodall <debianuser@woodall.me.uk> - 2024-02-26 22:40 +0100
                Re: SOLVED Re: Disk corruption and performance issue. Gremlin <scott-andrews@columbus.rr.com> - 2024-02-26 22:50 +0100
              Re: SOLVED Re: Disk corruption and performance issue. Stefan Monnier <monnier@iro.umontreal.ca> - 2024-02-26 22:50 +0100
        Re: SOLVED Re: Disk corruption and performance issue. Andy Smith <andy@strugglers.net> - 2024-02-27 00:50 +0100
          Re: SOLVED Re: Disk corruption and performance issue. Tim Woodall <debianuser@woodall.me.uk> - 2024-02-27 05:40 +0100

csiph-web