dlandon Posted September 9, 2014 Share Posted September 9, 2014 Once I updated to b8, I offloaded each disk in the array one at a time, formatted the disk XFS, and then reloaded each disk. As far as I know, I haven't had any issues. I don't do a lot of writing to my array. Mostly reads. I'm kind of glad I made the move to XFS on all my drives. Quote Link to comment
jumperalex Posted September 9, 2014 Share Posted September 9, 2014 Looks like I'll be running a checksum verify once b9 is released Quote Link to comment
archedraft Posted September 9, 2014 Share Posted September 9, 2014 Looks like I'll be running a checksum verify once b9 is released You read my mind! Quote Link to comment
dlandon Posted September 9, 2014 Share Posted September 9, 2014 Looks like I'll be running a checksum verify once b9 is released If files are corrupted, won't the parity also be corrupted? Quote Link to comment
jphipps Posted September 9, 2014 Share Posted September 9, 2014 Would beta 9 also have the fix for the race condition for XFS? Quote Link to comment
chuga Posted September 9, 2014 Share Posted September 9, 2014 So after I update to b9, if I delete everything I uploaded while on B8 and recopy will it be ok? I only copied a few rips over, which I can redo. Or from an earlier post if I understand correctly just the fact that I copied a few new files to the array on b8 means existing files could have been corrupted not just the new files I copied over? Will be quite some work if other stuff is corrupted ..... But I knew the risks when running beta Thanks Chuga Quote Link to comment
jumperalex Posted September 9, 2014 Share Posted September 9, 2014 Looks like I'll be running a checksum verify once b9 is released If files are corrupted, won't the parity also be corrupted? not parity, checksum hashes. I have one for every file on my array. Quote Link to comment
jonp Posted September 9, 2014 Share Posted September 9, 2014 Great questions. We are working to discover answers. Quote Link to comment
trurl Posted September 9, 2014 Share Posted September 9, 2014 Nothing in my nzbget queue at the moment. The only other process I have that writes to the array is transmission. I guess I will just stop it for now and hope we get a resolution soon. I can just set the security of the user shares to prevent any other writes. Quote Link to comment
dalben Posted September 10, 2014 Share Posted September 10, 2014 In the process of migrating my array disks to xfs I would have re-written my nearly my entire data, 7tb, onto rfs disks to make room for xfs. If I'm screwed, I'm screwed. If a utility gets made to check for corruption I'd want to get my hands on it pretty quickly. Quote Link to comment
limetech Posted September 10, 2014 Author Share Posted September 10, 2014 Would beta 9 also have the fix for the race condition for XFS? Yes Quote Link to comment
PeterB Posted September 10, 2014 Share Posted September 10, 2014 I suspect that I've already encountered this bug ... After I'd copied my LogitechMediaServer configuration files to appdata, while moving to Docker, I found that one of my LMS plugins wasn't starting up. Checking the error log, I could see that a syntax error was being reported for one of the .pl source files. Upon inspection, I discovered that the source file was truncated. I still had the original, so re-copied that one file, and all seems fine now. Eagerly awaiting beta9 now .... Quote Link to comment
Manticore Posted September 10, 2014 Share Posted September 10, 2014 For downgrading, what files should be changed/deleted? Quote Link to comment
smdion Posted September 10, 2014 Share Posted September 10, 2014 I suspect that I've already encountered this bug ... After I'd copied my LogitechMediaServer configuration files to appdata, while moving to Docker, I found that one of my plugins wasn't starting up. Checking the error log, I could see that a syntax error was being reported for one of the .pl source files. Upon inspection, I discovered that the source file was truncated. I still had the original, so re-copied that one file, and all seems fine now. Eagerly awaiting beta9 now .... Doesn't docker need BTRFS, and this only applies to REISER? Quote Link to comment
PeterB Posted September 10, 2014 Share Posted September 10, 2014 I suspect that I've already encountered this bug ... After I'd copied my LogitechMediaServer configuration files to appdata, while moving to Docker, I found that one of my plugins wasn't starting up. Checking the error log, I could see that a syntax error was being reported for one of the .pl source files. Upon inspection, I discovered that the source file was truncated. I still had the original, so re-copied that one file, and all seems fine now. Eagerly awaiting beta9 now .... Doesn't docker need BTRFS, and this only applies to REISER? Incorrect logic, on two counts. Firstly, as of beta8, the docker btrfs is a logical device which can exist on any host file system. Secondly, the appdata is held on an ordinary user share because it needs to be accessible from the host system. Quote Link to comment
PeterB Posted September 10, 2014 Share Posted September 10, 2014 Beta 9 is imminent. Wait for it.. Imminent - as in 1-2 hours, or 1-2 days? My largest array drive is 2TB but I only have 2 almost-empty 1TB drives (cache and docker drives), and am contemplating moving to xfs formatted drives via these two. Quote Link to comment
jonp Posted September 10, 2014 Share Posted September 10, 2014 Beta 9 is imminent. Wait for it.. Imminent - as in 1-2 hours, or 1-2 days? My largest array drive is 2TB but I only have 2 almost-empty 1TB drives (cache and docker drives), and am contemplating moving to xfs formatted drives via these two. Need to put the build through some testing before we will release. Quote Link to comment
doubleohwhatever Posted September 10, 2014 Share Posted September 10, 2014 It's more likely to affect small files than larger ones Can you define small? I ask because nothing on my system is smaller than a gigabyte. Quote Link to comment
generalz Posted September 10, 2014 Share Posted September 10, 2014 huh sucks, just moved about 500 gigs of stuff around Quote Link to comment
hackztor Posted September 10, 2014 Share Posted September 10, 2014 So far I have found one file that corrupted it was a 25gb. Good news it seems to 400GB others that I moved to different disks yesterday are still working. Quote Link to comment
PeterB Posted September 10, 2014 Share Posted September 10, 2014 Okay, so the reported corruptions are truncated files and garbage at beginning of files. So, it would seem that the file truncation I experienced was, almost certainly, caused by this bug. The frightening thing is Filesystem is clean and reiserfsck found nothing. meaning that there is no known way of detecting the corruption except by examining the file contents! Quote Link to comment
jbartlett Posted September 10, 2014 Share Posted September 10, 2014 Looks like I'll be running a checksum verify once b9 is released I've been working on a script called "bitrot" that generates a SHA256 key fore files and stores it as an extended attribute on the file itself. I've got my media scanned, I'll be running a verify after beta 9. I'll try to get the script posted soon, was working on adding nice-to-have features. Quote Link to comment
binhex Posted September 10, 2014 Share Posted September 10, 2014 Looks like I'll be running a checksum verify once b9 is released I've been working on a script called "bitrot" that generates a SHA256 key fore files and stores it as an extended attribute on the file itself. I've got my media scanned, I'll be running a verify after beta 9. I'll try to get the script posted soon, was working on adding nice-to-have features. i would very interested in getting a copy of the script! Quote Link to comment
aatti Posted September 10, 2014 Share Posted September 10, 2014 Running Beta 7 since some time and moved around 2.5 T of data from ReiserFS to XFS. Some files had SHA checksums just as control mechanism so I guess/hope everything is fine. Biggest issue is the router runs as a VM and is stored on the cache drive which is still ReiserFS and this machine writes a bit of data on daily basis (logs)... still running. I'll let you know if something unusual happens. Sadly, there is no way to stop the router and replace it with another at this moment. Quote Link to comment
gshlomi Posted September 10, 2014 Share Posted September 10, 2014 OMG. I've used BTSync to sync all my data from my main server (5.0.5) to my backup/test server ( 6beta8 ). Unfortunately, I've used two-way sync. As soon as I saw this thread I've shutdown my backup server. Is there a way I can check my data on the main server to find corruptions? Thanks... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.