Zfs: Trying to build the 'zhack' disable feature commit from a few years ago

[RNCTX]

Hello, as referenced by others like this issue here, I have a pool that was mistakenly upgraded under Linux that needs to go back to FreeBSD. Unfortunately userobj_accounting is enabled, which means that FreeBSD won't take the pool due to an unsupported feature.

I saw mention of this commit enabling feature disable functionality. I grabbed a Ubuntu 14.04 boot disk and installed ZoL (and an SPL from about that time) from that pull request, but am still getting reference to userobj_accounting being an "unsupported feature" when I try to import the pool.

I'm not sure if the pool should be mounted or not?

With the pool exported, trying zhack returns:

root@ubuntu:~/zfs# zhack feature disable media org.zfsonlinux:userobj_accounting
zhack: feature 'org.zfsonlinux:userobj_accounting' is active, can not disable

[loli10K]

Why are you ignoring both rules and requests (https://github.com/zfsonlinux/zfs/issues/6466#issuecomment-320420368)? Please use the issue template if you found a bug, otherwise ask the mailing lists (https://github.com/zfsonlinux/zfs/wiki/Mailing-Lists).

Thank you for your cooperation.

[RNCTX]

The question I asked was in regard to the lead developer of this project making a patch for himself to use on a catch22 in feature flags, and therefore not addressed to you. Nor is it addressed to anyone else that is using a current version of this software, since the relevant patch is over three years old (and now deprecated).

Thank you for your cooperation.

What makes you think I'm agreeing with anything you typed? Don't thank me, I'm not.

Thank you, for nothing. I'd file a bug report about people with pedophile'ish usernames with such high exposure in a project that Canonical seems to care so much about, but your form is (predictably) excessive. No thanks.

For those who might find this on Google, don't bother with that patch/commit. If your pool got userobj_accounting enabled it is now a Linux-only pool. You'll have to destroy it, since per the (broken) explanation in the manpage, once active it cannot be decactivated. Sort of like that Doomsday Machine that Slim Pickens was after....

[mschilli87]

The question I asked was in regard to the lead developer of this project making a patch for himself to use on a catch22 in feature flags, and therefore not addressed to you. Nor is it addressed to anyone else that is using a current version of this software, since the relevant patch is over three years old (and now deprecated).

Still, you post on a bug report platform watched by > 400 people that get emailed for each of your posts.

What makes you think I'm agreeing with anything you typed? Don't thank me, I'm not. [childish personal attacks]

Nobody asked for your opionion. There are rules established by the community, people who largely work on this project for free, an you can either stick to their rules, not contribute (anything) at all, or fork the project and work on your fork under your own rules. :wink:

---

I'll unsubscribe from this issue and won't comment here further.