From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NHTfU-0003N9-0d for garchives@archives.gentoo.org; Mon, 07 Dec 2009 02:49:48 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 22264E059A; Mon, 7 Dec 2009 02:48:35 +0000 (UTC) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by pigeon.gentoo.org (Postfix) with ESMTP id 0A769E059A for ; Mon, 7 Dec 2009 02:48:35 +0000 (UTC) Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id D2739C501D for ; Sun, 6 Dec 2009 21:48:34 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 06 Dec 2009 21:48:34 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:content-transfer-encoding; s=smtpout; bh=s5iFGaI3PqE7F/x97a7f3JjjmG4=; b=pLwq7WU67g27HV/UR1BPQxp1vM4vAA3JS/WBex6XrGRZBuSgMHuJ/6ZF+Gyf/Vbt/irqOCOAu68LxHhEismVaeIRLu6dyNM4SYgzPbE2OYHpxXnGty1bXuJrJ83rXM7vi9anLCJlcUhNcewDf/bUxMs8a/yPDwOpdxiPlb0fWfA= X-Sasl-enc: tmzph//vaBrqX3LDpRYWX9cFirn9ZVbyWewBeIHuuDEK 1260154114 Received: from [192.168.31.12] (cpe-069-134-183-088.nc.res.rr.com [69.134.183.88]) by www.fastmail.fm (Postfix) with ESMTPSA id 8A7EE1F57A for ; Sun, 6 Dec 2009 21:48:34 -0500 (EST) Subject: Re: [gentoo-user] Using losetup & loopback devices / filesystems - changes aren't written to disk?!?!? From: Albert Hopkins To: gentoo-user@lists.gentoo.org In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Sun, 06 Dec 2009 21:48:32 -0500 Message-ID: <1260154112.8295.5.camel@centar> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 7a5ac351-ec86-40bf-9320-2e95eb6df791 X-Archives-Hash: 4011d13cebdd1f36d44a96000d916c8d I tried repeating your experiment, sans NFS and NTFS, and while I did note that the modification timestamp on the file did not change, the contents of the file did (i.e. the filesystem changed). FWIW this is Debian bug #459703 (Google told me that). What I'm going to guess is happening in your instance is the NFS server is caching parts of the file, and it checks the timestamp to see if the cache is dirty. Since it doesn't see that file file is modified it assumes its cache isn't dirty and continues to use it. You could possibly get away with it by simply # touch individual.files.img Maybe, maybe not. Also, usually you don't need to use losetup unless you are using encryption or offsets or something else exotic. Usually # mount -o loop my.img /mnt/pt Will do the trick.