From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] dirty blocks in cwfs
Date: Sun, 10 Mar 2013 00:14:49 +0100 [thread overview]
Message-ID: <7bab0d6b4131bd4f501b012f531b6426@rei2.9hal> (raw)
In-Reply-To: <65D43A00-7F64-461A-B021-1B912C63AE4E@ar.aichi-u.ac.jp>
this is correct. in general, the filesystem repairing aside, dump
will always just visit blocks that are referenced in the filesystem.
for example, if you have 0 dirty blocks and then temporarily create
100MB file and then delete it *before* it is dumped. then you got
100MB of dirty blocks in the cache. these blocks will not be cleaned
out by dump as the blocks are not referneced in the filesystem. these
blocks belong to no files but are chained in the free list. these
blocks are not lost. they will be used when allocating storage for
files. if these files get dumped, the dirty pool shrinks.
--
cinap
next prev parent reply other threads:[~2013-03-09 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 6:02 arisawa
2013-03-05 6:22 ` erik quanstrom
2013-03-05 8:55 ` arisawa
2013-03-05 14:01 ` arisawa
2013-03-05 14:04 ` erik quanstrom
2013-03-06 12:48 ` arisawa
2013-03-09 23:14 ` cinap_lenrek [this message]
2013-03-10 1:34 ` erik quanstrom
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=7bab0d6b4131bd4f501b012f531b6426@rei2.9hal \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).