From: David Woodhouse <dwmw2@infradead.org>
To: Patrick Allaire <pallaire@gameloft.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: How to Sync properly ?
Date: Mon, 07 Jan 2002 13:59:20 +0000 [thread overview]
Message-ID: <20732.1010411960@redhat.com> (raw)
In-Reply-To: <9A1957CB9FC45A4FA6F35961093ABB84064B08A0@srvmail-mtl.montreal.ubisoft.org>
pallaire@gameloft.com said:
> If I want to move a file from a ram drive to the flash, I will issue
> a 'mv' command followed by a 'sync' command. Sometime it will be
> updated but sometime it wont !!! 'sync' should not return until the
> flash is updated ? no ?
> To see what was happening I added some printk in the driver, in the
> delete and write ! I saw some stranges behaviour. After a 'mv',
> sometimes the sync command does not do any things, sometime I see
> somes delteting and writing of buffers but not all of the blocks ...
> the remaining block will be written to the flash in a delay from 1 to
> 5 mintutes later ... and sometime the sync work fine !!!
What file system? If you're using a 'normal' filesystem on the mtdblock
device, you shouldn't expect it to be reliable.
Linux stupidly just assumes that block devices never do any write caching,
and a sync request is therefore never passed to the block device driver.
--
dwmw2
next prev parent reply other threads:[~2002-01-07 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 13:47 How to Sync properly ? Patrick Allaire
2002-01-07 13:59 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 14:08 Patrick Allaire
2002-01-07 14:34 ` David Woodhouse
2002-01-07 18:29 Patrick Allaire
2002-01-08 9:08 ` David Woodhouse
2002-01-08 13:48 Patrick Allaire
2002-01-08 13:54 ` David Woodhouse
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=20732.1010411960@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pallaire@gameloft.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.