From: Evgeniy Ivanov <lolkaantimat@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: few ext2/ext3 questions (i_blocks usage and updating superblock in r-only)
Date: Tue, 9 Mar 2010 18:27:27 +0300 [thread overview]
Message-ID: <e1e08eb01003090727p15eb7046nbce991899b0abc30@mail.gmail.com> (raw)
In-Reply-To: <e1e08eb01003090721q306a7bday7b47bca9bae691e@mail.gmail.com>
Hello,
What is correct way to treat i_blocks? i_blocks is a block counter,
but its values differ from real number of used blocks (e.g. 1 block is
used and written to i_block, but i_blocks is set to 8 and if I set
i_blocks to 1 e2fsck always wants to set it to 8). As I understand
preallocation shouldn't affect i_blocks and there are no unix holes.
Nothing on fs should be updated, when it's mounted in r-only (I mean
mount time, mount point attributes of superblock), right?
Btw, when I don't have problems with i_blocks, e2fsck's exit status is
1 (my ext2 implementation is guilty), but it doesn't say what was
wrong even with "-v". How can I get more verbose results?
Thanks in advance for any help.
--
Evgeniy Ivanov
next parent reply other threads:[~2010-03-09 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e1e08eb01003090721q306a7bday7b47bca9bae691e@mail.gmail.com>
2010-03-09 15:27 ` Evgeniy Ivanov [this message]
2010-03-09 16:46 ` few ext2/ext3 questions (i_blocks usage and updating superblock in r-only) tytso
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=e1e08eb01003090727p15eb7046nbce991899b0abc30@mail.gmail.com \
--to=lolkaantimat@gmail.com \
--cc=linux-fsdevel@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 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).