From: Stefan Ring <stefanrin@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/1] xfs_metadump: Zap more stale data
Date: Sun, 7 Oct 2018 11:43:16 +0200 [thread overview]
Message-ID: <CAAxjCEzGykBJLp7mssn7f3MJoS3nx6DmsXSuiNn+T7qGSYPk4w@mail.gmail.com> (raw)
In-Reply-To: <20181005204057.GB19324@magnolia>
On Fri, Oct 5, 2018 at 10:41 PM Darrick J. Wong <darrick.wong@oracle.com> wrote:
> > I forgot to mention this: sb_blocksize is used conspicuously rarely in
> > this file. Is this the right metric to lean on?
>
> No, because directory blocks span multiple fs blocks (good self catch!).
>
> You could look it up in the directory geometry structure in the
> xfs_mount *.
Interestingly my file system has dirblklog = 0. I guess I'll have to
start creating some toy file system images for experimentation.
next prev parent reply other threads:[~2018-10-07 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 20:57 [PATCH 0/1] Try to squash metadump data leaks Stefan Ring
2018-10-04 20:57 ` [PATCH 1/1] xfs_metadump: Zap more stale data Stefan Ring
2018-10-04 22:23 ` Darrick J. Wong
2018-10-05 20:46 ` Stefan Ring
2018-10-05 20:57 ` Darrick J. Wong
2018-10-05 20:35 ` Stefan Ring
2018-10-05 20:40 ` Darrick J. Wong
2018-10-07 9:43 ` Stefan Ring [this message]
2018-10-07 11:57 ` Stefan Ring
2018-10-07 16:21 ` Darrick J. Wong
2018-10-10 9:37 ` Stefan Ring
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=CAAxjCEzGykBJLp7mssn7f3MJoS3nx6DmsXSuiNn+T7qGSYPk4w@mail.gmail.com \
--to=stefanrin@gmail.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).