All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Leon Kolchinsky <leonk@construct.haifa.ac.il>, linux-xfs@oss.sgi.com
Subject: Re: mkfs and mount tips?
Date: Thu, 15 Feb 2007 12:19:16 +1100	[thread overview]
Message-ID: <5BFF2CB07B4CB49FEC7310C7@timothy-shimmins-power-mac-g5.local> (raw)
In-Reply-To: <20070213085037.216BE12C53@mail.edu.haifa.ac.il>

Hi Leon,

--On 13 February 2007 10:48:15 AM +0200 Leon Kolchinsky <leonk@construct.haifa.ac.il> wrote:

> I've also seen "–d unwritten=0" option:
>
> So my question:
> Is it safe to add –d unwritten=0 option to increase performance like this
> (or will I lose some essential functionality)?:
>

My understanding (although I'm not familiar with that code),
is that unwritten extents are used in space preallocation.
So unless you reserve space for a file it will not have an effect.
And if you do, then setting "unwritten=0" will speed up writes because it doesn't
need to flag the unwritten extents and write out the extra transactions for this.
If the unwritten extents aren't flagged as such then there can be a security issue
where one can read old data (other's data) for these unwritten parts.
In fact, the security issue on preallocation (1997-98 sgi-pv#705217) was what motivated
the idea of flagging extents as unwritten in the first place.

--Tim

  parent reply	other threads:[~2007-02-15  1:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13  8:48 mkfs and mount tips? Leon Kolchinsky
2007-02-13  9:30 ` Justin Piszcz
2007-02-13 10:33   ` Leon Kolchinsky
2007-02-13 11:14     ` Olaf Frączyk
2007-02-13 12:38       ` Leon Kolchinsky
2007-02-13 11:57     ` Andi Kleen
2007-02-13 18:10     ` Eric Sandeen
2007-02-15  1:19 ` Timothy Shimmin [this message]
2007-02-15 14:10   ` Leon Kolchinsky
2007-02-13  9:19 Leon Kolchinsky

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=5BFF2CB07B4CB49FEC7310C7@timothy-shimmins-power-mac-g5.local \
    --to=tes@sgi.com \
    --cc=leonk@construct.haifa.ac.il \
    --cc=linux-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 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.