From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs_repair: check and repair quota metadata
Date: Tue, 8 May 2018 09:28:37 +1000 [thread overview]
Message-ID: <20180507232837.GH23861@dastard> (raw)
In-Reply-To: <20180507163242.GZ26569@magnolia>
On Mon, May 07, 2018 at 09:32:42AM -0700, Darrick J. Wong wrote:
> On Mon, May 07, 2018 at 09:20:28AM -0500, Eric Sandeen wrote:
> > Today, quota inodes are not checked at all in xfs_repair. (This is
> > a little odd, because xfs_check used to do it in process_quota()).
> >
> > The kernel has quota inode validation and repair routines, but it is
> > out of the ordinary for the kernel to be doing metadata repair. And
> > now that we have metadata verifiers, this also yields a surprisingly
> > noisy mount if quota inodes are corrupted, even immediately after an
> > xfs_repair.
> >
> > So this patch allows xfs_repair to fix the quota inode metadata.
> >
> > Quotacheck is still left for the kernel. After a few more releases,
> > I'll propose removing the repair calls from the kernel, and move the
> > repair functions from libxfs/ into the repair code.
> >
> > Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> > ---
> >
> > This will need a bit of adjustment when my other quota patches land
> > in 4.18, but that should be no big deal.
> >
> > diff --git a/libxfs/libxfs_priv.h b/libxfs/libxfs_priv.h
> > index ab195f5f..e5eb3de1 100644
> > --- a/libxfs/libxfs_priv.h
> > +++ b/libxfs/libxfs_priv.h
> > @@ -196,8 +196,6 @@ enum ce { CE_DEBUG, CE_CONT, CE_NOTE, CE_WARN, CE_ALERT, CE_PANIC };
> > # define barrier() __memory_barrier()
> > #endif
> >
> > -#define XFS_DQUOT_CLUSTER_SIZE_FSB (xfs_filblks_t)1
> > -
> > /* miscellaneous kernel routines not in user space */
> > #define down_read(a) ((void) 0)
> > #define up_read(a) ((void) 0)
> > diff --git a/libxfs/xfs_quota_defs.h b/libxfs/xfs_quota_defs.h
> > index bb1b13a9..067475e2 100644
> > --- a/libxfs/xfs_quota_defs.h
> > +++ b/libxfs/xfs_quota_defs.h
> > @@ -30,6 +30,8 @@
> > typedef uint64_t xfs_qcnt_t;
> > typedef uint16_t xfs_qwarncnt_t;
> >
> > +#define XFS_DQUOT_CLUSTER_SIZE_FSB (xfs_filblks_t)1
>
> Requires a kernel patch, right? :)
It's already defined in the kernel in fs/xfs/xfs_qm.h.
And userspace also defines it as a private define to allow libxfs to
build:
$ git grep XFS_DQUOT_CLUSTER_SIZE_FSB
libxfs/libxfs_priv.h:#define XFS_DQUOT_CLUSTER_SIZE_FSB (xfs_filblks_t)1
libxfs/xfs_trans_resv.c: XFS_FSB_TO_B(mp, XFS_DQUOT_CLUSTER_SIZE_FSB) - 1);
libxfs/xfs_trans_space.h: XFS_DQUOT_CLUSTER_SIZE_FSB)
$
If it's going to be used outside libxfs in userspace, then it should
be lifted to a libxfs header file both in the kernel and userspace,
such as fs/xfs/xfs_quota_defs.h....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-05-07 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 14:20 [PATCH] xfs_repair: check and repair quota metadata Eric Sandeen
2018-05-07 16:32 ` Darrick J. Wong
2018-05-07 16:44 ` Eric Sandeen
2018-05-07 16:59 ` Darrick J. Wong
2018-05-07 23:28 ` Dave Chinner [this message]
2018-05-07 23:30 ` Eric Sandeen
2018-05-07 23:43 ` [PATCH V2] " Eric Sandeen
2018-05-07 23:54 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180507232837.GH23861@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox