xfs
[Top] [All Lists]

Re: xfs FAQ update for write cache

To: linux-xfs@xxxxxxxxxxx
Subject: Re: xfs FAQ update for write cache
From: Martin Steigerwald <Martin@xxxxxxxxxxxx>
Date: Thu, 20 Jul 2006 09:55:35 +0200
In-reply-to: <200607200602.k6K62Lsp32974694@xxxxxxxxxxxxxxxxxxxxxxx>
References: <200607200602.k6K62Lsp32974694@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.9.3
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


<Prev in Thread] Current Thread [Next in Thread>