Well the rsync --sparse finished. The old drive has 2.8TB used and the new one has 2.9TB used. The rsync command said it copied 4.2TB of data. Afterwards I updated to 6.3.3 and ran the reiserfsck on the old drive and it checked out fine, no corruption.
I'm not sure what to do next. Do I just go ahead and finish my conversion?
Thanks,
Doug
Thanks for the info. I'm trying the --sparse command first but I really don't think that's the issue. I certainly didn't put them there, but I suppose some process could have.
I have a feeling it goes back to some of the corruption issues I had last year with the SAS2LP card and the reiserfsck is going to be the solution, but we'll see.
Thanks again,
Doug
Hey guys,
I need some help converting my last reiserfs disk. All the rest have gone fine, but this one is behaving oddly. I'm copying Disk 8 (4TB) to Disk 13 (4TB) using the rsync command in the wiki page. As you can see the it's already copied more data than the array shows the original drive having. I tried this once already and it filled up my 4TB drive and wasn't done yet. The main page tells me the drive is only using 2.8TB, but it fills up a 4TB drive trying to do the copy? What's going on? Below is a pic and enclosed are the diagnostics.
tower-diagnostics-20170404-2052.zip
I was still running version 6.1.9 so I decided to give the upgrade a try. The upgrade to 6.3.2 went smooth and everything seems to be working okay.
I tried the copy from Windows again and this time it succeeded. It's still a bit odd though as the copy speed fluctuates from 100+ MB/s down to < 1 MB/s. It stalled a few times but ultimately didn't fail though which is good.
Are these wide speed fluctuations normal now?
Doug
Agreed that number seems fairly normal. It just felt slow while I was watching it.
When I try to copy from Windows to the Array it's still failing though. The copy starts okay, but then trails off to nothing and eventually fails.
So I was able to copy the file from the cache disk to the array using midnight commander. It seemed quite slow but was successful. It said it was copying around 33 MB/s.
I rebooted and ran a fresh set of diagnostics in case there is anything at startup that might be helpful.
No change to the behavior after reboot.
tower-diagnostics-20170316-2017.zip
Hi folks,
Suddenly today I am not able to copy large files to my array. I don't see any issues on the dashboard, but when I copy to a Share it starts fine, but the speeds slows way down and eventually fails. I tried copying to the Cache drive and that works just fine.
Enclosed are my diagnostics.
Any ideas what's going on?
Thanks,
Doug
tower-diagnostics-20170316-1951.zip
Well I think the problem may be the additional memory I just installed. I reverted to 6.1.7 and then had another segfault, but it was in one of my dockers this time. Going to try removing the memory and see how it goes.
Memtest on boot menu.
Over 2 hours and no more segfaults. Looks like it's either bad memory or just a bad combination. I'll check out the memtest and move this discussion to the hardware forum if I need further assistance.
Thanks for the help!
Doug
Well I think the problem may be the additional memory I just installed. I reverted to 6.1.7 and then had another segfault, but it was in one of my dockers this time. Going to try removing the memory and see how it goes.
I upgraded to 6.1.8 today and I've had kernel crashing issues twice now. This time I think I may have caught the error that is triggering it. I've enclosed the diagnostics here. It looks like the array is getting disconnected.
tower-diagnostics-20160214-1854.zip
I'm running 6.1.6 and I wasn't able to update via the Plugins page. I tried several times and it just kept telling me there was no update available. I restarted the server and tried again and it found the update okay. The update installed okay and everything seems to be normal.
Doug