public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: Re: xfs FAQ update for write cache
Date: Thu, 20 Jul 2006 09:55:35 +0200	[thread overview]
Message-ID: <200607200955.36136.Martin@lichtvoll.de> (raw)
In-Reply-To: <200607200602.k6K62Lsp32974694@snort.melbourne.sgi.com>

Am Donnerstag 20 Juli 2006 08:02 schrieb Timothy Shimmin:
> Modid:  current:xfs-website:212892a
> faq.html - 1.88 - changed
> 	- Update info about write cache.
> 	  Mention persistent write cache, external logs,
> 	  checking it was actually enabled in xfs msgs.

Hello Thimothy,

thanks a lot... thats awesome... I have that directory corruption problem 
also mentioned in the FAQ on a workstation at work. When you have a new 
xfs_check available I can test it. (I know how to compile it under 
Knoppix 5 ;-).

A little feedback: lines are not wrapped in either Firefox or Konqueror 
(http://oss.sgi.com/projects/xfs/faq.html). This is for the complete FAQ. 
It makes reading it difficult.

It might make sense to include the log messages when barriers are disabled 
at the approbiate places of the FAQ:

root@deepdance:/usr/src/linux/fs/xfs -> grep -ir "barrier" *
linux-2.6/xfs_super.c:xfs_mountfs_check_barriers(xfs_mount_t *mp)
linux-2.6/xfs_super.c:            "Disabling barriers, not supported with 
external log device");
linux-2.6/xfs_super.c:          mp->m_flags &= ~XFS_MOUNT_BARRIER;
linux-2.6/xfs_super.c:            "Disabling barriers, not supported by 
the underlying device");
linux-2.6/xfs_super.c:          mp->m_flags &= ~XFS_MOUNT_BARRIER;
linux-2.6/xfs_super.c:  error = xfs_barrier_test(mp);
linux-2.6/xfs_super.c:            "Disabling barriers, trial barrier write 
failed");
linux-2.6/xfs_super.c:          mp->m_flags &= ~XFS_MOUNT_BARRIER;

While they are quite self-explanatory it might still help to make it 
absolutely clear what each log message mean.

Is the last one  "Disabling barriers, trial barrier write failed" issued 
when the underlying device does not support write barriers?

It would be good to know which drivers do and which don't but thats more 
of a kernel FAQ regarding write barrier support. Its probably best to 
test for oneself and use the logs ;-)

Regards,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2006-07-20  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20  6:02 xfs FAQ update for write cache Timothy Shimmin
2006-07-20  7:55 ` Martin Steigerwald [this message]
2006-07-21  6:17   ` Timothy Shimmin
2006-07-21  9:26     ` Martin Steigerwald

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=200607200955.36136.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --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