* different log info for mkfs.xfs and xfs_growfs
@ 2010-04-17 14:59 Wengang Wang
2010-04-18 3:13 ` Eric Sandeen
0 siblings, 1 reply; 3+ messages in thread
From: Wengang Wang @ 2010-04-17 14:59 UTC (permalink / raw)
To: xfs
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
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: different log info for mkfs.xfs and xfs_growfs
2010-04-17 14:59 different log info for mkfs.xfs and xfs_growfs Wengang Wang
@ 2010-04-18 3:13 ` Eric Sandeen
2010-04-19 3:45 ` Wengang Wang
0 siblings, 1 reply; 3+ messages in thread
From: Eric Sandeen @ 2010-04-18 3:13 UTC (permalink / raw)
To: Wengang Wang; +Cc: xfs
Wengang Wang wrote:
> 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.
The devicename isn't stored in the superblock, so growfs can't get it via
the XFS_IOC_FSGEOMETRY ioctl.
> Why there is such a difference? And how get to know the log device name after it
> is mounted?
/etc/mtab? :)
The UUID of the filesystem can be found in the log device after mkfs, but
xfs is also perfectly happy with a completely zeroed-out log device (after
a clean unmount).
> 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
I think I saw this once but it went away; does a make realclean
fix it up for you - or was this a pristine git tree?
-Eric
> regards,
> wengang.
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: different log info for mkfs.xfs and xfs_growfs
2010-04-18 3:13 ` Eric Sandeen
@ 2010-04-19 3:45 ` Wengang Wang
0 siblings, 0 replies; 3+ messages in thread
From: Wengang Wang @ 2010-04-19 3:45 UTC (permalink / raw)
To: Eric Sandeen; +Cc: xfs, Wengang Wang
On 10-04-17 22:13, Eric Sandeen wrote:
> Wengang Wang wrote:
> > 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.
>
> The devicename isn't stored in the superblock, so growfs can't get it via
> the XFS_IOC_FSGEOMETRY ioctl.
>
> > Why there is such a difference? And how get to know the log device name after it
> > is mounted?
>
> /etc/mtab? :)
>
> The UUID of the filesystem can be found in the log device after mkfs, but
> xfs is also perfectly happy with a completely zeroed-out log device (after
> a clean unmount).
Ok. I got.
> > 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
>
> I think I saw this once but it went away; does a make realclean
> fix it up for you - or was this a pristine git tree?
Yes, realclean works.
Thanks for the explanations!
regards,
wengang.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-04-19 3:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-17 14:59 different log info for mkfs.xfs and xfs_growfs Wengang Wang
2010-04-18 3:13 ` Eric Sandeen
2010-04-19 3:45 ` Wengang Wang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox