On 2015-10-08 18:22, Hugo Mills wrote:
I have to agree with Hugo here, it really sounds like you have hardware issues. If the new HDD doesn't completely fix things, try replacing the cabling (because that's the easy to fix without spending a lot of money, and having spare cables is usually a good thing), then try the controller or RAM.On Fri, Oct 09, 2015 at 12:16:43AM +0200, Pavel Pisa wrote:Hello Hugo,On Thursday 08 of October 2015 23:13:52 Hugo Mills wrote:On Thu, Oct 08, 2015 at 07:47:33AM -0400, Austin S Hemmelgarn wrote:On 2015-10-08 04:28, Pavel Pisa wrote:I go to use "btrfs replace" because there has not been any reply to my inplace correction question. But I expect that clarification if possible/how to resync RAID1 after one drive temporal disappear is really important to many of BTRFS users.As of right now, there is no way that I know of to safely re-sync a drive that's been disconnected for a while. The best bet is probably to use replace, but for that to work reliably, you would need to tell it to ignore the now stale drive when trying to read each chunk.Scrub is officially what you need there. I can confirm that it works correctly, having used it myself after accidentally unplugging the wrong drive.Thanks for the reply. I have tried to run scrub after reconnect but it counted errors in its console output and write errors has been logged by kernel as crazy. I have to admit I have not wait to finish it because I have not good feeling from it.If the scrub works OK, you will still get lots of scary-looking errors in the logs, but they'll usually say it's repaired the problem. Getting write errors at this point indicates that you have hardware problems of some kind, and (usually) that device needs to be replaced. (Or the controller, or the cabling).May it be it was result of not fully correct reconnect. But other partition worked with ext4 has no problems to write. But if mount/unmount (in my case requiring reboot) and then scrub worked it would be much simpler than replaces series. I hope I would not need that (at least soon/in years) but I give try to scrub again. May it be problem is my btrfs tools old version on the server -- Wheezy Btrfs v3.17 backport. Kernel is Linux 4.1.2 #1 SMP PREEMPT.No, the version of the tools has no effect on any of this. It really sounds like you have hardware issues.
smime.p7s
Description: S/MIME Cryptographic Signature
