linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC] mke2fs: get device topology values from blkid
Date: Fri, 18 Sep 2009 09:04:37 -0500	[thread overview]
Message-ID: <4AB39375.6040506@redhat.com> (raw)
In-Reply-To: <20090918055547.GO2537@webber.adilger.int>

Andreas Dilger wrote:
> On Sep 17, 2009  17:22 -0500, Eric Sandeen wrote:
>> This is just a rough cut, due to the blkid header selection
>> issues I mentioned earlier on the list.  It'll also need
>> some config-fu to be sure we've got a blkid which has these
>> calls, but with it in place, we'll finally have automatic
>> selection of stride/stripe:
>>
>> # misc/mke2fs -b 4096 /dev/md0 
>> mke2fs 1.41.9 (22-Aug-2009)
>> Filesystem label=
>> OS type: Linux
>> Block size=4096 (log=2)
>> Fragment size=4096 (log=2)
>> Stride=16 blocks, Stripe width=32 blocks
>> ...
> 
> Cool.
> 
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>>  	printf(_("Fragment size=%u (log=%u)\n"), fs->fragsize,
>>  		s->s_log_frag_size);
>> +	printf(_("Stride=%u blocks, Stripe width=%u blocks\n"),
>> +	       s->s_raid_stride, s->s_raid_stripe_width);
> 
> I was going to say we should only print these if non-zero, but for
> Pete's sake we print the "Fragment size", which has never been useful,
> so I don't see any harm in this.  Maybe "RAID Stride ..."?
> 
>> +static errcode_t ext2fs_get_device_geometry(const char *file,
>> +					    struct ext2_super_block *fs_param)
>> +{
>> +	rc = blkid_probe_set_device(pr, fd, 0, 0);
> 
> Is this in the e2fsprogs blkid code yet?  I'm guessing not, since you

right, not yet.  I don't know what the long-term plan is for e2fsprogs 
blkid; keeping 2 trees in sync seems like a lot of work w/o much gain...

> are getting build problems, which means anyone building with something
> other than latest & greatest util-linux will also get failures.
> 
> Either this needs to be configured in, or you need to upgrade the
> blkid included with e2fsprogs to handle this.

Yep, that's why I said "It'll also need some config-fu to be sure we've 
got a blkid which has these calls...." :) and why I was asking about 
moving the in-tree headers slightly out of the way.

-Eric

> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
> 


  reply	other threads:[~2009-09-18 14:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 22:22 [PATCH, RFC] mke2fs: get device topology values from blkid Eric Sandeen
2009-09-18  5:55 ` Andreas Dilger
2009-09-18 14:04   ` Eric Sandeen [this message]
2009-09-18 14:20     ` Andreas Dilger
2009-09-18 14:30       ` Eric Sandeen
2009-09-18 16:43       ` Theodore Tso
2009-09-18 16:57         ` Eric Sandeen
2009-09-18  6:13 ` Martin K. Petersen
2009-09-18 14:18   ` Andreas Dilger
2009-09-18 14:23   ` Eric Sandeen
2009-09-18 19:40     ` Martin K. Petersen
2009-09-18 20:28       ` Andreas Dilger
2009-09-20 20:46         ` Martin K. Petersen
2009-09-22 14:30           ` Ric Wheeler
2009-09-18 23:59 ` Karel Zak
2009-09-19  3:03   ` Eric Sandeen
2009-09-21 17:06 ` [PATCH V2] " Eric Sandeen
2009-10-02 16:32   ` [PATCH V3] " Eric Sandeen
2009-10-04 19:16     ` Theodore Tso

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=4AB39375.6040506@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@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).