From: Younger Liu <younger.liucn@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Why does not freeblocks number change after deleting a big file?
Date: Tue, 06 May 2014 11:32:12 +0800 [thread overview]
Message-ID: <536857BC.3010002@gmail.com> (raw)
Hi:
Analyze ext4 filesystem with "debugfs -R "stats" <device>",
Why does not free blocks number change after deleting a big file?
The big file:
# stat test
file："test"
size：290554084 blocks：567496 IO block：4096
before deleting the file "test":
# debugfs -R "stats" /dev/sdb
...
Inode count: 243593216
Block count: 1948728320
Reserved block count: 97436416
Free blocks: 406830314
Free inodes: 151667854
...
deleting the file "test"
# debugfs -R "stats" /dev/sdb
...
Inode count: 243593216
Block count: 1948728320
Reserved block count: 97436416
Free blocks: 406830314
Free inodes: 151667854
...
Younger
thx.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-05-06 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 3:32 Younger Liu [this message]
2014-05-06 9:57 ` Why does not freeblocks number change after deleting a big file? Azat Khuzhin
2014-05-06 10:35 ` Lukáš Czerner
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=536857BC.3010002@gmail.com \
--to=younger.liucn@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.