[linux-lvm] Can't mount logical volume - super block error

[linux-lvm] Can't mount logical volume - super block error

[Sasha Z]

I had a functioning lvm using four hard discs, but found it necessary
to rebuild my operating system. Since then, while the vg and lv come
online are read available, I can't actually mount the filesystem or do
anything with it. It says it cannot read the superblock at locations 2
and 16.

does anybody have any thoughts on this?

I've tried 2.00.25 and 2.00.33.

Re: [linux-lvm] Can't mount logical volume - super block error

[Scott Serr]

Sasha Z wrote:

>I had a functioning lvm using four hard discs, but found it necessary
>to rebuild my operating system. Since then, while the vg and lv come
>online are read available, I can't actually mount the filesystem or do
>anything with it. It says it cannot read the superblock at locations 2
>and 16.
>
>does anybody have any thoughts on this?
>  
>
I'm not sure what you mean by "the vg and lv come online are read 
available..."  Have you tried:
pvscan
pvdisplay [-v]
lvdisplay [-v]

All looks good? 

Are you sure you have your file system turned on in your kernel?  How 
about explicitly mounting it with "-t"?

I probably can't help other than have you describe more for the gurus.

>I've tried 2.00.25 and 2.00.33.
>  
>
I just went from kernel 2.4.27 with lvm 2.00.25 to 2.6.10 with 2.00.33, 
it worked ok for me, just to give you a data point.

Re: [linux-lvm] Can't mount logical volume - super block error

[Brian McCullough]

[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]

On Thu, Mar 03, 2005 at 01:05:29AM -0700, Scott Serr wrote:
> Sasha Z wrote:
> 
> >I had a functioning lvm using four hard discs, but found it necessary
> >to rebuild my operating system. Since then, while the vg and lv come
> >online are read available, I can't actually mount the filesystem or do
> >anything with it. It says it cannot read the superblock at locations 2
> >and 16.
> >
> I'm not sure what you mean by "the vg and lv come online are read 
> available..."  Have you tried:
> pvscan
> pvdisplay [-v]
> lvdisplay [-v]
> 
> All looks good? 


I have a very similar problem, and discovered this message.

As recommended, I have run all three commands above, and everything
looks normal.  I will give output in a subsequent message.

Leading up to this:

Over the past week, I have been completely rebuilding this system,
replacing the main ( root ) disk drive, and installing a fresh distribution.
To this I want to add the old "data" disk drive, which has one PV, one
VG and four LVs on it. 

The data drive is a SATA drive, one of two mirrored on a single
controller, which were seen as hde and hdg in the old system.  Now,
aside from issues which appear to prevent the second channel of the
Silicon Image 3112 card from being used with "modern" kernels ( tried
2.4.27, 2.6.8 and 2.6.10 ), the drive seems to be recognized as "sda".

OK, so I changed my /etc/raidtab to have the new drive name, and it
appears to start up correctly.  I am also able to run vgscan, vgchange,
pvscan, pvdisplay and lvdisplay, and all results appear "normal."

However, as the previous writer described, mount refuses to work with
these Logical Volumes, as below:

root@tri1:/mnt# mount /dev/VGProjectData/lvol4 misc
/dev/VGProjectData/lvol4: Invalid argument
mount: /dev/VGProjectData/lvol4: can't read superblock

or:

root@tri1:/mnt# mount -t ext3 /dev/VGProjectData/lvol4 misc
mount: wrong fs type, bad option, bad superblock on \
/dev/VGProjectData/lvol4,
	or too many mounted file systems
	( could this be the IDE device where you in fact use
	ide-scsi so that sr0 or sda or so is needed? )



Any suggestions for my next step?


TIA,
Brian


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2229 bytes --]

[linux-lvm] snapshot problem when memory size is over 4GB

[Chung Hsien Hu]

Hi,
I got a server with Tyan5350 mainboard and 8GB ECC RAM. And
it seem that snapshot didn't work in either LVM1 or LVM2 when
the memory over 4GB is plugged. We have HIGHMEM64G=y kernel
option been set. Everything is ok when the comination is
"snapshot + 4GB RAM" or "no snapshot + 8GB RAM"...
Any clues?
PS: Hope you could understand my question, english is not my
mother language. :(

1. in linux-2.4.27 + LVM-1.0.8, it failed to activate the VG with
any existed snapshot volume.
bash-2.03# vgchange -ay
vgchange -- ERROR "Bad address" activating volume group "storage"

2. And again, in linux-2.4.27 + LVM-1.0.8, it failed to create snapshot
volume.
bash-2.03# lvcreate -A n -s  -n test_snap -l 16 /dev/storage/test
lvcreate -- WARNING: the snapshot will be automatically disabled once it 
gets full
lvcreate -- INFO: using default snapshot chunk size of 64 KB for 
"/dev/storage/test_snap"
lvcreate -- ERROR "Cannot allocate memory" creating VGDA for 
"/dev/storage/test_snap" in kernel

3. Then I turn to test linux-2.6.10 + LVM2. This time I can create a 
snapshot and it work well until
I reboot the system. The system will crash when I try to make a tarfile 
over the original volume.

bash-2.03# lvm version
  LVM version:     2.00.31 (2004-12-12)
  Library version: 1.00.19-ioctl (2004-07-03)
  Driver version:  4.3.0
bash-2.03# lvm lvscan
  ACTIVE   Original '/dev/storage/test' [1.95 GB] inherit
  ACTIVE            '/dev/storage/xfs' [1.95 GB] inherit
  ACTIVE   Snapshot '/dev/storage/test_snap' [500.00 MB] inherit
  ACTIVE            '/dev/storage/sysvolume' [2.44 GB] inherit
bash-2.03# tar cvf /mnt/xfs/test.tar /mnt/test
a /mnt/test/ directory
a /mnt/test/ACARD101RC3.iso 67534848 bytes, 131904 tape blocks
===>SYSTEM CRASHED!!......
system halt and the last line of messages on screen is:
<0>Kernel panic - not syncing: Fatal execption in interrupt

It's interesting to mention that the snapshot work well before reboot. Seem
it is kind of problem relate to VFS cache, snapshot and HIGHMEM support?

-- 
Mozo Hu. mozo@coventive
R&D Assistant Manager, Coventive Advance Technologies

Re: [linux-lvm] Can't mount logical volume - super block error

[Joe Harvell]

Sasha:

The symptoms you are describing sound similar to the problem I am 
having.  Refer to my recent post in linux-lvm entitled: "LVM2 
tools<-->library<-->driver compatibility".

Sasha Z wrote:
> I had a functioning lvm using four hard discs, but found it necessary
> to rebuild my operating system. Since then, while the vg and lv come
> online are read available, I can't actually mount the filesystem or do
> anything with it. It says it cannot read the superblock at locations 2
> and 16.
>
> does anybody have any thoughts on this?
>
> I've tried 2.00.25 and 2.00.33.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>