From: "Leon Kolchinsky" <leonk@construct.haifa.ac.il>
To: linux-xfs@oss.sgi.com
Subject: mkfs and mount tips?
Date: Tue, 13 Feb 2007 10:48:15 +0200 [thread overview]
Message-ID: <20070213085037.216BE12C53@mail.edu.haifa.ac.il> (raw)
Hello All,
I have Pentium II (Deschutes) with first 10GB (/dev/hda) and second
60GB(/dev/hdc) disk.
After reading gentoo xfs threads on their forum and some SGI docs and FAQs I
came with this options for creating FS and mounting the disks:
1) To create XFS on hda:
Code:
# mkfs.xfs -l internal,size=128m -d agcount=2 /dev/hda
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)?:
Is this how the code should look?:
# mkfs.xfs -l internal,size=128m -d agcount=2 –d unwritten=0 /dev/hda
2) To prevent data lost in case of power outage(Disabling the write back
cache):
Add the following to local.start:
Code:
# hdparm -W0 /dev/hda
# hdparm -W0 /dev/hdc
# blktool /dev/hda wcache off
# blktool /dev/hdc wcache off
Right?
3) Mount options:
On gentoo xfs thread it's suggested that the mount options should be
"noatime,logbufs=8"
But what about "osyncisdsync" mount option.
"• osyncisdsync
– Writes to files opened with the O_SYNC flag set will behave as if the
O_DSYNC flag
had been used instead.
– This can result in better performance without compromising data safety.
– However timestamp updates from O_SYNC writes can be lost if the system
crashes.
Use osyncisosync to disable this setting."
So do you think it is safe to add "osyncisdsync" mount option to fstab?
I'd appreciate any comments/tips/answers.
Best Regards,
Leon Kolchinsky
next reply other threads:[~2007-02-13 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 8:48 Leon Kolchinsky [this message]
2007-02-13 9:30 ` mkfs and mount tips? 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
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=20070213085037.216BE12C53@mail.edu.haifa.ac.il \
--to=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.