Date: Mon, 24 Sep 2018 22:59:44 +0100 From: Chris Rees <crees@bayofrum.net> To: Miroslav Lachman <000.fbsd@quip.cz>, fs@freebsd.org Subject: Re: ZFS and chflags Message-ID: <551A17FF-1A7B-4F41-8D65-FFBB89348296@bayofrum.net> In-Reply-To: <8541779c-9a64-d277-b749-b36a120d9c67@quip.cz> References: <59BBABA0-9B8F-4CDA-AFF1-39D3508C0C6E@bayofrum.net> <8541779c-9a64-d277-b749-b36a120d9c67@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey, On 24 September 2018 22:44:48 BST, Miroslav Lachman <000.fbsd@quip.cz> wrot= e: >Chris Rees wrote on 2018/09/24 23:08: >> Hi all, >>=20 >> I don't know if it's some sort of veneer, but two of my machines >actually have started supporting file flags (schg for example), which >makes pkgbase happy. >>=20 >> My remaining machine, which I've managed to shoehorn 11.2-R onto >after a 2014 head, still says chflags: Unsupported by device, causing >pkg to error out. I was hoping the new kernel would sort this out, but >it appears to still happen. >>=20 >> I can't find anything on Google, and was wondering what is different >between the three computers. I know ZFS doesn't support them, but they >do work on two of them! >>=20 >> Please let me know if I should be asking on pkgbase@ > >Are all your machines on the same ZFS pool version? What about "zpool=20 >upgrade" and "zfs upgrade"? Uh, thanks! I'd done zpool upgrade and forgotten about zfs upgrade... I b= et that'll work. I'll update when I have a chance. Chris=20 --=20 Sent from my Android device with K-9 Mail. Please excuse my brevity. --=20 This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?551A17FF-1A7B-4F41-8D65-FFBB89348296>