On Tue, Jun 12, 2018 at 11:38:15PM -0700, Elliott Mitchell wrote:
> Package: e2fsproc
> Version: 1.43.4-2
>
> Subject tells the story:
>
> # tune2fs -O dir_index,extent,metadata_csum,mmp,quota -Q
> usrquota,grpquota,prjquota /dev/foo
> tune2fs 1.43.4 (31-Jan-2017)
> [ERROR] ../../../../lib/support/quotaio.c:275:quota_file_open::
> qh_ops->check_file failed
> tune2fs: Unknown code ____ 255 while updating quota limits (0)
I apologize for lousy error messages from the quota handling code, in
particular.
Can you tell me something about the file system you were starting
with? In particular, can you send me the output of dumpe2fs -h.
Also, have you tried running e2fsck on the file system in question
first?
Finally, what are you trying to do? It looks like you're starting
with an old ext file system and trying to enable a bunch of new ext4
features? Why do you need to enable all of these features? In
particular, unless you really know what you are doing, you probably
don't need mmp.
And do you really need to enable user, group, and project quota
tracking? Please keep in mind there is a performance cost for
enabling quota tracking; it is definitely not free....
> All of the other features had been successfully enabled with some
> trouble (mostly needing several runs of `fsck -f`), but quota enabling
> failed.
>
> The error messages from `tune2fs` were less than helpful during the
> process of getting flags enabled. "mmp" was particularly troublesome.
How so? And again, why do you need (or think you need) mmp?
- Ted
