Snapraid data error in aquota.user

  • Hi,


    In my last snapraid check, I got:


    Data error in file '/srv/dev-disk-by-label-Data4/aquota.user' at position '0', diff bits 61/128Data error in file '/srv/dev-disk-by-label-Data4/aquota.group' at position '0', diff bits 61/128I kinda doubt that there is really something wrong with the disk because it would be too much of a coincidence that two errors occur at the same time in two small files.Does anybody have a clue? I previously had false data errors in Excel files because (IIRC) Excel sometimes modifies some bits in the header without changing the access time, which triggers the error detection mechanism of snapraid.

  • The typical Snapraid install using the plugin excludes those files, among others, by default.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • I installed it using the plugin, but I recently had an error during an update of the plugin, maybe something went wrong there.


    Edit: below is my snapraid.conf. The only excluded files are snapraid.conf*


    Does it make sense to edit it manually, or will the changes be overwritten by the next update? I haven't seen any way to add excludes from the frontend.


    # this file was automatically generated from
    # openmediavault Arrakis 4.1.23-1
    # and 'openmediavault-snapraid' 3.7.5



    block_size 256
    autosave 0
    #####################################################################
    # OMV-Name: Parity Drive Label: Parity
    parity /srv/dev-disk-by-label-Parity/snapraid.parity



    #####################################################################
    # OMV-Name: Data1 Drive Label: Data1
    content /srv/dev-disk-by-label-Data1/snapraid.content
    disk Data1 /srv/dev-disk-by-label-Data1



    #####################################################################
    # OMV-Name: Data2 Drive Label: Data2
    content /srv/dev-disk-by-label-Data2/snapraid.content
    disk Data2 /srv/dev-disk-by-label-Data2



    #####################################################################
    # OMV-Name: Data3 Drive Label: Data3
    content /srv/dev-disk-by-label-Data3/snapraid.content
    disk Data3 /srv/dev-disk-by-label-Data3



    #####################################################################
    # OMV-Name: Data4 Drive Label: Data4
    content /srv/dev-disk-by-label-Data4/snapraid.content
    disk Data4 /srv/dev-disk-by-label-Data4



    exclude /snapraid.conf*

  • I installed it using the plugin, but I recently had an error during an update of the plugin, maybe something went wrong there.


    Edit: below is my snapraid.conf. The only excluded files are snapraid.conf*


    Does it make sense to edit it manually, or will the changes be overwritten by the next update? I haven't seen any way to add excludes from the frontend.

    Make sure you have the current version of the plugin which is 3.7.7.


    Look in /etc/default/openmediavault-snapraid these are the default excludes. If you don't have this file reinstall the plugin.


    If you make manual changes to snapriad.conf they will be lost the nest time you use the plugin to make any changes.


    To use the plugin to add excludes and includes, see the Rules tab.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • Thanks, after the upgrade to 3.7.7 my excludes are


    exclude /snapraid.conf*
    exclude *.unrecoverable
    exclude lost+found/
    exclude aquota.user
    exclude aquota.group
    exclude /tmp/
    exclude .content
    exclude *.bak


    So I should be fine now.

  • i have almost the same problem


    my conf:


    xclude *.unrecoverable

    exclude lost+found/

    exclude aquota.user

    exclude aquota.group

    exclude /tmp/

    exclude .content

    exclude *.bak

    exclude /snapraid.conf*



    yet i get:



    Data error in file '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/a quota.group' at position '0', diff bits 59/128

    Data error in file '/srv/dev-disk-by-uuid-7d46260d-a71f-4138-8ab1-8ae5bac8e8d6/a quota.user' at position '0', diff bits 71/128



    on another omv with the same setup there are no errors

    in both cases the rule section in the plugin are empty

    so my head have a hard time understading why 2 equal setups behave different... and only on 1 of 5 disk in the system with the problem

    both omv's are updated to latest version


    these defaults are in the config section of the plugin thou... so i assume they are in effect in both cass?

  • i added the excludes in the rules section, now they are there doubble in the config section


    will do a full force sync and see if the errors are there or not, will take a VERY loooooong time

    There are default excludes already in place. If you add the same ones yourself, you will get errors.


    Try running snapraid status instead of snapraid sync.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • root@bo-omv:~# snapraid status

    Self test...

    Loading state from /srv/dev-disk-by-uuid-2e4e0ef5-a94a-4973-9ca2-acf2c23f1d24/snapraid.content...

    Using 224 MiB of memory for the file-system.

    SnapRAID status report:


    Files Fragmented Excess Wasted Used Free Use Name

    Files Fragments GB GB GB

    7956 1 15 - 215 275 44% sdb1_disk1

    22042 62 192 505.8 1722 1708 50% sdc1_disk2

    757 5 49 - 137 176 43% sdd1_disk3

    2509 21 63 - 861 1106 43% sde1_disk4

    --------------------------------------------------------------------------

    33264 89 319 505.8 2937 3266 47%



    84%|o

    |*

    |*

    |*

    |*

    |*

    |*

    42%|*

    |*

    |*

    |*

    |*

    |*

    |* o

    0%|*________________________________________o__________________________oo

    1 days ago of the last scrub/sync 0


    The oldest block was scrubbed 1 days ago, the median 1, the newest 0.


    WARNING! The array is NOT fully synced.

    You have a sync in progress at 99%.

    The 16% of the array is not scrubbed.

    No file has a zero sub-second timestamp.

    No rehash is in progress or needed.

    No error detected.




    doing another full sync while i have dinner etc

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!