1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • speed performance issues

    From faeychild@2:250/1 to All on Thu May 19 23:41:45 2022

    For the last week or two I have had slow responses from the system.
    Icons are erratically slow to highlight when the cursor rolls over
    Dolphin can be reluctant to change folders quickly

    When I render video with Kdenlive I used to get core temps in the high
    70's degrees celsius. Now it barely pushes 60.

    Handbrake is slow to load files and it doesn't push the system either

    I get a HD light hard on when booting. It comes on at the end of kernel messages - hot plug loading- and last for about 1 minute and a half at
    the login screen.

    The primary drive is SSD, The secondary is spinning rust with no
    sounds of thrashing

    I don't have a full partition lurking anywhere

    ~]$ df -Th
    Filesystem Type Size Used Avail Use% Mounted on
    devtmpfs devtmpfs 16G 0 16G 0% /dev
    tmpfs tmpfs 16G 0 16G 0% /dev/shm
    tmpfs tmpfs 16G 1.3M 16G 1% /run
    /dev/nvme0n1p8 ext4 26G 17G 8.4G 67% /
    tmpfs tmpfs 16G 4.0K 16G 1% /tmp
    /dev/nvme0n1p1 vfat 299M 168K 299M 1% /boot/EFI
    /dev/sda1 ext4 5.5T 4.1T 1.2T 78% /video
    tmpfs tmpfs 3.2G 112K 3.2G 1% /run/user/1000



    This all a bit vague, I know. I have run out of inspiration
    The box is definitely not as snappy as it used to be

    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.35-desktop-2.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Thu May 19 23:54:00 2022
    On 2022-05-19, faeychild <faeychild@nomail.afraid.org> wrote:

    For the last week or two I have had slow responses from the system.
    Icons are erratically slow to highlight when the cursor rolls over
    Dolphin can be reluctant to change folders quickly

    When I render video with Kdenlive I used to get core temps in the high
    70's degrees celsius. Now it barely pushes 60.

    Handbrake is slow to load files and it doesn't push the system either

    I get a HD light hard on when booting. It comes on at the end of kernel messages - hot plug loading- and last for about 1 minute and a half at
    the login screen.

    The primary drive is SSD, The secondary is spinning rust with no
    sounds of thrashing

    I don't have a full partition lurking anywhere

    ~]$ df -Th
    Filesystem Type Size Used Avail Use% Mounted on
    devtmpfs devtmpfs 16G 0 16G 0% /dev
    tmpfs tmpfs 16G 0 16G 0% /dev/shm
    tmpfs tmpfs 16G 1.3M 16G 1% /run
    /dev/nvme0n1p8 ext4 26G 17G 8.4G 67% /
    tmpfs tmpfs 16G 4.0K 16G 1% /tmp
    /dev/nvme0n1p1 vfat 299M 168K 299M 1% /boot/EFI
    /dev/sda1 ext4 5.5T 4.1T 1.2T 78% /video
    tmpfs tmpfs 3.2G 112K 3.2G 1% /run/user/1000



    This all a bit vague, I know. I have run out of inspiration
    The box is definitely not as snappy as it used to be


    Use top to see what is running and taking up time. User gkrellm to
    follow how things are changing.

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri May 20 00:22:33 2022
    On Thu, 19 May 2022 18:41:45 -0400, faeychild <faeychild@nomail.afraid.org> wrote:
    The primary drive is SSD, The secondary is spinning rust with no
    sounds of thrashing
    This all a bit vague, I know. I have run out of inspiration
    The box is definitely not as snappy as it used to be

    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    Regards, Dave Hodgins

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Vincent Coen@2:250/1 to David W. Hodgins on Fri May 20 13:51:53 2022
    Hello David!

    Friday May 20 2022 00:22, David W. Hodgins wrote to All:

    On Thu, 19 May 2022 18:41:45 -0400, faeychild
    <faeychild@nomail.afraid.org> wrote:
    The primary drive is SSD, The secondary is spinning rust with no
    sounds of thrashing
    This all a bit vague, I know. I have run out of inspiration
    The box is definitely not as snappy as it used to be

    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    I run fstrim via crontab every 12 hours (00 and 12) so is there a way of
    using this service (fstrim-timer) more often than weekly and is there documentation for the timer settings ?

    One other thing while here about systemctl services I have clamd and
    auxiliary tools installed including .socket which I have to change to use a port (3310) and every time there is a update to clam, these setting get
    over written so is there a way of stopping this or using the setting
    currently in use ?

    I assume here that any other systemctl setting within
    /usr/lib/systemd/system will behave in a similar manner - not retain
    existing settings etc.


    Vincent


    SEEN-BY: 25/0 230/150 250/0 1 2 3 4 5 6 12 263/0
  • From Jim@2:250/1 to All on Fri May 20 15:06:14 2022
    On Thu, 19 May 2022 19:22:33 -0400, David W. Hodgins wrote:
    <snip>
    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    I tried those two commands, and was presented with error message
    that mean nothing to me. What is "unit files" in this context?
    What else should I know, but don't?

    # systemctl enable fstrim.service
    The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for
    template
    units). This means they are not meant to be enabled using systemctl.

    Possible reasons for having this kind of units are:
    • A unit may be statically enabled by being symlinked from another unit's
    .wants/ or .requires/ directory.
    • A unit's purpose may be to act as a helper for some other unit which has
    a requirement dependency on it.
    • A unit may be started when needed via activation (socket, path, timer,
    D-Bus, udev, scripted systemctl call, ...).
    • In case of template units, the unit is meant to be enabled with some
    instance name specified.

    # systemctl enable fstrim.timer
    Created symlink /etc/systemd/system/timers.target.wants/fstrim.timer → / usr/lib/systemd/system/fstrim.timer.
    [root@sorrel ~]# systemctl enable fstrim.service
    The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for
    template
    units). This means they are not meant to be enabled using systemctl.

    Possible reasons for having this kind of units are:
    • A unit may be statically enabled by being symlinked from another unit's
    .wants/ or .requires/ directory.
    • A unit's purpose may be to act as a helper for some other unit which has
    a requirement dependency on it.
    • A unit may be started when needed via activation (socket, path, timer,
    D-Bus, udev, scripted systemctl call, ...).
    • In case of template units, the unit is meant to be enabled with some
    instance name specified.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely
    expects users to be computer friendly.

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Fri May 20 21:27:34 2022
    On Fri, 20 May 2022 10:06:14 -0400, Jim <jim.beard@verizon.net> wrote:

    On Thu, 19 May 2022 19:22:33 -0400, David W. Hodgins wrote:
    <snip>
    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    I tried those two commands, and was presented with error message
    that mean nothing to me. What is "unit files" in this context?
    What else should I know, but don't?

    Only try getting it to run automatically if you've confirmed "fstrim -av"
    fixes the issue.

    Reboot, and then post the output of (as root) "fstrim -av".

    I was wrong about needing to enable fstrim.service, though trying to do so
    does no harm other then the error message.

    For fstrim.timer, enable it to run once a week, which should be enough for
    most people. Running it more often will reduce the life span of the ssd drives.

    If you really want to run it more often, then with fstrim.timer disabled ...
    # cp /lib/systemd/system/fstrim.timer /etc/systemd/system
    Then edit the copy of the fstrim.timer file in /etc/systemd/system.
    Change the weekly to daily.

    Running it every 12 hours is excessive, but if you insist, use 12h instead of daily. See "man systemd.time" for how to specify other values.

    Note that while fstrim is running, anything trying to access files on the file system currently being trimmed will be stuck in a device wait state.

    The first fstrim that runs after boot will try to discard all unused pages, which may take a while. After that it only discards pages for deleted file.

    Regards, Dave Hodgins

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri May 20 23:16:55 2022
    On 20/5/22 09:22, David W. Hodgins wrote:
    On Thu, 19 May 2022 18:41:45 -0400, faeychild
    <faeychild@nomail.afraid.org> wrote:
    The primary drive is SSD, The secondary is  spinning  rust with no
    sounds of thrashing
    This all a bit vague, I know. I have run out of inspiration
    The box is definitely not as snappy as it used to be

    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    Regards, Dave Hodgins



    ~]# fstrim -av
    /boot/EFI: 298.2 MiB (312733696 bytes) trimmed on /dev/nvme0n1p1
    /: 9.7 GiB (10414579712 bytes) trimmed on /dev/nvme0n1p8


    No change.
    I notice it's /boot/EFI again Some days ago I had a dmesg suggesting I
    fsck the partiton.

    I will have to find more time this afternoon


    And then there is this

    [ 6.205049] FAT-fs (nvme0n1p1): utf8 is not a recommended IO charset
    for FAT filesystems, filesystem will be case sensitive!
    [ 6.428738] EXT4-fs (sda1): mounted filesystem with ordered data
    mode. Opts: acl. Quota mode: none.
    [ 7.587714] cfg80211: Loading compiled-in X.509 certificates for
    regulatory database
    [ 7.590146] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
    [ 10.863675] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps
    Full Duplex, Flow Control: Rx/Tx
    [ 10.865959] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
    [ 12.726993] NET: Registered PF_PACKET protocol family
    [ 16.622278] netfilter PSD loaded - (c) astaro AG
    [ 16.623909] IFWLOG: register target
    [ 41.219566] ata2.00: exception Emask 0x0 SAct 0x43c008 SErr 0x0
    action 0x0
    [ 41.219581] ata2.00: irq_stat 0x40000008
    [ 41.219587] ata2.00: failed command: READ FPDMA QUEUED
    [ 41.219592] ata2.00: cmd 60/08:70:00:08:80/00:00:6a:00:00/40 tag 14
    ncq dma 4096 in
    res 41/40:00:00:08:80/00:00:6a:00:00/00 Emask
    0x409 (media error) <F>
    [ 41.219610] ata2.00: status: { DRDY ERR }
    [ 41.219615] ata2.00: error: { UNC }
    [ 41.222418] ata2.00: configured for UDMA/133
    [ 41.222454] sd 1:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=3s
    [ 41.222463] sd 1:0:0:0: [sda] tag#14 Sense Key : Medium Error [current]
    [ 41.222468] sd 1:0:0:0: [sda] tag#14 Add. Sense: Unrecovered read
    error - auto reallocate failed
    [ 41.222474] sd 1:0:0:0: [sda] tag#14 CDB: Read(16) 88 00 00 00 00 00
    6a 80 08 00 00 00 00 08 00 00
    [ 41.222477] blk_update_request: I/O error, dev sda, sector 1786775552
    op 0x0:(READ) flags 0x83700 phys_seg 1 prio class 0
    [ 41.222499] ata2: EH complete



    Do I have a drive dying
    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.35-desktop-2.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri May 20 23:29:51 2022
    On 21/5/22 08:16, faeychild wrote:
    smartctl doesn't find any errors


    ~]# smartctl -a /dev/sda
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.35-desktop-2.mga8]
    (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Model Family: Western Digital Blue
    Device Model: WDC WD60EZRZ-00RWYB1
    Serial Number: WD-WX21DB509Z06
    LU WWN Device Id: 5 0014ee 2633681b9
    Firmware Version: 80.00A80
    User Capacity: 6,001,175,126,016 bytes [6.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5700 rpm
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
    SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Sat May 21 08:26:10 2022 AEST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status: (0x84) Offline data collection activity
    was suspended by an
    interrupting command from host.
    Auto Offline Data Collection: Enabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test
    has ever
    been run.
    Total time to complete Offline
    data collection: ( 2624) seconds.
    Offline data collection
    capabilities: (0x7b) SMART execute Offline immediate.
    Auto Offline data collection
    on/off support.
    Suspend Offline collection upon new
    command.
    Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported. Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 680) minutes.
    Conveyance self-test routine
    recommended polling time: ( 5) minutes.
    SCT capabilities: (0x3035) SCT Status supported.
    SCT Feature Control supported.
    SCT Data Table supported.

    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
    UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x002f 085 085 051 Pre-fail
    Always - 4462
    3 Spin_Up_Time 0x0027 200 193 021 Pre-fail
    Always - 9000
    4 Start_Stop_Count 0x0032 097 097 000 Old_age
    Always - 3289
    5 Reallocated_Sector_Ct 0x0033 171 171 140 Pre-fail
    Always - 867
    7 Seek_Error_Rate 0x002e 200 196 000 Old_age
    Always - 0
    9 Power_On_Hours 0x0032 060 060 000 Old_age
    Always - 29631
    10 Spin_Retry_Count 0x0032 100 100 000 Old_age
    Always - 0
    11 Calibration_Retry_Count 0x0032 100 100 000 Old_age
    Always - 0
    12 Power_Cycle_Count 0x0032 097 097 000 Old_age
    Always - 3288
    192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always
    - 261
    193 Load_Cycle_Count 0x0032 134 134 000 Old_age Always
    - 198292
    194 Temperature_Celsius 0x0022 126 106 000 Old_age Always
    - 26
    196 Reallocated_Event_Count 0x0032 190 190 000 Old_age Always
    - 10
    197 Current_Pending_Sector 0x0032 199 199 000 Old_age Always
    - 1085
    198 Offline_Uncorrectable 0x0030 200 200 000 Old_age
    Offline - 839
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always
    - 0
    200 Multi_Zone_Error_Rate 0x0008 194 194 000 Old_age
    Offline - 3131

    SMART Error Log Version: 1
    No Errors Logged

    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining
    LifeTime(hours) LBA_of_first_error
    # 1 Short offline Completed without error 00% 14188
    -
    # 2 Short offline Aborted by host 80% 14188
    -
    # 3 Extended offline Interrupted (host reset) 60% 10311
    -

    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.

    [root@unimatrix ~]#



    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.35-desktop-2.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri May 20 23:45:24 2022
    On 20/5/22 08:54, William Unruh wrote:



    Use top to see what is running and taking up time. User gkrellm to
    follow how things are changing.



    htop and gkrellm show everything is idling

    all cores are at 2% or lower

    They all jump up to 70% when handbrake is running and running much
    cooler than they used to
    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.35-desktop-2.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Sat May 21 00:47:35 2022
    On Fri, 20 May 2022 18:29:51 -0400, faeychild <faeychild@nomail.afraid.org> wrote:
    On 21/5/22 08:16, faeychild wrote:
    smartctl doesn't find any errors
    ~]# smartctl -a /dev/sda

    Note that sda is the spinning rust drive, not the ssd drives.

    Snip details, which show 867 reallocated sectors meaning 867 sectors that are bad,
    so they've been replaced from a pool of spare sectors. It hasn't run out of spare
    sectors yet, apparently.

    The last test that ran was at 14188 power on hours, which passed ok.
    The current power on hours is 29631.

    From the prior article "blk_update_request: I/O error, dev sda, sector 1786775552 op 0x0:(READ) flags 0x83700 phys_seg 1 prio class 0" shows the drive has at least one
    error that has developed since the last smartctl test.

    I wouldn't risk continuing to use that drive. It is also likely slowing down the rest of the system, depending on what it's being used for.

    The nvme is the one that may or may not benefit from the fstrim command.

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sat May 21 02:39:51 2022
    On 21/5/22 09:47, David W. Hodgins wrote:


    The nvme is the one that may or may not benefit from the fstrim command.

    ~]# smartctl -a /dev/nvme0n1
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.35-desktop-2.mga8]
    (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Model Number: INTEL SSDPEKKW128G7
    Serial Number: BTPY63260EBE128A
    Firmware Version: PSF100C
    PCI Vendor/Subsystem ID: 0x8086
    IEEE OUI Identifier: 0x5cd2e4
    Controller ID: 1
    NVMe Version: 1.2
    Number of Namespaces: 1
    Namespace 1 Size/Capacity: 128,035,676,160 [128 GB]
    Namespace 1 Formatted LBA Size: 512
    Local Time is: Sat May 21 11:28:59 2022 AEST
    Firmware Updates (0x12): 1 Slot, no Reset required
    Optional Admin Commands (0x0006): Format Frmw_DL
    Optional NVM Commands (0x001e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
    Log Page Attributes (0x03): S/H_per_NS Cmd_Eff_Lg
    Maximum Data Transfer Size: 32 Pages
    Warning Comp. Temp. Threshold: 70 Celsius
    Critical Comp. Temp. Threshold: 80 Celsius

    Supported Power States
    St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
    0 + 9.00W - - 0 0 0 0 5 5
    1 + 4.60W - - 1 1 1 1 30 30
    2 + 3.80W - - 2 2 2 2 30 30
    3 - 0.0700W - - 3 3 3 3 10000 300
    4 - 0.0050W - - 4 4 4 4 2000 10000

    Supported LBA Sizes (NSID 0x1)
    Id Fmt Data Metadt Rel_Perf
    0 + 512 0 0

    === START OF SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    SMART/Health Information (NVMe Log 0x02)
    Critical Warning: 0x00
    Temperature: 36 Celsius
    Available Spare: 100%
    Available Spare Threshold: 10%
    Percentage Used: 20%
    Data Units Read: 27,535,227 [14.0 TB]
    Data Units Written: 51,918,270 [26.5 TB]
    Host Read Commands: 475,392,526
    Host Write Commands: 772,459,911
    Controller Busy Time: 6,121
    Power Cycles: 3,176
    Power On Hours: 29,832
    Unsafe Shutdowns: 184
    Media and Data Integrity Errors: 1
    Error Information Log Entries: 1
    Warning Comp. Temperature Time: 0
    Critical Comp. Temperature Time: 0

    Error Information (NVMe Log 0x01, 16 of 64 entries)
    Num ErrCount SQId CmdId Status PELoc LBA NSID VS
    0 1 5 0x0000 0x0286 - 0 1 -



    My choice is between seagate and WD for a new drive. I think it was
    second hand when it went into the box so it could be older than I
    imagine. there is no click of death yet


    I have also logged to "junk" user a couple of times between jobs and
    can't recreate the lag in the highlighting of a selected icon.

    So it's my config files somewhere.


    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.35-desktop-2.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim@2:250/1 to All on Sat May 21 15:33:05 2022
    On Fri, 20 May 2022 16:27:34 -0400, David W. Hodgins wrote:

    On Fri, 20 May 2022 10:06:14 -0400, Jim <jim.beard@verizon.net> wrote:

    On Thu, 19 May 2022 19:22:33 -0400, David W. Hodgins wrote: <snip>
    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    I tried those two commands, and was presented with error message that
    mean nothing to me. What is "unit files" in this context? What else
    should I know, but don't?

    Only try getting it to run automatically if you've confirmed "fstrim
    -av" fixes the issue.

    I did not have the problem, but was just thinking of trying out the
    automatic fstrim setup.

    IIRC, the error messages I saw were insignificant, as things had
    not been set up yet, so no problem there.

    I will continue running fstrim now and then manually.

    Thanks for your info.

    Cheers!

    jim b.


    --
    UNIX is not user-unfriendly, it merely
    expects users to be computer friendly.

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Vincent Coen@2:250/1 to Jim on Sat May 21 18:32:35 2022
    Hello Jim!

    Saturday May 21 2022 15:33, Jim wrote to All:

    On Fri, 20 May 2022 16:27:34 -0400, David W. Hodgins wrote:

    On Fri, 20 May 2022 10:06:14 -0400, Jim <jim.beard@verizon.net>
    wrote:

    On Thu, 19 May 2022 19:22:33 -0400, David W. Hodgins wrote: <snip>
    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable
    fstrim.timer".

    I tried those two commands, and was presented with error message
    that mean nothing to me. What is "unit files" in this context?
    What else should I know, but don't?

    Only try getting it to run automatically if you've confirmed "fstrim
    -av" fixes the issue.

    I did not have the problem, but was just thinking of trying out the automatic fstrim setup.

    IIRC, the error messages I saw were insignificant, as things had
    not been set up yet, so no problem there.

    I will continue running fstrim now and then manually.

    Thanks for your info.

    My system is 24/7 and I run various services including a bbs so I run it
    every 12 hours.

    Just as well as over the last few weeks it is reporting large values which
    for the life of me I cannot see why, i.e.,

    /boot/EFI: 298.3 MiB (312737792 bytes) trimmed on /dev/sda1
    /: 10.4 GiB (11157245952 bytes) trimmed on /dev/sda2


    and it is usually larger and can go to almost 30 Gb.

    Before it was a few hundred megs and if a system update was due, larger
    becuase of the cache being used for auto downloads and yes I have it set to manually do the updates.

    Possible reason a recent update of some thing.

    Vincent


    SEEN-BY: 25/0 230/150 250/0 1 2 3 4 5 6 12 263/0
  • From David W. Hodgins@2:250/1 to All on Sat May 21 18:02:18 2022
    On Sat, 21 May 2022 10:33:05 -0400, Jim <jim.beard@verizon.net> wrote:

    On Fri, 20 May 2022 16:27:34 -0400, David W. Hodgins wrote:

    On Fri, 20 May 2022 10:06:14 -0400, Jim <jim.beard@verizon.net> wrote:

    On Thu, 19 May 2022 19:22:33 -0400, David W. Hodgins wrote: <snip>
    Try running "fstrim -av" (as root). If that fixes it, then run
    "systemctl enable fstrim.service" and "systemctl enable fstrim.timer".

    I tried those two commands, and was presented with error message that
    mean nothing to me. What is "unit files" in this context? What else
    should I know, but don't?

    Only try getting it to run automatically if you've confirmed "fstrim
    -av" fixes the issue.

    I did not have the problem, but was just thinking of trying out the
    automatic fstrim setup.

    IIRC, the error messages I saw were insignificant, as things had
    not been set up yet, so no problem there.

    I will continue running fstrim now and then manually.

    Thanks for your info.

    Cheers!

    Be aware of https://bugs.mageia.org/show_bug.cgi?id=30406#c18
    Some ssd drives will discard in use pages when running fstrim, so only use
    if the drive slows down dramatically indicating it doesn't automatically discard unused pages.

    Regards, Dave Hodgins

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sat May 21 23:43:31 2022
    On 21/5/22 11:39, faeychild wrote:
    I shall be doing nothing for while
    I have contracted Flu

    The ackey breakey broken rib kind
    Hurts to breath in hurts to breath out.
    specially hurts to cough

    I will be lurking and glaring :-)


    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.35-desktop-2.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim@2:250/1 to All on Sun May 22 00:42:15 2022
    On Sun, 22 May 2022 08:43:31 +1000, faeychild wrote:

    On 21/5/22 11:39, faeychild wrote:
    I shall be doing nothing for while I have contracted Flu

    The ackey breakey broken rib kind Hurts to breath in hurts to breath
    out.
    specially hurts to cough

    I will be lurking and glaring :-)

    Good luck with the respiratory infection.
    Can be nasty.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely
    expects users to be computer friendly.

    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun May 22 23:08:56 2022
    On 22/5/22 09:42, Jim wrote:


    Good luck with the respiratory infection.
    Can be nasty.

    Cheers!

    jim b.

    I can cough again so maybe things are looking up
    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.41-desktop-1.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Mon May 23 03:15:41 2022
    On 21/5/22 09:47, David W. Hodgins wrote:

    I wouldn't risk continuing to use that drive. It is also likely slowing
    down
    the rest of the system, depending on what it's being used for.

    The nvme is the one that may or may not benefit from the fstrim command.

    After a morning rally against the flu I had an inspiration and rem'd out
    the /dev/sda entry in fstab

    The system booted up without the long HD light display.

    The spinning rust is not looking good
    I may fsck the HD to see what happens but a new one is in order.
    --
    faeychild
    Running plasmashell 5.20.4 on 5.15.41-desktop-1.mga8 kernel.
    Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


    --- MBSE BBS v1.0.8 (Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)