Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scrubbing causes system lockup when running bitcoind #2067

Closed
lancethepants opened this issue Jan 21, 2014 · 3 comments
Closed

Scrubbing causes system lockup when running bitcoind #2067

lancethepants opened this issue Jan 21, 2014 · 3 comments
Labels
Type: Performance Performance improvement or performance problem
Milestone

Comments

@lancethepants
Copy link

I'm running Debian Wheezy. I am using a 4 disk mirror configuration. I have one zfs file system that mounts to my home directory. I also have bitcoind running, which is stored in my home directory.
Whenever I run a scrub and bitcoind is running (daemonized), the whole system freezes up. The computer is neither accessible remotely, nor locally by ssh or login. I can still ping the box, but it will not serve anything. After a hard reboot, the scrub will successfully work when I kill bitcoind first. Tested this a couple times, and seems apparent to me that running bitcoind is causing the issue.

@AndCycle
Copy link

my configuration is 3 disk raidz,

I didn't get the lock up under Gentoo sys-fs/zfs-0.6.2-r2 with kernel 3.12.5,
but I do see bitcoind occupy 1st place in iotop,
so I move to current git version and that problem just gone,

I will suggest you tryout git head version, at least it works and haven't corrupt my entire system.

@behlendorf
Copy link
Contributor

We try very hard to ensure master is always safe to run. That said, there is always the possibility the something will accidentally sneak in. But even in those case it's exceptionally unlikely to cause any persistent damage to the pool. Keeping your data safe is always job number one.

So I'd encouraging you also to try the latest source from Git. I think there's a pretty good chance it will resolve your issue.

@behlendorf
Copy link
Contributor

This has been resolved in 0.6.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Performance Performance improvement or performance problem
Projects
None yet
Development

No branches or pull requests

3 participants