From: Eric Sandeen <sandeen@sandeen.net>
To: Iuri Diniz <iuridiniz@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Disable journaling
Date: Mon, 26 Jan 2009 19:46:01 -0600 [thread overview]
Message-ID: <497E6759.3060300@sandeen.net> (raw)
In-Reply-To: <b211fe280901261723h6dd1db69t9d24c8d6774b18bc@mail.gmail.com>
Iuri Diniz wrote:
> BACKGOUND:
> I'm looking for a filesystem for linux with these features:
>
> * Fast Sequential Read (FSR)
> * Optional: copy on write support (COW)
>
> I think that Ext4 and XFS are the best options. (ZFS too, but current ZFS
> implementation is not GPL, maybe brtfs when ready).
>
> why do I want this? because I have a SSD.FSQ will reduce the boot time and
> COW will reduce writes on the same sector while allowing snapshots
>
> I've found that XFS has a FSQ support (good job)[1], so I it will be very
> fast on SSD (random read == sequential read).
>
> FAIK xfs doesn't support COW, it's ok because ext4 doesn't too.
>
> MY PROBLEM:
>
> I know that my SSD drive supports wearing level on hardware, but anyway I
> want to reduce unnecessary writes on my device, so I want to disable
> journaling on my filesytem.
>
> Maybe, the ext4 (like ext3 does) will support it by doing this:
>
> tune2fs -O ^has_journal /dev/sda1
>
> Is possible to disable journaling on XFS too?
No, it's not right possible today. There used to be a sort of config
option that disabled journaling ages ago, but it's gone now. Not sure
it ever worked on Linux.
Ext4 does have an option to disable journaling now, which is
interesting. If I ever have any time I'd like to see how hard it might
be to allow a mount option to xfs to also make journaling a no-op.
> Thanks in advance
>
> [1] http://www.phoronix.com/scan.php?page=article&item=ext4_benchmarks&num=4
Fatally flawed article FWIW, their bonnie++ results are comically bad
(you try deleting 8G files on ext3, see if you can do 200 per second) I
alerted them to the bonnie++ problems, and explained what they had done
wrong in the results parsing, and although they link to my email, they
leave the ridiculous graphs in place. The iozone results may be better,
but I'd be very inclined to do my own testing rather than use those
results right now.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-27 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 1:23 Disable journaling Iuri Diniz
2009-01-27 1:46 ` Eric Sandeen [this message]
2009-01-27 2:02 ` Nathan Scott
2009-01-27 2:12 ` Iuri Diniz
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=497E6759.3060300@sandeen.net \
--to=sandeen@sandeen.net \
--cc=iuridiniz@gmail.com \
--cc=xfs@oss.sgi.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