From: Theodore Tso <tytso@mit.edu>
To: "Renato S. Yamane" <yamane@diamondcut.com.br>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 on SSD Intel X25-M
Date: Thu, 12 Nov 2009 10:30:17 -0500 [thread overview]
Message-ID: <20091112153017.GA32122@mit.edu> (raw)
In-Reply-To: <4AFC14D6.7080700@diamondcut.com.br>
On Thu, Nov 12, 2009 at 11:59:50AM -0200, Renato S. Yamane wrote:
> Hi,
>
> [please, leave me on cc because I'm not subscribed on this ML]
>
> I'm using Intel SSD X25-M on my laptop, and I always hear that is not a
> good idea use journal on SSD (it decrease the life time).
>
> I ask Intel about this, but I don't receive any answer.
>
> So, I would like to know if is possible disable Journal on EXT4.
It is possible to create an ext4 file system without a journal. It
would mean that unclean shutdowns would require a full fsck, which on
a freshly created file system on an SSD isn't _that_ bad. Depending
on how full/fragmented your filesystem happens to be, it will probably
be under 10 seconds.
That being said, though, it shouldn't be necessary to avoid using a
journal on the Intel SSD. Intel says that laptop will last at least 5
years with 10GB worth of writes per day, and that's a huge amount. I
have an X25-M SSD in my laptop, using an ext4 file system and with the
journal enabled, and since the file system was created 266 days ago,
when I put my X25-M into service, the drive has seen 570GB worth of
writes, so I'm averaging 2.14 GB writes per day. That's well under
the 20GB of writes/per day upon which Intel based its 5 year lifetime
(and most hard drives, and heck, most laptops generally aren't in
service for that long before they are replaced.)
I have done a few things to reduce needless disk utilization, such as
using tmpfs for /tmp and configuring firefox to place its cache in
/tmp, but the bottom line is I wouldn't really worry that much about
the journal. If you really want to run without a journal, you can use
"mke2fs -t ext4 -O ^has_journal /dev/XXX" to format an ext4 filesystem
without a journal. But there will be some distinct tradeoffs with
omitting the journal, including possibility that sometimes on an
unclean shutdown you will need to do a manual e2fsck pass.
Best regards,
- Ted
next prev parent reply other threads:[~2009-11-12 15:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 13:59 Ext4 on SSD Intel X25-M Renato S. Yamane
2009-11-12 15:11 ` Eric Sandeen
2009-11-12 15:30 ` Theodore Tso [this message]
2009-11-12 20:06 ` Renato S. Yamane
2009-11-13 11:39 ` Andi Kleen
2009-11-13 14:13 ` Theodore Tso
2009-11-13 22:03 ` Florian Weimer
2009-11-15 21:15 ` Renato S. Yamane
2009-11-15 21:18 ` Florian Weimer
2009-11-15 21:30 ` Eric Sandeen
2009-11-15 21:46 ` Renato S. Yamane
2009-11-15 22:11 ` Theodore Tso
2009-11-15 22:18 ` Renato S. Yamane
2009-11-16 18:40 ` Theodore Tso
2009-11-16 19:00 ` Renato S. Yamane
2009-11-15 22:01 ` Theodore Tso
-- strict thread matches above, loose matches on Subject: below --
2010-06-27 17:47 Nebojsa Trpkovic
2010-06-29 13:56 ` tytso
2010-06-29 14:35 ` Nebojsa Trpkovic
2010-06-29 15:12 ` Nebojsa Trpkovic
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=20091112153017.GA32122@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=yamane@diamondcut.com.br \
/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).