snapraid + adding new drive

  • Just use the plugin to add the new disk. SnapRaid can never delete data from a data disk.

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


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • okay, looks fine, thank you for prompt reply!


    Now one more question... i added drive as a data drive to snapraid... can i also add it into my UnionFS? At the moment i have one item inside UnionFS which consists of 3 drives that were part of the snapraid, so may I add this new drive with data into it? Wont be there any data loss?


    thank you

  • UnionFS, which on OMV 4 is actually mergerfs, will also not in and of itself delete data. So, just add the disk in via the UnionFS plugin..

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


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • hi,
    i replaced failing drive but still have multiple errors related to the mergerfs in dmesg...


    [44459.406162] EXT4-fs error (device sdd1): htree_dirblock_to_tree:990: inode #157287807: block 629154085: comm mergerfs: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4294967295, rec_len=65535, name_len=255
    [44459.443936] EXT4-fs error (device sdd1): htree_dirblock_to_tree:990: inode #157287807: block 629154085: comm mergerfs: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4294967295, rec_len=65535, name_len=255



    these kind of errors are popping up on drive.. even based on the smartctl it looks 100% ok and i unmounted drive, executed fsck on it, mounted it back... but errors are still popping ...


    any idea how to fix that issue.. i am desperate...thanks

  • UnionFS, which on OMV 4 is actually mergerfs, will also not in and of itself delete data. So, just add the disk in via the UnionFS plugin..

    @gderf do u have any idea reagarding my last post? there is almost 0 write operations to hdds and even i am getting these issue reported in post above. Is it bc of failing CPU/RAM?


    thank u

  • I can't comment on the problems you are having. Perhaps the mergerfs author who posts here can comment.

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


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • i emailed mergerfs guy nad he said there is no connection with mergerfs. He said the issue is on ext4, but there is no write on drives so i do not understand what is corrupting data?



    whats his nick?

  • There isn't much for me to add to the previous conversation. The error is not due to writes (directly). It's a reading of directory info issue (as the error indicates). mergerfs is in the logs because its the proxy for your app's requests. mergerfs is just a proxy. It runs in userspace like any other user software. It's not the cause of the error. It's only triggering it. mergerfs would have to write directly to the device, which it does not, for it to screw up the filesystem data structures itself.


    Look at the error: rec_len % 4 != 0 - offset=0(0), inode=4294967295, rec_len=65535, name_len=255


    The inode, rec_len, and name_len are all maxed out values. All 0xFF. The rec_len is 4 vs the expected 0. I don't know what the defaults are for those variables (I'd imagine 0) but they aren't just random data left over of some directory entry that became corrupted. This looks like it was explicitly set / overwritten.


    As I mentioned in my email this is either 1) a bug with ext4. Try a different kernel or different filesystem. 2) The CPU is faulty. 3) The RAM is faulty. 4) The drive is faulty. 5) something is going around corrupting the drive.


    The only time users have had those kinds of errors were as a result of the above situations.

  • @gderf is there any chance to upgrade kernel on omv3x ? if i dont want to upgrade to 4x

    I do not know what backport kernels are available on OMV 3, maybe as high as 4.9 What kernel are you running now?


    You really should upgrade to OMV 4.

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


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • @gderf its Linux openmediavault 4.9.61-odroidxu4
    Is it safe to upgrade to 4x? can i do it somehow from gui? configuration smb/nfs will remain?



    @trapexit i dont know, but i saw if i do ls /storage which is mergerer fs on top of all drives it takes ~15ec to see content,,, so maybe that sleep somehow breaks things? dunno

  • @gderf its Linux openmediavault 4.9.61-odroidxu4
    Is it safe to upgrade to 4x? can i do it somehow from gui? configuration smb/nfs will remain?

    I had no problems upgrading from OMV 3.x to 4.x on AMD64. But I followed the upgrade procedure exactly, including removing unsupported plugins and having a known to be restorable backup. I don't think you can upgrade in the GUI, I used the shell.

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


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • will try, thanks, got diff error today after i run fsck:



    [ 9102.609111] EXT4-fs error (device sdd1): htree_dirblock_to_tree:990: inode #150994945: block 603988000: comm mergerfs: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3656225552, rec_len=50358, name_len=105
    [24517.929619] EXT4-fs warning (device sdd1): dx_probe:751: inode #151259290: comm mergerfs: Unrecognised inode hash code 173
    [24517.929627] EXT4-fs warning (device sdd1): dx_probe:856: inode #151259290: comm mergerfs: Corrupt directory, running e2fsck is recommended
    [24518.219846] EXT4-fs warning (device sdd1): dx_probe:751: inode #151259290: comm mergerfs: Unrecognised inode hash code 173
    [24518.219853] EXT4-fs warning (device sdd1): dx_probe:856: inode #151259290: comm mergerfs: Corrupt directory, running e2fsck is recommended
    [24518.219970] EXT4-fs warning (device sdd1): dx_probe:751: inode #151259290: comm mergerfs: Unrecognised inode hash code 173
    [24518.219976] EXT4-fs warning (device sdd1): dx_probe:856: inode #151259290: comm mergerfs: Corrupt directory, running e2fsck is recommended
    [24518.220451] EXT4-fs warning (device sdd1): dx_probe:751: inode #151259290: comm mergerfs: Unrecognised inode hash code 173
    [24518.220457] EXT4-fs warning (device sdd1): dx_probe:856: inode #151259290: comm mergerfs: Corrupt directory, running e2fsck is recommended
    [24518.220555] EXT4-fs warning (device sdd1): dx_probe:751: inode #151259290: comm mergerfs: Unrecognised inode hash code 173
    [24518.220561] EXT4-fs warning (device sdd1): dx_probe:856: inode #151259290: comm mergerfs: Corrupt directory, running e2fsck is recommended

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!