![]() ![]() ![]() # echo 512 > /sys/module/zfs/parameters/zfs_flags ![]() # echo 1 > /sys/module/zfs/parameters/zfs_flagsĬannot mount 'tank/backup/root': Input/output error (And if none of those are new with the unlock attempt or relevant, you could try echo 512 |. I'd be curious, if you do go back to 2.1.5 and it goes boom again, whether you could try doing echo 1 | sudo tee /sys/module/zfs/parameters/zfs_flags, attempt the mount again, and then look in /proc/spl/kstat/zfs/dbgmsg and see what the last dozen or two entries are. ![]() (You could confirm it's a decryption error by looking in /proc/spl/kstat/kcf/NONAME_provider_stats after attempting it, I believe.) I'm not quite sure what you'd be hitting here - there have been a few fixes to encryption bugs since 2.0.1, but none of them should (AFAIK) reduce the number of things that can be unlocked, and I suspect the existing issue is still there if you go back to 2.1.5, the error just got removed from the log because it was a decryption error and scrub won't find those. Going forward should only require explicitly enabling new things in order to use existing functionality in the event of show-stopping bugs, AFAIK, and none of those should really apply here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |