Posts by prtigger1

    votdev


    Hi, i manually fixed your file:

    Code
    root@pr-srv-01:/etc/apt/sources.list.d# cat openmediavault-local.list
    deb [trusted=yes] file:/var/cache/openmediavault/archives ./
    root@pr-srv-01:/etc/apt/sources.list.d#

    Sorry, this it not fixing the problem:



    Best regards

    prtigger

    Ok thank´s


    You can move this to Installation/Updates-Upgrades!

    I was putting it wrong here!


    Hi folks


    What´s going on here after updating from 7.7.23 to 7.7.24...?



    Never had any errors before!

    Best regards


    prtigger

    Hi folks


    Does anybody knows a method to get rid of the automated mount option, for my data BTRFS Raid1 with three SSDs: discard=async?


    I want to do the trim of the filesystem manually, because there may be a problem with the Samsung 870 QVOs.


    Code
    /dev/sdb on /srv/dev-disk-by-uuid-a8a06053-0cc4-491d-adf2-01bb8a02fb44 type btrfs (rw,relatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/)

    I tried to set this and reboot, with no effect!:

    Code
    omv-env set OMV_FSTAB_MNTOPS_BTRFS "nodiscard"
    monit restart omv-engined
    omv-salt stage run prepare
    omv-salt stage run deploy

    Any suggestions?


    Best regards

    prtigger

    Krisbee

    crashtest


    Hi together

    here are my research results (without having a shutdown hang, up to now):


    -I/O-waits for writing 50GB of data to the btrfs Raid1 with three SSDs is from 2 to 5... That's good!

    (Edited: With write cache disabled on all disks and writing 14GB of data, I/O-waits are between 0,1 to 7,9)


    -'Synchronizing SCSI Cache/Stopping disk' is not the Problem... This always needs only a very short time during shutdown.

    Not a noticeable difference, when write cache is disabled.


    -'Stopping disk' is the part that could take time from very short (<0.5) to 6 seconds per disk, with my setup!

    That's combined with the drive usage LED... No relation to SSD write cache usage....


    I guess, stopping of the SSDs is not necessary because, no rotating disk...

    No relation to btrfs driver, because at this time no filesystem is active anymore.

    Activ is only the Sata Layer (AHCI driver in my setup).

    Varying stopping times could be SSD firmware related or Linux kernel driver, managing the stopping of the drives...

    It´s the same with 6.12.x Debian kernel and 6.14.x Proxmox kernel.


    When i think back to the last shutdown hang:

    '[FAILED] Failed unmounting srv-dev\x2dddisk\x2dby\x2duuid\x2...srv/dev-disk-by-uuid-<my-server-volume-uuid>'

    may happen at this part of the shutdown... But can't confirm at this time.


    I guess, there is nothing to unmount at this time of shutdown, because all file systems are already down!


    Possible workaround:

    Don't use shutdown! Use reboot (No disk stopping), go to Grub or BIOS and power off, by power button.


    So far at this point...


    Best regards

    prtigger

    Krisbee

    crashtest


    Hi

    I've got a question: I want to try, to disabling the write cache of the three Samsung SSDs (for Testing). The cache is enabled by default.

    I made no disk specific settings in the OMV GUI! Is there an easy way to disable it?


    Do you know any way to do a 'Synchronizing SCSI Cache' (Syncing on ahci driver layer) before shutdown server with mounted filesystem?


    Best regards

    prtigger

    Krisbee

    Hi here the result of the I/O-waits test:


    Had done this:


    Running 'top' with 5 seconds delay time:



    I/O-waits (wa) is most of the time between 1,4 - 2,3!

    The maximum i had seen during scrub was 3,3


    The maximum load average (1 min.) was 10,08


    Best regards

    prtigger

    ryecoaaron


    I guess it's an issue with the folder2ram script. But i don't care anymore, because i fixed it manually...

    Thank's for your information!


    Krisbee

    Here attached a picture of a normal shutdown process ending, before my system is powering off!

    Sometimes it's quick and sometimes 'Synchronizing SCSI Cache/Stopping disk' could take a long time!

    In this case it took about 3-4 seconds for each disk of the Btrfs Raid1 (The three Samsung SSDs).

    I don´s know what's happening at this time, because i can't find this part in the journal!

    I guess, journal service is down already, at this time...

    In this period of syncing and stopping the SSDs, the drive access led is on, permanently!


    My conclusion at this time:


    The 'Failed unmounting srv-dev\x2ddisk\.......' from picture of my post #12 is happening here!

    disk access led will stay permanently on....

    And this causes the server hang!


    Waiting more than 10 minutes doesn't help!:





    Best regards

    prtigger