public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ian Rothwell" <ian.rothwell@prestigemedical.co.uk>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Correct approach with FAT16 FS & pluggable media?
Date: Mon, 12 Jun 2006 16:01:00 -0000	[thread overview]
Message-ID: <PCBBJHAPELBIGHBMGFCMAEMGCJAA.ian.rothwell@prestigemedical.co.uk> (raw)

Hello there (Savin?),
	I'm running the FAT16 package on MMC reliably (if a little slowly...)
but after putting it off for some months I'm now unavoidably at the stage
where I need to safely hot unplug/replug the flash card. Looking at it I
guessed it'd just be a case of umounting root (having initially mounted
the FS at boot), then remounting later, but on umount fatfs.c:fat_fs_umount
is failing before getting to delete the block layer cache when
fatfs_get_live_node_count(disk) is tested. I guess this ties in with
where the code talks about the file system needing to be empty for a
successful umount, but I'm not sure how to empty it, short of closing all
open files/dirs and that's been tried. A successful flush/sync of the block
cache isn't really critical for me at the moment, more important for now is
for it to be properly scrapped on card unplug, to make way for a fresh block
lib instance when root is subsequently remounted after the card's come back
in (with its files externally edited) and been brought back online in my
device
driver.

Regards,

Ian Rothwell
Prestige Medical ltd.




-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2006-06-12 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=PCBBJHAPELBIGHBMGFCMAEMGCJAA.ian.rothwell@prestigemedical.co.uk \
    --to=ian.rothwell@prestigemedical.co.uk \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).