From: YeYin <eyniy@qq.com>
To: "Eric Sandeen" <sandeen@sandeen.net>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: du result is smaller than xfs_quota report
Date: Wed, 21 Oct 2015 14:37:04 +0800 [thread overview]
Message-ID: <tencent_756CDB1668EC804906FB9672@qq.com> (raw)
In-Reply-To: <0952A0E9-F360-46CE-BE7A-1B8473700F08@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 3276 bytes --]
> Is anything mounted under that directory hierarchy, and hiding files from du's view?
No, Thanks. I found some unlinked inodes, but I can't get some useful information:
# xfs_db -xr -c 'agi 1' -c p /dev/sda4
magicnum = 0x58414749
versionnum = 1
seqno = 1
length = 89150592
count = 9472
root = 3
level = 1
freecount = 1902
newino = 997952
dirino = null
unlinked[0-63] = 0:78272 1:98561 2:98562 3:78275 4:77060 5:78277 6:77062 7:78279 8:98568 9:98569 10:98570 11:77067 12:77068 13:98573 14:98574 15:78287 16:98576 17:98577 18:78290 19:98515 20:98068 21:78165 22:78294 23:78295 24:78168 25:888985 26:78170 27:98075 28:78172 29:78301 30:78302 31:98079 32:888992 33:76129 34:98082 35:76131 36:98084 37:98277 38:98278 39:910503 40:98280 41:98281 42:98282 43:98091 44:98092 45:98541 46:98094 47:98095 48:76976 49:75953 50:75954 51:98547 52:98484 53:98485 54:98550 55:98551 56:98488 57:98489 58:98106 59:98491 60:98492 61:889021 62:98558 63:98495
# xfs_db -xr -c 'inode 78272' -c p /dev/sda4
core.magic = 0
core.mode = 0
core.version = 0
core.format = 0 (dev)
core.uid = 0
core.gid = 0
core.flushiter = 0
core.atime.sec = Thu Jan 1 08:00:00 1970
core.atime.nsec = 000000000
core.mtime.sec = Thu Jan 1 08:00:00 1970
core.mtime.nsec = 000000000
core.ctime.sec = Thu Jan 1 08:00:00 1970
core.ctime.nsec = 000000000
core.size = 0
core.nblocks = 0
core.extsize = 0
core.nextents = 0
core.naextents = 0
core.forkoff = 0
core.aformat = 0 (dev)
core.dmevmask = 0
core.dmstate = 0
core.newrtbm = 0
core.prealloc = 0
core.realtime = 0
core.immutable = 0
core.append = 0
core.sync = 0
core.noatime = 0
core.nodump = 0
core.rtinherit = 0
core.projinherit = 0
core.nosymlinks = 0
core.extsz = 0
core.extszinherit = 0
core.nodefrag = 0
core.filestream = 0
core.gen = 0
next_unlinked = 0
u.dev = 0
Thanks,
Ye
------------------ Original ------------------
From: "Eric Sandeen";<sandeen@sandeen.net>;
Date: Wed, Oct 21, 2015 03:35 AM
To: "YeYin"<eyniy@qq.com>;
Cc: "xfs"<xfs@oss.sgi.com>;
Subject: Re: du result is smaller than xfs_quota report
> On Oct 20, 2015, at 4:09 AM, YeYin <eyniy@qq.com> wrote:
>
> Hi, all,
> I encountered some problems when I used XFS with project quota:
>
> # cat /etc/projid
> docker-15091421396426:65061
> docker-15092311522409:26286
> docker-15101215637294:14162
>
> # cat /etc/projects
> 65061:/data/docker-volumes/docker-15091421396426
> 26286:/data/docker-volumes/docker-15092311522409
> 14162:/data/docker-volumes/docker-15101215637294
>
> # xfs_quota -xc 'report -h' /data
> Project quota on /data (/dev/sda4)
> Blocks
> Project ID Used Soft Hard Warn/Grace
> ---------- ---------------------------------
> docker-15091421396426 1.0G 0 100G 00 [------]
> docker-15092311522409 371.5G 0 700G 00 [------]
> docker-15101215637294 920.8M 0 400G 00 [------]
>
> # du -sh /data/docker-volumes/docker-15092311522409
> 200G /data/docker-volumes/docker-15092311522409
>
> As we can see, du's result(200G) is smaller than xfs_quota report.
>
Is anything mounted under that directory hierarchy, and hiding files from du's view?
Eric
[-- Attachment #1.2: Type: text/html, Size: 4783 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-10-21 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 9:09 du result is smaller than xfs_quota report YeYin
2015-10-20 11:31 ` Emmanuel Florac
2015-10-20 13:30 ` YeYin
2015-10-20 19:35 ` Eric Sandeen
2015-10-21 6:37 ` YeYin [this message]
2015-10-21 7:13 ` Dave Chinner
2015-10-21 8:09 ` YeYin
2015-10-23 6:55 ` Dave Chinner
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=tencent_756CDB1668EC804906FB9672@qq.com \
--to=eyniy@qq.com \
--cc=sandeen@sandeen.net \
--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