[gpfsug-discuss] du --apparent-size and quota

Hannappel, Juergen juergen.hannappel at desy.de
Wed Jun 2 16:26:07 BST 2021


Hi, 
mmrepquota reports without the --block-size parameter the size in units of 1KiB, so (if no ill-advised copy-paste editing confuses us) we are not talking about 400GiB but 400KiB. 
With just 863 files (from the inode part of the repquota output) and therefore 0.5KiB/file on average that could be explained by the sub-block size(although many files should vanish in the inodes). 
If it's 400GiB in 863 files with 500MiB/File the subblock overhead would not matter at all! 

> From: "IBM Spectrum Scale" <scale at us.ibm.com>
> To: "gpfsug main discussion list" <gpfsug-discuss at spectrumscale.org>
> Cc: gpfsug-discuss-bounces at spectrumscale.org, gpfsug-discuss at gpfsug.org
> Sent: Wednesday, 2 June, 2021 16:12:52
> Subject: Re: [gpfsug-discuss] du --apparent-size and quota

> Hi,
> The data and metadata replications are 2 on both source and destination
> filesystems, so from:

> $ mmrepquota -j srcfilesys | grep fileset
> srcfileset FILESET 800 800 800 0 none | 863 0 0
> 0 none

> $ mmrepquota -j dstfilesys | grep fileset
> fileset root FILESET 457 400 400 0 none | 853 0
> 0 0 none

> the quota data should be changed from 800G to 457G (or 400G to 228.5G), after
> "rsync -AHS".

> Regards, The Spectrum Scale (GPFS) team

> ------------------------------------------------------------------------------------------------------------------
> If you feel that your question can benefit other users of Spectrum Scale (GPFS),
> then please post it to the public IBM developerWroks Forum at [
> https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479
> |
> https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479
> ] .

> If your query concerns a potential software error in Spectrum Scale (GPFS) and
> you have an IBM software maintenance contract please contact 1-800-237-5511 in
> the United States or your local IBM Service Center in other countries.

> The forum is informally monitored as time permits and should not be used for
> priority messages to the Spectrum Scale (GPFS) team.

> Ulrich Sibiller ---06/02/2021 06:16:22 PM---On 6/1/21 6:08 PM, Kumaran Rajaram
> wrote: >>> If I'm not mistaken even with SS5 created filesystems,

> From: Ulrich Sibiller <u.sibiller at science-computing.de>
> To: Kumaran Rajaram <krajaram at geocomputing.net>, gpfsug main discussion list
> <gpfsug-discuss at spectrumscale.org>, "gpfsug-discuss at gpfsug.org"
> <gpfsug-discuss at gpfsug.org>
> Date: 06/02/2021 06:16 PM
> Subject: [EXTERNAL] Re: [gpfsug-discuss] du --apparent-size and quota
> Sent by: gpfsug-discuss-bounces at spectrumscale.org

> On 6/1/21 6:08 PM, Kumaran Rajaram wrote:
>>>> If I'm not mistaken even with SS5 created filesystems, 1 MiB FS block size
> >>> implies 32 kiB sub blocks (32 sub-blocks).

>> Just to add: The /srcfilesys seemed to have been created with GPFS version 4.x
> > which supports only 32 sub-blocks per block.

> > -T /srcfilesys Default mount point
> > -V 16.00 (4.2.2.0) Current file system version
> > 14.10 (4.1.0.4) Original file system version
> > --create-time Tue Feb 3 11:46:10 2015 File system creation time
> > -B 1048576 Block size
> > -f 32768 Minimum fragment (subblock) size in bytes
> > --subblocks-per-full-block 32 Number of subblocks per full block


>> The /dstfilesys was created with GPFS version 5.x which support greater than 32
>> subblocks per block. /dstfilesys does have 512 subblocks-per-full-block with
> > 8KiB subblock size since file-system blocksize is 4MiB.


> > -T /dstfilesys Default mount point
> > -V 23.00 (5.0.5.0) File system version
> > --create-time Tue May 11 16:51:27 2021 File system creation time
> > -B 4194304 Block size
> > -f 8192 Minimum fragment (subblock) size in bytes
> > --subblocks-per-full-block 512 Number of subblocks per full block


> Well, from the higher flexibility in terms of the number of subblocks I'd expect
> a lower disk usage
> instead of a higher one. Is this a wrong assumption? From 400G to 457G it's a
> ~13% increase!

>> Beside the overhead, hard-links in the source FS (which, if I'm not mistaken,
>> are not handled by "rsync" unless you specify "-H") and in some cases spare
> > files can also explain the differences.

> My rsync is using -AHS, so this should not be relevant here.

> Uli

> --
> Science + Computing AG
> Vorstandsvorsitzender/Chairman of the board of management:
> Dr. Martin Matzke
> Vorstand/Board of Management:
> Matthias Schempp, Sabine Hohenstein
> Vorsitzender des Aufsichtsrats/
> Chairman of the Supervisory Board:
> Philippe Miltin
> Aufsichtsrat/Supervisory Board:
> Martin Wibbe, Ursula Morgenstern
> Sitz/Registered Office: Tuebingen
> Registergericht/Registration Court: Stuttgart
> Registernummer/Commercial Register No.: HRB 382196
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> [ http://gpfsug.org/mailman/listinfo/gpfsug-discuss |
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss ]

> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0030.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0031.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0032.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0033.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0034.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0035.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0036.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0037.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0038.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0039.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0040.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0041.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0042.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0043.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0044.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1711 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20210602/218fbba7/attachment-0002.bin>


More information about the gpfsug-discuss mailing list