[Top] [All Lists]

Re: Initial mount with inode32 option

To: xfs@xxxxxxxxxxx
Subject: Re: Initial mount with inode32 option
From: Arkadiusz MiÅkiewicz <arekm@xxxxxxxx>
Date: Thu, 24 Jan 2013 09:59:59 +0100
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maven.pl; s=maven; h=x-received:from:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=k+LeYGh9L20m9Ek+H/WMmzJ86I+/L4Fx6MOWHDtPXw4=; b=q84fkf7M1EclFhL1v5l8Tgb64o1euFfkuVDu9zjNgEQJzeq7LQdtuXziaXQFSWkPkN GyBbu3e/OLbYuiy8F3i5Azln/7+hoW5BuBHqDNlvVndnRbUB4dyUmeHpWObZhUbbIJBb mAqIDb8vaxaaS9GIrwDfaPb0uT9Y0DorgrEyE=
In-reply-to: <20130124001400.GW2498@dastard>
References: <51006D3E.6080704@xxxxxx> <20130123232244.GZ27055@xxxxxxx> <20130124001400.GW2498@dastard>
User-agent: KMail/1.13.7 (Linux/3.7.4; KDE/4.9.5; x86_64; ; )
On Thursday 24 of January 2013, Dave Chinner wrote:

> which, as you can see, mounts as inode32 just fine. Let's make that
> a 500g filesystem on the same device:
> $ sudo mkfs.xfs -f -l size=131072b,sunit=8 -d size=500g /dev/vdc
> meta-data=/dev/vdc               isize=256    agcount=4, agsize=32768000
> blks =                       sectsz=512   attr=2, projid32bit=0 data     =
>                       bsize=4096   blocks=131072000, imaxpct=25 =         
>              sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0
> log      =internal log           bsize=4096   blocks=131072, version=2
>          =                       sectsz=512   sunit=1 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> $ sudo mount -o inode32 /dev/vdc /mnt/scratch
> $ grep /mnt/scratch /proc/mounts
> /dev/vdc /mnt/scratch xfs rw,relatime,attr2,inode64,noquota 0 0
> $
> It reports inode64 just like it should - inode32 was ignored because
> the filesystem is not large enough to create 64 bit inodes, and so
> is using the inode64 allocation behaviour. It's been like this for
> 15 years... ;)

"Will switch" as in when I mount 500GB fs with inode32 option (/proc/mounts 
shows inode64 as in above example), then I do grow lvm under and do 
xfs_growfs. Will it magically start reporting inode32 (and using inode32 
allocator) then?

> Cheers,
> Dave.

Arkadiusz MiÅkiewicz, arekm / maven.pl

<Prev in Thread] Current Thread [Next in Thread>