Posts by mlillo

    Hello people!!!,


    I am having a problem with my btrfs volume, when an indeterminate time passes, for example 24 hours, I receive a monit alert email with the following content:


    Quote

    [NAS.local] Monitoring alert -- Filesystem flags changed filesystem_srv_dev-disk-by-label-poolFS

    Host: \NAS.local
    Date: Mon, 17 Aug 2020 11:51:17
    Service: filesystem_srv_dev-disk-by-label-poolFS
    Event: Filesystem flags changed
    Description: filesystem flags changed to ro,noatime,compress=zstd:3,space_cache,subvolid=5,subvol=/
    This triggered the monitoring system to: alert

    From this moment the file system appears as readonly and my containers that I have on this volume begin to fail. When I reboot the system returns to normal.

    I scrubbed the volume and got the following message:


    Code
    root@NAS:/srv/dev-disk-by-label-poolFS/@homeUsers/mlillo# btrfs scrub status /srv/dev-disk-by-label-poolFS/
    scrub status for 0e696343-a445-481b-9f9f-0449d8ad65c3
    scrub started at Sun Aug 16 13:31:35 2020 and was aborted after 22:19:19
    total bytes scrubbed: 6.98TiB with 2 errors
    error details: super=1 csum=1
    corrected errors: 1, uncorrectable errors: 0, unverified errors: 0

    Can anybody help me?

    This has me a little desperate.


    Thank you

    Hello colleagues,

    I am having problems with my omv5.4.2-1 since the last update. When the system starts, I receive monit alerts about the availability of two services:

    Code
    The system monitoring needs your attention.
    Host: \NAS.local
    Date: Mon, 04 May 2020 08:16:57
    Service: proftpd
    Event: Does not exist
    Description: process is not running
    This triggered the monitoring system to: restart

    In a minute or so I re-receive alerts that the file system is already available:


    Code
    The system monitoring needs your attention.
    Host: \NAS.local
    Date: Mon, 04 May 2020 08:17:58
    Service: mountpoint_srv_dev-disk-by-label-poolFS
    Event: Status succeeded
    Description: status succeeded (0) -- /srv/dev-disk-by-label-poolFS is a mountpoint
    This triggered the monitoring system to: alert
    Code
    The system monitoring needs your attention.
    Host: \NAS.local
    Date: Mon, 04 May 2020 08:17:28
    Service: filesystem_srv_dev-disk-by-label-poolFS
    Event: Exists
    Description: succeeded getting filesystem statistics for '/srv/dev-disk-by-label-poolFS'
    This triggered the monitoring system to: alert
    Code
    The system monitoring needs your attention.
    Host: \NAS.local
    Date: Mon, 04 May 2020 08:16:57
    Service: proftpd
    Event: Does not exist
    Description: process is not running
    This triggered the monitoring system to: restart

    I understand that it is for the time that elapses since the mount is launched until the filesystem is ready.


    The one that worries me is the filesystem because it causes my docker containers to be corrupted because when they start up they do not have access to the volumes located in the poolFS that I have with btrfs and raid1.


    I'm pretty lost with this, can anyone help me?


    I add some information that I have collected:


    Code
    blkid
    /dev/sda: LABEL="poolFS" UUID="0e696343-a445-481b-9f9f-0449d8ad65c3" UUID_SUB="de0668a0-116a-420e-ba18-120e256be965" TYPE="btrfs"
    /dev/sdc: LABEL="poolFS" UUID="0e696343-a445-481b-9f9f-0449d8ad65c3" UUID_SUB="514ce6bf-77c8-466c-803e-a00406203080" TYPE="btrfs"
    /dev/sdb1: UUID="440A-716A" TYPE="vfat" PARTUUID="8416d791-32ac-4e22-97ac-87c9359f1d24"
    /dev/sdb2: UUID="720c65b3-b6ad-4fd8-a29d-7a71ea7bf347" TYPE="ext4" PARTUUID="c4da7b72-06da-4f84-b08f-682cf65648fd"
    /dev/sdb3: UUID="804397ea-1c5c-48ea-bf6d-8cf1a4e62040" TYPE="swap" PARTUUID="22a373c9-efa1-4f47-9ad7-c47987444487"
    /dev/sdd: LABEL="poolFS" UUID="0e696343-a445-481b-9f9f-0449d8ad65c3" UUID_SUB="19f398c6-8a42-4d2c-83be-55f7b74bc192" TYPE="btrfs"


    thanks in advance and sorry for my english