| To: | Klaus Strebel <klaus.strebel@xxxxxxxxxx> |
|---|---|
| Subject: | Re: different behaviour between XFS and ext3 |
| From: | Blair Barnett <bbarnett@xxxxxxxxxx> |
| Date: | Thu, 31 Jul 2003 06:35:28 -0700 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| Organization: | Monta Vista Software, Inc |
| References: | <3F283E36.778CC934@mvista.com> <3F28CE63.80005@eigner.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Hi Klaus
Thanks for the pointer. I'm probably just naive, but I thought a sync
call forced the data to secondary storage. Maybe sync doesn't guaruntee
that:
NAME
sync - flush filesystem buffers
SYNOPSIS
sync [OPTION]
DESCRIPTION
Force changed blocks to disk, update the super block.
--help display this help and exit
--version
output version information and exit
Looks like the manual is wrong in the case of sync and XFS. :-)
I would assume that sync overrides the mount options, but again I could
be mistaken.
Thanks for the reply.
-blair
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Performance drop in Linux 2.4.19-XFS 1.2 ?, Seth Mos |
|---|---|
| Next by Date: | Re: different behaviour between XFS and ext3, Blair Barnett |
| Previous by Thread: | Re: different behaviour between XFS and ext3, Olaf Frączyk |
| Next by Thread: | Re: different behaviour between XFS and ext3, Simon Matter |
| Indexes: | [Date] [Thread] [Top] [All Lists] |