From: ebiederm@xmission.com (Eric W. Biederman)
To: Byron Stanoszek <gandalf@winds.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Strange /dev/loop behavior
Date: 15 Sep 2001 13:10:24 -0600 [thread overview]
Message-ID: <m13d5otgm7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0109141505530.29038-100000@winds.org>
In-Reply-To: <Pine.LNX.4.33.0109141505530.29038-100000@winds.org>
Byron Stanoszek <gandalf@winds.org> writes:
> Is there any known method of copying/compressing the loopback-mounted file-
> system that always guarantees consistency after a sync, without requiring the
> fs to be unmounted first?
Mounting read-only and then syncing might do it. Going directly to
the block device on 2.4.x is not supported when the filesystem is
mounted. This is because the page cache is not coherent with the
block cache, and there are now plans to make this the case. In
general this won't work anyway because some other program might
be modifying your fs while you read the block device.
Eric
prev parent reply other threads:[~2001-09-15 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 19:14 Strange /dev/loop behavior Byron Stanoszek
2001-09-14 19:21 ` Ignacio Vazquez-Abrams
2001-09-15 10:57 ` Pavel Machek
2001-09-15 21:39 ` Ignacio Vazquez-Abrams
2001-09-15 19:10 ` Eric W. Biederman [this message]
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=m13d5otgm7.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=gandalf@winds.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).