From: "Lukáš Czerner" <lczerner@redhat.com>
To: Azat Khuzhin <a3at.mail@gmail.com>
Cc: Younger Liu <younger.liucn@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Why does not freeblocks number change after deleting a big file?
Date: Tue, 6 May 2014 12:35:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1405061229410.2255@localhost.localdomain> (raw)
In-Reply-To: <20140506095748.GD23108@azat>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2308 bytes --]
On Tue, 6 May 2014, Azat Khuzhin wrote:
> Date: Tue, 6 May 2014 13:57:48 +0400
> From: Azat Khuzhin <a3at.mail@gmail.com>
> To: Younger Liu <younger.liucn@gmail.com>
> Cc: linux-ext4@vger.kernel.org
> Subject: Re: Why does not freeblocks number change after deleting a big file?
>
> On Tue, May 06, 2014 at 11:32:12AM +0800, Younger Liu wrote:
> > 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
>
> Hi,
>
> Seems that you are trying to do this on a mounted partition, and the
> super block are not dumped to disk after every write/flush.
>
> You could use statfs(2) instead of debugfs/stats command, or "mount -o
> remount /dev/sdb_X_" and after debugfs, this _must_ work only in case
> you don't have journal.
>
> For more information you could look into ext4_commit_super().
Yes, it really looks like you're doing this on mounted file system.
However we do not update the superblock for some of the summary
statistics such as number of free blocks, inodes and so on.
This is because it is recalculated from per block group
descriptors when the file system is mounted, or unmounted. So when
the file system is mounted debugfs is not going to give you an
accurate information. You have to use something else like 'stat -f'
for example.
Thanks!
-Lukas
>
> > ...
> >
> > 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
>
>
prev parent reply other threads:[~2014-05-06 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 3:32 Why does not freeblocks number change after deleting a big file? Younger Liu
2014-05-06 9:57 ` Azat Khuzhin
2014-05-06 10:35 ` Lukáš Czerner [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=alpine.LFD.2.00.1405061229410.2255@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=a3at.mail@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=younger.liucn@gmail.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