From: Eric Sandeen <sandeen@sandeen.net>
To: calembour <mrcekets@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: write back cache and barriers
Date: Sat, 29 Jul 2006 22:52:58 -0500 [thread overview]
Message-ID: <44CC2D1A.3060805@sandeen.net> (raw)
In-Reply-To: <5545990.post@talk.nabble.com>
calembour wrote:
> 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 ?
lots of this is in the faq:
http://oss.sgi.com/projects/xfs/faq.html#wcache
> (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) ?
I'd guess that if there's a write cache anywhere under your device, then in
effect the raid device would be considered write-cached.
> (3) how should I do to enable/disable the write cache on the raid device ?
see faq
> 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 ??
I don't see ext3 or reiser actually checking whether the underlying device
supports barriers. xfs does, in xfs_mountfs_check_barriers().
> (4) is there a way to know if the raid device supports barrier or not ?
I'm not sure how barriers interact with multiple devices; perhaps someone else
can answer....
> (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 ?
Dunno :)
-Eric
> Thanks for reading the message
> Marco
next prev parent reply other threads:[~2006-07-30 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 19:45 write back cache and barriers calembour
2006-07-30 3:52 ` Eric Sandeen [this message]
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=44CC2D1A.3060805@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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 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.