From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6107 invoked by alias); 12 Jun 2006 16:01:17 -0000 Received: (qmail 6098 invoked by uid 22791); 12 Jun 2006 16:01:16 -0000 X-Spam-Check-By: sourceware.org Received: from anchor-post-32.mail.demon.net (HELO anchor-post-32.mail.demon.net) (194.217.242.90) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 12 Jun 2006 16:01:09 +0000 Received: from prestige-adsl.demon.co.uk ([80.176.150.34] helo=feathers) by anchor-post-32.mail.demon.net with esmtp (Exim 4.42) id 1Fpoqf-0007Mb-88 for ecos-discuss@ecos.sourceware.org; Mon, 12 Jun 2006 16:01:05 +0000 Received: from 192.168.0.146 by feathers ([192.168.0.250] running VPOP3) with SMTP for ; Mon, 12 Jun 2006 16:57:44 +0100 Reply-To: From: "Ian Rothwell" To: Date: Mon, 12 Jun 2006 16:01:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-Server: VPOP3 V1.5.0g - Registered Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Correct approach with FAT16 FS & pluggable media? X-SW-Source: 2006-06/txt/msg00109.txt.bz2 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