From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Unable to mount snapshot
Date: Fri Dec 19 04:10:02 2003 [thread overview]
Message-ID: <20031219110429.D18654@sistina.com> (raw)
In-Reply-To: <9BBB7C9EFEF1874BAC4DC204E867EFAF02560DD0@s99mail06>; from Chris.Little@okdhs.org on Thu, Dec 18, 2003 at 12:06:11PM -0600
On Thu, Dec 18, 2003 at 12:06:11PM -0600, Little, Chris wrote:
> don't use snapshot. it sucks and the owners won't answer questions about
> it.
Chris,
what in particular problems do you have with snapshots ?
Regards,
Heinz -- The LVM Guy --
>
> > -----Original Message-----
> > From: John Craig [mailto:johncraig01@netscape.net]
> > Sent: Thursday, December 18, 2003 11:34 AM
> > To: linux-lvm@sistina.com
> > Subject: [linux-lvm] Unable to mount snapshot
> >
> >
> > Hi,
> >
> > I successfully created a snapshot of an active LV with XFS
> > filesystem,
> > and ldisplay shows it to be operating correctly. However,
> > when I try to
> > mount the snapshot, it says "wrong fs type, bad option, bad
> > superblock
> > on /dev/system/snap or too many mounted file systems"
> >
> > Can anyone help, or shed some light on why this is happening?
> > Is there a
> > workaround?
> >
> > The mount command was "mount -t xfs -o ro /dev/system/snap /mnt/snap"
> >
> > I am running SuSE 9.0 on x86-64, with kernel 2.4.21-149, lvm version
> > 1.0.7(mp-v6). I have a volume group running on 3 raid arrays,
> > each 0.9
> > TB, for a total of 2.7 TB. It has 2 active LVs, one of them 2 TB, and
> > the other 500GB, leaving about 249GB unallocated. I created
> > the snapshot
> > with:
> >
> > lvcreate -L 200G -s -n snap /dev/system/adsdata
> >
> > As I said, the snapshot seems to be working correctly, but
> > when I bring
> > up the LVM tool in YAST, it shows the original LV, with
> > capacity 1.9 TB,
> > mounted, and the snapshot with a capacity of 1.9TB,
> > unmounted. When I
> > try to set the mount point for the snapshot, it says the capacity is
> > wrong, it needs to be <= 249GB. In other words, it seems to
> > be treating
> > it as if it were a regular LV, not a snapshot..
> >
> > The listing of lvdisplay is:
> > --- Logical volume ---
> > LV Name /dev/system/snap
> > VG Name system
> > LV Write Access read only
> > LV snapshot status active destination for /dev/system/adsdata
> > LV Status available
> > LV # 3
> > # open 0
> > LV Size 2 TB
> > Current LE 16383
> > Allocated LE 16383
> > snapshot chunk size 64 KB
> > Allocated to snapshot 16.66% [33.29 GB/199.90 GB]
> > Allocated to COW-table 100 MB
> > Allocation next free
> > Read ahead sectors 1024
> > Block device 58:2
> >
> >
> >
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-12-19 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 12:08 [linux-lvm] Unable to mount snapshot Little, Chris
2003-12-19 4:10 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 9:18 Little, Chris
2003-12-18 11:36 John Craig
2003-12-19 1:19 ` more
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=20031219110429.D18654@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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.