From: Ignacio Vazquez-Abrams <ignacio@openservices.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Strange /dev/loop behavior
Date: Fri, 14 Sep 2001 15:21:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0109141519490.5549-100000@terbidium.openservices.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0109141505530.29038-100000@winds.org>
On Fri, 14 Sep 2001, Byron Stanoszek wrote:
> 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?
Try mounting the loop device synchronously (mount ... -o sync).
--
Ignacio Vazquez-Abrams <ignacio@openservices.net>
next prev parent reply other threads:[~2001-09-14 19:21 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 [this message]
2001-09-15 10:57 ` Pavel Machek
2001-09-15 21:39 ` Ignacio Vazquez-Abrams
2001-09-15 19:10 ` Eric W. Biederman
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=Pine.LNX.4.33.0109141519490.5549-100000@terbidium.openservices.net \
--to=ignacio@openservices.net \
--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).