From: OGAWA Hirofumi Subject: Re: vfat vs msdos and -o flush Date: Sun, 07 Mar 2010 20:00:55 +0900 Message-ID: <871vfwiefs.fsf@devron.myhome.or.jp> References: <20100301170827.GA5142@lst.de> <877hpt1q96.fsf@devron.myhome.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: chris.mason@oracle.com, linux-fsdevel@vger.kernel.org To: Christoph Hellwig Return-path: Received: from mail.parknet.co.jp ([210.171.160.6]:59966 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751421Ab0CGLA7 (ORCPT ); Sun, 7 Mar 2010 06:00:59 -0500 In-Reply-To: <877hpt1q96.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Wed, 03 Mar 2010 22:36:21 +0900") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: OGAWA Hirofumi writes: > Christoph Hellwig writes: > >> Commit ae78bf9c4f5fde3c67e2829505f195d7347ce3e4 added a -o flush >> option to the fat driver back in 2006, which causes asynchronous >> writeout after I/O operations ASAP. This already is quite hacky >> and not something I like very much, but even worse the option >> is accepted when using the more common vfat filesysten type, but >> only actually implemented for the less common legacy msdos >> filesystem type. >> >> This tells us two lessons: >> >> - the -o flush option probably never got a whole lot of exposure >> and users didn't notice it doesn't work. We might as well just >> remove it again > > Sigh. Chris, could you handle this? It seems there is no answer, so I have no objection to drop it... Thanks. -- OGAWA Hirofumi