From: "Olaf Frączyk" <olaf@cbk.poznan.pl>
To: Leon Kolchinsky <leonk@construct.haifa.ac.il>
Cc: 'Justin Piszcz' <jpiszcz@lucidpixels.com>, linux-xfs@oss.sgi.com
Subject: RE: mkfs and mount tips?
Date: Tue, 13 Feb 2007 12:14:28 +0100 [thread overview]
Message-ID: <1171365268.20354.31.camel@venus.local.navi.pl> (raw)
In-Reply-To: <20070213103533.C89F519311@mail.edu.haifa.ac.il>
On Tue, 2007-02-13 at 12:33 +0200, Leon Kolchinsky wrote:
>
> > -----Original Message-----
> > From: Justin Piszcz [mailto:jpiszcz@lucidpixels.com]
> > Sent: Tuesday, February 13, 2007 11:30 AM
> > To: Leon Kolchinsky
> > Cc: linux-xfs@oss.sgi.com
> > Subject: Re: mkfs and mount tips?
(...)
> > When I was trying out different optimizations (and what I currently use on
> > a couple volumes is):
> >
> > logbufs=8,logbsize=262144,biosize=16,noatime,nodiratime,nobarrier
> >
>
> I think that "nobarrier" option is bad, cause power failure would corrupt
> your FS in this case.
It depends on hardware. If you use SCSI with write cache turned off I
see no reason to loss data. You might use RAID with write cache (battery
powered) safely too.
I'm not sure but even (S)ATA with write cache disabled should be fine.
Regards,
Olaf
--
Olaf Frączyk <olaf@cbk.poznan.pl>
next prev parent reply other threads:[~2007-02-13 12:49 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 [this message]
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
2007-02-15 14:10 ` Leon Kolchinsky
-- strict thread matches above, loose matches on Subject: below --
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=1171365268.20354.31.camel@venus.local.navi.pl \
--to=olaf@cbk.poznan.pl \
--cc=jpiszcz@lucidpixels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox