Linux LVM users
 help / color / mirror / Atom feed
From: Mark Komarinski <mkomarinski@hms.harvard.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Snapshots with Debian 2.4.26
Date: Wed, 30 Jun 2004 14:00:17 -0400	[thread overview]
Message-ID: <40E2FFB1.6060301@hms.harvard.edu> (raw)

Right.  I'm off breaking all the rules here.  Here's what I have:

Debian backport of 2.4.26 (only change was adding 64G support)
Debian stable (1.0.4 it says)

I want to use snapshots for backing up oracle, but here's what I have:

cliff:~# lvcreate -l1 -s -n oracle_control_1_snap /dev/vg00/oracle_control_1
lvcreate -- INFO: using default snapshot chunk size of 64 KB for 
"/dev/vg00/oracle_control_1_snap"
lvcreate -- doing automatic backup of "vg00"
lvcreate -- logical volume "/dev/vg00/oracle_control_1_snap" 
successfully created

cliff:~# mount /dev/vg00/oracle_control_1_snap /snapshot/oracle/
mount: block device /dev/vg00/oracle_control_1_snap is write-protected, 
mounting read-only
mount: wrong fs type, bad option, bad superblock on 
/dev/vg00/oracle_control_1_snap,
        or too many mounted file systems
cliff:~#

(The size of the lv that I'm doing a snapshot of is 1 64M extent, so 
doing a 1 extent in size should be enough, yes?)

My understanding is that this is a result of the VFS patch not being 
applied.  But there doesn't seem to be a VFS patch for 2.4.26.

Any ideas?  I can provide whatever additional information you need, but 
this is really strange.

-Mark

-- 
Mark Komarinski				mkomarinski@hms.harvard.edu
Sr. Linux/UNIX System Administrator	http://wqcg.med.harvard.edu
West Quad Computing Group
Harvard Medical School

             reply	other threads:[~2004-06-30 18:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 18:00 Mark Komarinski [this message]
2004-07-01 13:23 ` [linux-lvm] Snapshots with Debian 2.4.26 Mark Komarinski
2004-07-01 14:49   ` Delian Krustev

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=40E2FFB1.6060301@hms.harvard.edu \
    --to=mkomarinski@hms.harvard.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox