From: "Dolev Raviv" <draviv@codeaurora.org>
To: <linux-mtd@lists.infradead.org>, <linux-ext4@vger.kernel.org>
Cc: "Tanya Brokhman" <tlinder@codeaurora.org>
Subject: planning general storage capacity for y fs
Date: Sun, 26 Apr 2015 14:14:53 +0300 [thread overview]
Message-ID: <006901d08012$3a1f97a0$ae5ec6e0$@codeaurora.org> (raw)
Hi,
I'm looking for guidelines for planning storage capacity. I understand it
strongly depended on the usage type.
I want to know at what point storage fullness is effecting performance in a
standard read/write partition. Do different File Systems (UBIFS/EXT4) have
different full-free ratio?
What about read only fs? Can I plan less free space in such cases?
I'll appreciate any input on this, for UBIFS specific and fs in general.
Thanks,
Dolev
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
next reply other threads:[~2015-04-26 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 11:14 Dolev Raviv [this message]
2015-04-26 20:45 ` planning general storage capacity for y fs Richard Weinberger
2015-04-26 20:45 ` Richard Weinberger
2015-04-27 7:55 ` Dolev Raviv
2015-04-27 7:55 ` Dolev Raviv
2015-04-27 8:06 ` Richard Weinberger
2015-04-27 8:06 ` Richard Weinberger
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='006901d08012$3a1f97a0$ae5ec6e0$@codeaurora.org' \
--to=draviv@codeaurora.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tlinder@codeaurora.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.