All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Brown" <davidb@qualcomm.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Snapshots and mmaped files.
Date: Tue, 19 Apr 2005 10:08:27 -0700	[thread overview]
Message-ID: <opsphokdjknas5wc@a64.davidb.org> (raw)

I'm using lvm2 snapshots to do backups of several machines.  (lvm2  
2.00.33, device-mapper 1.01.00,
ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.9/2.6.9-udm1.tar.bz2  
minus patch 13)  (I've tried some newer patches, without success, but  
that'll be a separate mail).

The problem shows up with files that contains Berkeley databases.  These  
files seem to be modified on both the original and the snapshot.  They  
show up in my 'var' partition with imapd, and exim, and anything else that  
has a berkeley database opened, and modifies the file after the snapshot  
is taken.

The mtime of the file is not modified, only the contents.  I suspect that  
if one side grew, then the size change would not be affected.

Thanks,
David Brown

             reply	other threads:[~2005-04-19 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 17:08 David Brown [this message]
2005-04-20 21:36 ` [linux-lvm] Snapshots and mmaped files Dan Stromberg
2005-04-21  4:06   ` David Brown

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=opsphokdjknas5wc@a64.davidb.org \
    --to=davidb@qualcomm.com \
    --cc=linux-lvm@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.