From: calembour <mrcekets@gmail.com>
To: xfs@oss.sgi.com
Subject: write back cache and barriers
Date: Fri, 28 Jul 2006 12:45:06 -0700 (PDT) [thread overview]
Message-ID: <5545990.post@talk.nabble.com> (raw)
Hi,
I don't have a deep knowledge about filesystems and I've few experiences
with
raid configuration, so I need someone who can answer some questions about
write back cache and barriers.
I have two sata hd (sda, sdb) configured in bios-raid 0 and relative device
created by dmraid on boot (nvidia_ihfaaicb).
(1) what should I do to know if the write back cache is enabled or not ?
(2) if the write cache is enabled on both sda and sdb this mean that is
enabled
also on the raid device (/dev/mapper/nvidia_ihfaaicb) ?
(3) how should I do to enable/disable the write cache on the raid device ?
If I try mounting a xfs filesystem I get a message like "barriers are not
supported by this device" but if I mount a ext3 or a reiserfs filesystem
respectively with options barrier=1 and barrier=flush they don't complain.
If I mount the reiserfs I explicity get a message like "using barriers".
So who tells the truth ??
(4) is there a way to know if the raid device supports barrier or not ?
(5) is there a (not dangerous) test I can do to figure out if barriers are
really enabled and used with ext3 and reiserfs filesystems ?
Thanks for reading the message
Marco
--
View this message in context: http://www.nabble.com/write-back-cache-and-barriers-tf2017234.html#a5545990
Sent from the Xfs - General forum at Nabble.com.
next reply other threads:[~2006-07-28 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 19:45 calembour [this message]
2006-07-30 3:52 ` write back cache and barriers Eric Sandeen
2006-08-01 11:30 ` calembour
2006-08-06 9:00 ` Martin Steigerwald
2006-08-07 2:31 ` Eric Sandeen
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=5545990.post@talk.nabble.com \
--to=mrcekets@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