linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin Liao" <kevinliao@iei.com.tw>
To: "Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Writing files to remote storage
Date: Wed, 28 Aug 2002 16:17:50 +0800	[thread overview]
Message-ID: <00cf01c24e6b$678127e0$1d0d11ac@ieileb9wqxg5qq> (raw)
In-Reply-To: 20020828081412.GA1496@spunk

Dear all,

I don't know whether it's proper to post such a problem in this mailing
list,
but I guess someone here could help me...

If I mount a remote linux partition through smb or nfs and write one file to
that partition. How could I make sure that that file is really written to
the remote disk successfully? I know that some cache mechanisms existed in
linux kernel. So I guess there may be two possibilities as below:

1. After the call write() returns successfully, the file has been actually
in the local cache and then submit to remote cache later.
2. After the call write() returns successfully, the file has been actually
in the remote cache and then submit to remote disk later.

Then, no matter which one of the above two situations happens, the data is
not yet written to the physical storage at that time, right? Should I need
to call fsync() each time after calling write()? Thanks a lot!

Regards,
Kevin



  reply	other threads:[~2002-08-28  8:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 19:47 Linux v2.5.32 Linus Torvalds
2002-08-27 20:22 ` Stephane Wirtel
2002-08-27 20:36   ` Thunder from the hill
2002-08-27 20:48     ` Stephane Wirtel
2002-08-27 20:54   ` Gabor Z. Papp
2002-08-28  6:18     ` Jan-Benedict Glaw
2002-08-28  7:41       ` Edward Coffey
2002-08-28  8:35       ` Russell King
2002-08-27 20:43 ` Udo A. Steinberg
2002-08-27 20:47   ` Andre Hedrick
2002-08-27 20:47   ` Alexander Viro
2002-08-27 22:35     ` Alan Cox
2002-08-28  2:07       ` [PATCH] " Alexander Viro
2002-08-28  1:21     ` Arador
2002-08-28  2:17       ` Alexander Viro
2002-08-27 22:28 ` Chris Funderburg (at home)
2002-08-28  7:31 ` Linux v2.5.32 - some menuconfig oddities Helge Hafting
2002-08-28  7:43   ` Gabor Kerenyi
2002-08-28  8:14 ` Linux v2.5.32 Edward Coffey
2002-08-28  8:17   ` Kevin Liao [this message]
2002-08-28 14:18     ` Writing files to remote storage Alan Cox
2002-08-28 13:00 ` 2.5.32 doesn't beep? Mikael Pettersson
2002-08-28 13:05   ` Vojtech Pavlik
2002-08-28 13:12     ` Mikael Pettersson
2002-08-28 13:58     ` Gerhard Mack
2002-08-28 14:33       ` Jos Hulzink
2002-08-28 14:49       ` Vojtech Pavlik
2002-08-28 20:04     ` Mikael Pettersson
2002-08-28 20:30       ` Vojtech Pavlik
2002-08-29  8:41         ` Gerd Knorr
2002-08-28 17:21 ` Linux v2.5.32 Adrian Bunk
2002-08-31 16:54 ` Linux v2.5.32 (Config options to have a working keyboard) Axel Siebenwirth

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='00cf01c24e6b$678127e0$1d0d11ac@ieileb9wqxg5qq' \
    --to=kevinliao@iei.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).