From: Linda Walsh <xfs@tlinx.org>
To: ajh0418@naver.com
Cc: xfs@oss.sgi.com
Subject: Re: Hi, I'm intereted in XFS filesystem.. i have a question
Date: Sat, 13 Jul 2013 00:55:11 -0700 [thread overview]
Message-ID: <51E107DF.2000307@tlinx.org> (raw)
In-Reply-To: <fe7d2eb1da66e64a15bd37fb20a47c6e@tweb12.nm.nhnsystem.com>
안재형 wrote:
> I want to see free space blocks or none-allocation blocks. I can't find
> program in XFSprogs package.
---
You should be able to use the standard linux utils for those --
xfsprogs are only for things that are xfs specific, but "df" tells you
free space & used. The "du" command will showyou how many blocks are really
used in a block. ... etc. '
That's a benefit of the OS kernel.
If you want more technical details, you can try the xfs tool
"xfs_info with -o,ro. That shows you # blocks total.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-07-13 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 6:29 Hi, I'm intereted in XFS filesystem.. i have a question 안재형
2013-07-13 7:55 ` Linda Walsh [this message]
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=51E107DF.2000307@tlinx.org \
--to=xfs@tlinx.org \
--cc=ajh0418@naver.com \
--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