On Fri, Jun 15, 2018 at 08:39:05PM -0400, Theodore Y. Ts'o wrote:
> On Tue, Jun 12, 2018 at 11:38:15PM -0700, Elliott Mitchell wrote:
> > # 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?

During the process I ended up running `e2fsck -f` multiple times.  I
ended up running `e2fsck -f` after enabling each feature (`tune2fs`
really didn't like enabling multiple features at once).

The dumpe2fs will take a bit to get to...

> 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....

I definitely want user quota with journal.  I'm unsure of group and
project.


> > 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?

I'm pretty sure mmp is appropriate in this case.  This is a server with
multiple VMs.  A few times I have found it useful to access guest
filesysterms from the hypervisor, such as the upgrade `tune2fs` operation
I was doing here.  Adjusting the guest /etc/fstab from the hypervisor was
also useful.  This opens the door to accidentally mounting the guest
root filesystem read-write from the hypervisor, while the guest has the
filesystem mounted read-only (or worse mounting it read-write in both
locations at the same time; *crunch*).

So yes, I believe I have a case where MMP functionality is useful.
Hopefully I won't actually need it, but it should be useful to defend
against operator error (I like to think I'm perfect, but experience has
demonstrated otherwise).


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sig...@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Reply via email to