NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Enable Bitrot on Files: MV or CP?
So I want to make sure that bitrot protection is enabled on my files, I don't recall if I had it enabled on my shares before files were placed there. According to the documentation you can create a ...
You can use "lsattr" to check if a file has CoW enabled or not.
Here my txt file does not have CoW enabled, denoted by the "C" in the end.
root@Databak:~# lsattr /data/Data-dump/MyFile_NoCoW.txt ---------------C /data/Data-dump/MyFile_NoCoW.txt
Here is what a file looks like, that has CoW enabled.
root@Databak:~# lsattr /data/Data-dump/MyFile_CoW.txt ---------------- /data/Data-dump/MyFile_CoW.txt
I don't think the "mv" command is enough to trigger CoW on a file that has previously been marked for No CoW - due to reasons that StephenB mentioned. I think you need to re-create the file - i.e. "cp"
But you can check on the files you moved :)
Everything from SSH, could do it via a network share but that would add network overhead.
MV across shares, takes some time - not instant.
MV within shares is instant. (note this was done after above, which may have created metadata?)
CP within a share is taking forever.
Hopefully someone from Netgear can chime in if an initial MV will create the metadata or not.
rhpot1991 wrote:
Everything from SSH, could do it via a network share but that would add network overhead.
MV across shares, takes some time - not instant.
MV within shares is instant. (note this was done after above, which may have created metadata?)
CP within a share is taking forever.
Hopefully someone from Netgear can chime in if an initial MV will create the metadata or not.
Please don't double-post. I replied here: https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Enable-Bitrot-on-Files-MV-or-CP/m-p/2066796
I replied to you.
rhpot1991 wrote:
I replied to you.
Sorry, it was showing up as a separate thread when I replied.
Perhaps rn_enthusiast or mdgm will chime in.
In order for bit-rot protection to work, you need both BTRFS checksums and RAID parity. My understanding is that the only safe way to create the BTRFS checksums is to copy the file data itself after checksums are enabled. That won't happen if the files are moved.
There is a linux command that can also recalculate the checksums - but it is considered dangerous. Normally the file system is unmounted before that command is run.
You can use "lsattr" to check if a file has CoW enabled or not.
Here my txt file does not have CoW enabled, denoted by the "C" in the end.
root@Databak:~# lsattr /data/Data-dump/MyFile_NoCoW.txt ---------------C /data/Data-dump/MyFile_NoCoW.txt
Here is what a file looks like, that has CoW enabled.
root@Databak:~# lsattr /data/Data-dump/MyFile_CoW.txt ---------------- /data/Data-dump/MyFile_CoW.txt
I don't think the "mv" command is enough to trigger CoW on a file that has previously been marked for No CoW - due to reasons that StephenB mentioned. I think you need to re-create the file - i.e. "cp"
But you can check on the files you moved :)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
