<font size=2 face="sans-serif">I just noticed that tsdbfs shows you how
much data fits in the inode, even if you don't fill it... So a few commands
will give you the answer:</font><br><font size=2 face="sans-serif">dd, sync, ls, tsdbfs, inode </font><br><br><font size=2 face="sans-serif">Encryption uses EAs, so you lose some
space in inode to that.</font><br><font size=2 face="sans-serif">I don't have an encrypted FS handy for
testing, if you have one, go ahead and use tsdbfs to look at an inode and
see whether or not</font><br><font size=2 face="sans-serif">encryption pushes the data out of the
inode, I wouldn't be surprised either way.</font><br><br><font size=2 face="sans-serif">[root@n2 isizes]# dd if=/dev/urandom
bs=1 count=100 of=i100</font><br><font size=2 face="sans-serif">100+0 records in</font><br><font size=2 face="sans-serif">100+0 records out</font><br><font size=2 face="sans-serif">100 bytes (100 B) copied, 0.00226643
s, 44.1 kB/s</font><br><font size=2 face="sans-serif">[root@n2 isizes]# sync</font><br><br><font size=2 face="sans-serif">[root@n2 isizes]# ls -ild i100</font><br><font size=2 face="sans-serif">16346894 -rw-r--r-- 1 root root 100
Oct 3 09:14 i100</font><br><font size=2 face="sans-serif">[root@n2 isizes]# tsdbfs mak</font><br><font size=2 face="sans-serif">Enter command or null to read next sector.
Type ? for help.</font><br><font size=2 face="sans-serif">inode 16346894</font><br><font size=2 face="sans-serif">Inode 16346894 [16346894] snap 0 (index
14 in block 255420):</font><br><font size=2 face="sans-serif"> Inode address: 6:123049072 size
4096 nAddrs 330</font><br><font size=2 face="sans-serif"> indirectionLevel=INODE status=USERFILE</font><br><font size=2 face="sans-serif"> objectVersion=1 generation=0x9D45DC1
nlink=1</font><br><font size=2 face="sans-serif"> owner uid=0 gid=0 mode=0200100644:
-rw-r--r--</font><br><font size=2 face="sans-serif"> blocksize code=5 (32 subblocks)</font><br><font size=2 face="sans-serif"> lastBlockSubblocks=0</font><br><font size=2 face="sans-serif"> checksum=0x2496E008 is Valid</font><br><font size=2 face="sans-serif"> fileSize=100 nFullBlocks=0</font><br><font size=2 face="sans-serif"> ...</font><br><font size=2 face="sans-serif"> Data [3968]:</font><br><font size=2 face="sans-serif">0000000000000000: 17699B6F 5F9ACD28
70C05242 9268F44E *.i.o_..(p.RB.h.N*</font><br><font size=2 face="sans-serif">0000000000000010: 8FFCDCC1 C2ACE0EC
69C1FE2A 986B752C *........i..*.ku,*</font><br><font size=2 face="sans-serif">0000000000000020: 8E0434E6 1904B7FC
8B0C5709 2243343C *..4.......W."C4<*</font><br><font size=2 face="sans-serif">0000000000000030: BD317374 FB5C322D
8E257B69 FF573283 *.1st.\2-.%{i.W2.*</font><br><font size=2 face="sans-serif">0000000000000040: 515B333B EDFAE930
9B6F8712 0814BF65 *Q[3;...0.o.....e*</font><br><font size=2 face="sans-serif">0000000000000050: DBDCC25E 87EB2C16
77AE672D 45FB6BE3 *...^..,.w.g-E.k.*</font><br><font size=2 face="sans-serif">0000000000000060: 65D52D17 00000000
00000000 00000000 *e.-.............*</font><br><font size=2 face="sans-serif">0000000000000070: 00000000 00000000
00000000 00000000 *................*</font><br><font size=2 face="sans-serif"> ...</font><br><font size=2 face="sans-serif"> trailer: is NULL</font><br><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Simon Thompson
(Research Computing - IT Services)" <S.J.Thompson@bham.ac.uk></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug main discussion
list <gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/03/2016 12:10 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [gpfsug-discuss]
Biggest file that will fit inside an inode?</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><tt><font size=2><br>TCT doesn't use dmapi though I thought?<br>________________________________________<br>From: gpfsug-discuss-bounces@spectrumscale.org [gpfsug-discuss-bounces@spectrumscale.org]
on behalf of Luke Raimbach [luke.raimbach@googlemail.com]<br>Sent: 03 October 2016 17:07<br>To: gpfsug main discussion list<br>Subject: Re: [gpfsug-discuss] Biggest file that will fit inside an inode?<br><br>Surely it wouldn't go? Maybe the data would get copied out rather than
stubbed... DMAPI can't be stupid enough to stub data out of an inode? Can
it? Interesting question.<br><br>Maybe I'll test that one.<br><br>On Mon, 3 Oct 2016 at 17:00 Simon Thompson (Research Computing - IT Services)
<S.J.Thompson@bham.ac.uk<</font></tt><a href=mailto:S.J.Thompson@bham.ac.uk><tt><font size=2>mailto:S.J.Thompson@bham.ac.uk</font></tt></a><tt><font size=2>>>
wrote:<br><br>Would you tier an in-inode file to the cloud?<br><br>I mean, I wouldn't tier an in-inode file out to tape?<br><br>Simon<br>________________________________________<br>From: gpfsug-discuss-bounces@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><tt><font size=2>mailto:gpfsug-discuss-bounces@spectrumscale.org</font></tt></a><tt><font size=2>>
[gpfsug-discuss-bounces@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><tt><font size=2>mailto:gpfsug-discuss-bounces@spectrumscale.org</font></tt></a><tt><font size=2>>]
on behalf of Oesterlin, Robert [Robert.Oesterlin@nuance.com<</font></tt><a href=mailto:Robert.Oesterlin@nuance.com><tt><font size=2>mailto:Robert.Oesterlin@nuance.com</font></tt></a><tt><font size=2>>]<br>Sent: 03 October 2016 16:56<br>To: gpfsug main discussion list<br>Subject: Re: [gpfsug-discuss] Biggest file that will fit inside an inode?<br><br>What's going be taken away if you use Encryption or Transparent Cloud Tiering?<br><br><br>Bob Oesterlin<br>Sr Storage Engineer, Nuance HPC Grid<br><br><br>From: <gpfsug-discuss-bounces@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><tt><font size=2>mailto:gpfsug-discuss-bounces@spectrumscale.org</font></tt></a><tt><font size=2>>>
on behalf of Marc A Kaplan <makaplan@us.ibm.com<</font></tt><a href=mailto:makaplan@us.ibm.com><tt><font size=2>mailto:makaplan@us.ibm.com</font></tt></a><tt><font size=2>>><br>Reply-To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss@spectrumscale.org"><tt><font size=2>mailto:gpfsug-discuss@spectrumscale.org</font></tt></a><tt><font size=2>>><br>Date: Monday, October 3, 2016 at 10:46 AM<br>To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<</font></tt><a href="mailto:gpfsug-discuss@spectrumscale.org"><tt><font size=2>mailto:gpfsug-discuss@spectrumscale.org</font></tt></a><tt><font size=2>>><br>Subject: [EXTERNAL] Re: [gpfsug-discuss] Biggest file that will fit inside
an inode? 3968!!<br><br>On a non-SELINUX system the answer is 3968 of data in a 4K inode, just
128 bytes of metadata.<br><br>Caution: it's possible in some future release, this could change ... I
don't know of any plans, I'm just saying ...<br><br>Inode 16346892 [16346892] snap 0 (index 12 in block 255420):<br> Inode address: 6:123049056 size 4096 nAddrs 330<br> indirectionLevel=INODE status=USERFILE<br> objectVersion=1 generation=0xC0156CB nlink=1<br> owner uid=0 gid=0 mode=0200100644: -rw-r--r--<br> blocksize code=5 (32 subblocks)<br> lastBlockSubblocks=0<br> checksum=0xAD8E0B4B is Valid<br> fileSize=3968 nFullBlocks=0<br> currentMetadataReplicas=1 maxMetadataReplicas=2<br> currentDataReplicas=1 maxDataReplicas=2<br> ...<br> Data [3968]:<br>0000000000000000: BCA91252 2B64BEDC A7D7BA9D D5BE8C30 *...R+d.........0*<br>...<br>0000000000000F70: DA925E2F 16A68C01 03CA5E37 08D72B7F *..^/......^7..+.*<br> trailer: is NULL<br><br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<</font></tt><a href=http://spectrumscale.org/><tt><font size=2>http://spectrumscale.org</font></tt></a><tt><font size=2>><br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br><br></font></tt><br><BR>