All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Shailendra Tripathi <stripathi@agami.com>,
	Rene Salmon <rsalmon@tulane.edu>,
	xfs@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: LVM and XFS cannot set blocksize on block device
Date: Mon, 02 Oct 2006 17:28:10 +1000	[thread overview]
Message-ID: <4520BF8A.4090602@sgi.com> (raw)
In-Reply-To: <20060928153218.GA26366@tuatara.stupidest.org>

Chris Wedgwood wrote:
> On Thu, Sep 28, 2006 at 08:23:43PM +1000, Tim Shimmin wrote:
> 
>> I'll have a look soon at passing the mkfs.xfs -s option thru to
>> libxfs which is consistent with the existing code.
> 
> (following up on something mentioned off the list)
> 
> When you do this change please consider *not* making the code fallback
> to a different blocksize if the ioctl fails when "-s size=" is given.
> 
> The logic here is that if someone clearly wants a specific value and
> if that cannot be met it should error out with a suitable message, not
> silently do something else.

I agree.
I prefer default behaviour to happen when we are using the defaults -
so we can do fallback behaviour under the assumption the user
doesn't mind.
But when we ask for something explicitly, then do it or error out.
:)

I'd be tempted to reuse libxfs_init_t's setblksize to be 1 as it currently
is if one wants the device blksize to be set and
 >1 (really > 512 etc...) if one wants to set it to a particular value.

--Tim

  reply	other threads:[~2006-10-02  7:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 22:11 LVM and XFS cannot set blocksize on block device Rene Salmon
2006-09-26  0:17 ` Chris Wedgwood
2006-09-26 13:58   ` Rene Salmon
2006-09-26 22:40     ` Chris Wedgwood
2006-09-27 11:55       ` Shailendra Tripathi
2006-09-27 13:16         ` Rene Salmon
2006-09-28 10:33           ` Tim Shimmin
2006-09-27 15:48         ` Eric Sandeen
2006-09-28 10:23         ` Tim Shimmin
2006-09-28 15:32           ` Chris Wedgwood
2006-10-02  7:28             ` Timothy Shimmin [this message]
2006-10-03  7:35         ` Timothy Shimmin
2006-10-06 20:36           ` Rene Salmon
2006-10-11  9:59             ` Timothy Shimmin

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=4520BF8A.4090602@sgi.com \
    --to=tes@sgi.com \
    --cc=cw@f00f.org \
    --cc=rsalmon@tulane.edu \
    --cc=sandeen@sandeen.net \
    --cc=stripathi@agami.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.