Linux LVM users
 help / color / mirror / Atom feed
* [linux-lvm] Unable to mount snapshot
@ 2003-12-18 11:36 John Craig
  2003-12-19  1:19 ` more
  0 siblings, 1 reply; 5+ messages in thread
From: John Craig @ 2003-12-18 11:36 UTC (permalink / raw)
  To: linux-lvm

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: [linux-lvm] Unable to mount snapshot
@ 2003-12-18 12:08 Little, Chris
  2003-12-19  4:10 ` Heinz J . Mauelshagen
  0 siblings, 1 reply; 5+ messages in thread
From: Little, Chris @ 2003-12-18 12:08 UTC (permalink / raw)
  To: 'linux-lvm@sistina.com'

don't use snapshot.  it sucks and the owners won't answer questions about
it.

> -----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/
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] Unable to mount snapshot
  2003-12-18 11:36 [linux-lvm] Unable to mount snapshot John Craig
@ 2003-12-19  1:19 ` more
  0 siblings, 0 replies; 5+ messages in thread
From: more @ 2003-12-19  1:19 UTC (permalink / raw)
  To: linux-lvm

Hi, John,

You should use "-onouuid,ro" as parameter for mount snapshot volume.


John Craig wrote:

> 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/
>
>
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] Unable to mount snapshot
  2003-12-18 12:08 Little, Chris
@ 2003-12-19  4:10 ` Heinz J . Mauelshagen
  0 siblings, 0 replies; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2003-12-19  4:10 UTC (permalink / raw)
  To: linux-lvm

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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: [linux-lvm] Unable to mount snapshot
@ 2003-12-19  9:18 Little, Chris
  0 siblings, 0 replies; 5+ messages in thread
From: Little, Chris @ 2003-12-19  9:18 UTC (permalink / raw)
  To: 'linux-lvm@sistina.com'

http://lists.sistina.com/pipermail/linux-lvm/2003-December/015359.html
http://lists.sistina.com/pipermail/linux-lvm/2003-November/015278.html

> -----Original Message-----
> From: Heinz J . Mauelshagen [mailto:mauelshagen@sistina.com]
> Sent: Friday, December 19, 2003 4:04 AM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] Unable to mount snapshot
> 
> 
> 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> =-=-=-=-=-=-=-=-
> 
> _______________________________________________
> 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/
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2003-12-19  9:18 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-12-18 11:36 [linux-lvm] Unable to mount snapshot John Craig
2003-12-19  1:19 ` more
  -- strict thread matches above, loose matches on Subject: below --
2003-12-18 12:08 Little, Chris
2003-12-19  4:10 ` Heinz J . Mauelshagen
2003-12-19  9:18 Little, Chris

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox