All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Jan Tulak <jtulak@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: What is the meaning of XLOG_MIN_RECORD_BSIZE? (Missing a check?)
Date: Fri, 19 Feb 2016 11:29:13 -0500	[thread overview]
Message-ID: <20160219162913.GC27263@bfoster.bfoster> (raw)
In-Reply-To: <CACj3i72wijiApA0gD0mRrMvPomDC5pEAr1Mvv6e3vi4HU1S_sw@mail.gmail.com>

On Fri, Feb 19, 2016 at 05:16:28PM +0100, Jan Tulak wrote:
> On Fri, Feb 19, 2016 at 4:43 PM, Brian Foster <bfoster@redhat.com> wrote:
> 
> > On Fri, Feb 19, 2016 at 02:34:52PM +0100, Jan Tulak wrote:
> > > Hi guys,
> > >
> > > what is the meaning of XLOG_MIN_RECORD_BSIZE in libxfs/xfs_log_format.h?
> > > It is not used anywhere. I thought it might be related to -l su/sunit
> > > option, but seeing tests with -l su=4096 (the macro is set to 16k), it
> > > looks more like a forgotten value.
> > >
> >
> > It's the minimum log buffer size allowed in the kernel. It's used in
> > xfs_super.c at mount time to validate the logbsize option:
> >
> >         if (mp->m_logbsize != -1 &&
> >             mp->m_logbsize !=  0 &&
> >             (mp->m_logbsize < XLOG_MIN_RECORD_BSIZE ||
> >              mp->m_logbsize > XLOG_MAX_RECORD_BSIZE ||
> >              !is_power_of_2(mp->m_logbsize))) {
> >                 xfs_warn(mp,
> >                         "invalid logbufsize: %d [not 16k,32k,64k,128k or
> > 256k]",
> >                         mp->m_logbsize);
> >                 return -EINVAL;
> >         }
> >
> > I suspect it's not relevant in userspace.
> >
> 
> This is ok, then. Thank you for pointing me to kernel space, I didn't
> realised I should check it there too. :-)
> ​
> 
> 
> >
> > > There is no check for a minimal value, so I can do -l su=1 (or su=0). Are
> > > there some caveat​s (other than performance) with such a small value? Can
> > > it be that we are missing a check? Because
> > > XLOG_BIG_RECORD_BSIZE
> > > ​ and XLOG_MAX_RECORD_BSIZE are used and the upper bound is limited.​..
> > >
> >
> > On a quick test, it looks like mkfs just ignores certain log stripe unit
> > values that aren't block aligned. I'd probably expect this to behave
> > similar to the '-d su' option and complain about invalid input..?
> >
> 
> ​Sounds logical and like what I expected and didn't found. I will send a
> patch adding this check... the only question is, what should be the minimal
> value? Should I check it against block size and forbid smaller sizes?
> Aligning a stripe unit with length 1024 on 4096 blocks doesn't looks like a
> nice thing. :-)
> (And on a quick check, it seems that -d su is doing just that.)
> 

The man page says it must be a multiple of the fsb size. Indeed, '-d su'
complains about anything that is less than 1 FSB, so I would just go
with that. :)

Brian

> Thanks,
> Jan
> 
> -- 
> Jan Tulak
> jtulak@redhat.com / jan@tulak.me

> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-02-19 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 13:34 What is the meaning of XLOG_MIN_RECORD_BSIZE? (Missing a check?) Jan Tulak
2016-02-19 15:43 ` Brian Foster
2016-02-19 16:16   ` Jan Tulak
2016-02-19 16:29     ` Brian Foster [this message]
2016-02-21 23:18       ` Dave Chinner
2016-02-22  8:38         ` Jan Tulak

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=20160219162913.GC27263@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=jtulak@redhat.com \
    --cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.