linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larkin Lowrey <llowrey@nuclearwinter.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: Re: Q wrt LVM snapshot of ext4 w/ external journal
Date: Tue, 13 Apr 2010 16:06:41 -0500	[thread overview]
Message-ID: <4BC4DCE1.3050600@nuclearwinter.com> (raw)
In-Reply-To: <20100413192257.GP1849@thunk.org>

On 4/13/2010 2:22 PM, tytso@mit.edu wrote:
> It's safe to mount the LVM2 snapshot only if you use the mount option
> noload.  This will prevent it from using the journal, which is good,
> since the journal is in use by the original file system.  :-)
>
>   
I was able to verify that mounting with noload worked as advertised.
Thank you. The exact message was "mounted filesystem without journal".
> Hopefully, mounting the snapshot without using noload _should_ fail,
> since the journal is already in use, but I'm not sure we have that
> check in place, so I don't recommend trying it on a production file
> system.
I also verified that mounting w/o noload causes the mount operation to
fail. The message was "failed to claim external journal device".

When I unmounted the original fs so that the journal device was not in
use and then tried to mount the snapshot w/o noload, the mounted
snapshot was able to claim the journal. Of course I would never do that
on purpose but I wanted to see what would happen. I believe this falls
under the "don't do that or bad things will happen" category.

Thank you very much for your response to my query.

--Larkin

      reply	other threads:[~2010-04-13 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 18:22 Q wrt LVM snapshot of ext4 w/ external journal Larkin Lowrey
2010-04-13 19:22 ` tytso
2010-04-13 21:06   ` Larkin Lowrey [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=4BC4DCE1.3050600@nuclearwinter.com \
    --to=llowrey@nuclearwinter.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).