public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: xfs@oss.sgi.com
Subject: different log info for mkfs.xfs and xfs_growfs
Date: Sat, 17 Apr 2010 22:59:47 +0800	[thread overview]
Message-ID: <20100417145947.GA2573@laptop.oracle.com> (raw)

Hi experts,

I just noticed that the log info is different for mkfs.xfs and
xfs_growfs.

[root@desk test-xfsprogs]# mkfs.xfs -llogdev=/dev/sda11,size=32768b
/dev/sda10 -f
meta-data=/dev/sda10             isize=256    agcount=4, agsize=1250558
blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=5002231, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =/dev/sda11             bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0
[root@desk test-xfsprogs]# mount -ologdev=/dev/sda11 /dev/sda10 /xfs
[root@desk test-xfsprogs]# xfs_growfs -n /xfs 
meta-data=/dev/sda10             isize=256    agcount=4, agsize=1250558
blks
         =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=5002231, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =external               bsize=4096   blocks=32768, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=0
realtime =none                   extsz=4096   blocks=0, rtextents=0

So xfs_growfs is simply reporting external.

Why there is such a difference? And how get to know the log device name after it
is mounted?

It's 3.0.0 of xfsprogs. I failed to test with upstream because of the
comlilation error:
[wwg@desk xfsprogs.git]$ make
Building include
Building libxfs
    [DEP]
/usr/bin/makedepend: warning:  ignoring option -Wall
/usr/bin/makedepend: error:  cannot open "no-strict-aliasing"
    [LD]     libxfs.la
libtool: link: only absolute run-paths are allowed
gmake[2]: *** [libxfs.la] Error 1
gmake[1]: *** [libxfs] Error 2
make: *** [default] Error 2

regards,
wengang.

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

             reply	other threads:[~2010-04-17 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 14:59 Wengang Wang [this message]
2010-04-18  3:13 ` different log info for mkfs.xfs and xfs_growfs Eric Sandeen
2010-04-19  3:45   ` Wengang Wang

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=20100417145947.GA2573@laptop.oracle.com \
    --to=wen.gang.wang@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox