Re: raid10 and lvm problem on new lenny install

2011-03-20 Thread Jonathan Matthews
On 20 March 2011 02:24, Jim Green student.northwest...@gmail.com wrote:
 http://www.gagme.com/greg/linux/raid-lvm.php

That looks like an LVM1 article.

Here's a readable one about LVM2:
http://www.ibm.com/developerworks/library/l-lvm2/

With LVM2, there's no limit on the maximum numbers of extents per PV/LV.

Jonathan
-- 
Jonathan Matthews
London, UK
http://www.jpluscplusm.com/contact.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=K0fDpyWeEjzGT=8iflk__ro9fko_vwa_nz...@mail.gmail.com



Re: raid10 and lvm problem on new lenny install

2011-03-20 Thread Jim Green
On 20 March 2011 04:09, Jonathan Matthews cont...@jpluscplusm.com wrote:
 On 20 March 2011 02:24, Jim Green student.northwest...@gmail.com wrote:
 http://www.gagme.com/greg/linux/raid-lvm.php

 That looks like an LVM1 article.

 Here's a readable one about LVM2:
 http://www.ibm.com/developerworks/library/l-lvm2/

 With LVM2, there's no limit on the maximum numbers of extents per PV/LV.

Thanks!


 Jonathan
 --
 Jonathan Matthews
 London, UK
 http://www.jpluscplusm.com/contact.html


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/AANLkTi=K0fDpyWeEjzGT=8iflk__ro9fko_vwa_nz...@mail.gmail.com




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTim4yP=x8ndgcacb_yff2nhqdtdguplrwuj+0...@mail.gmail.com



raid10 and lvm problem on new lenny install

2011-03-19 Thread Jim Green
this is what I have from fdisk -l, I have lvm on /dev/md1, md1 is a
raid10 array with 4x2T drives.
Disk /dev/md1: 4000.5 GB, 4000525058048 bytes
2 heads, 4 sectors/track, 976690688 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
Disk identifier: 0x


this is what I have from pvdisplay
  --- Physical volume ---
  PV Name   /dev/md1
  VG Name   2600k
  PV Size   3.64 TiB / not usable 0
  Allocatable   yes
  PE Size   4.00 MiB
  Total PE  953799
  Free PE   831052
  Allocated PE  122747
  PV UUID   WUpkTR-xyCK-HGOc-Hk7Q-OfBp-Mqsz-GubCy7

I don't know why I only have a 3.64T pv size, it should be 4T I think,
in the installation of lenny i use ext3 for all the partitions,
also I set the unused space for each partition as 1%.

Thank you if you  have an explanation or if you have ways to reclaim
the 0.36 T from my arrays.

Jim


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimwmxzmvrgdow1bt0nvvxiiupfqpohp+hmsy...@mail.gmail.com



Re: raid10 and lvm problem on new lenny install

2011-03-19 Thread Gregory Seidman
On Sat, Mar 19, 2011 at 10:02:24PM -0400, Jim Green wrote:
 this is what I have from fdisk -l, I have lvm on /dev/md1, md1 is a
 raid10 array with 4x2T drives.
 Disk /dev/md1: 4000.5 GB, 4000525058048 bytes
 2 heads, 4 sectors/track, 976690688 cylinders
 Units = cylinders of 8 * 512 = 4096 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
 Disk identifier: 0x

Note that 4000525058048 != 4 x 2^40 (4398046511104)

 this is what I have from pvdisplay
   --- Physical volume ---
   PV Name   /dev/md1
   VG Name   2600k
   PV Size   3.64 TiB / not usable 0
   Allocatable   yes
   PE Size   4.00 MiB
   Total PE  953799
   Free PE   831052
   Allocated PE  122747
   PV UUID   WUpkTR-xyCK-HGOc-Hk7Q-OfBp-Mqsz-GubCy7

2^40 = 1099511627776

4000525058048 / 1099511627776 = 3.6384563446044921875 ~= 3.64

 I don't know why I only have a 3.64T pv size, it should be 4T I think,
 in the installation of lenny i use ext3 for all the partitions,
 also I set the unused space for each partition as 1%.
 
 Thank you if you  have an explanation or if you have ways to reclaim
 the 0.36 T from my arrays.

The difference is between what vendors use to describe their drives (TB,
meaning trillions of bytes) and what sane computer systems use (TiB,
meaning 2^40 bytes).

 Jim
--Greg


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110320021554.ga29...@anthropohedron.net



Re: raid10 and lvm problem on new lenny install

2011-03-19 Thread Jim Green
Thank you for the excellent explanation!


http://www.gagme.com/greg/linux/raid-lvm.php
from this link I read

The maximum number of physical extents is approximately 65k so take
your maximum volume size and divide it by 65k then round it to the
next nice round number. 

looks like I already have

 Total PE  953799

this is bigger than 65k,

does anyone know the current maximum number PE in debian lenny?

Jim

On 19 March 2011 22:15, Gregory Seidman
gsslist+deb...@anthropohedron.net wrote:
 On Sat, Mar 19, 2011 at 10:02:24PM -0400, Jim Green wrote:
 this is what I have from fdisk -l, I have lvm on /dev/md1, md1 is a
 raid10 array with 4x2T drives.
 Disk /dev/md1: 4000.5 GB, 4000525058048 bytes
 2 heads, 4 sectors/track, 976690688 cylinders
 Units = cylinders of 8 * 512 = 4096 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
 Disk identifier: 0x

 Note that 4000525058048 != 4 x 2^40 (4398046511104)

 this is what I have from pvdisplay
   --- Physical volume ---
   PV Name               /dev/md1
   VG Name               2600k
   PV Size               3.64 TiB / not usable 0
   Allocatable           yes
   PE Size               4.00 MiB
   Total PE              953799
   Free PE               831052
   Allocated PE          122747
   PV UUID               WUpkTR-xyCK-HGOc-Hk7Q-OfBp-Mqsz-GubCy7

 2^40 = 1099511627776

 4000525058048 / 1099511627776 = 3.6384563446044921875 ~= 3.64

 I don't know why I only have a 3.64T pv size, it should be 4T I think,
 in the installation of lenny i use ext3 for all the partitions,
 also I set the unused space for each partition as 1%.

 Thank you if you  have an explanation or if you have ways to reclaim
 the 0.36 T from my arrays.

 The difference is between what vendors use to describe their drives (TB,
 meaning trillions of bytes) and what sane computer systems use (TiB,
 meaning 2^40 bytes).

 Jim
 --Greg


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20110320021554.ga29...@anthropohedron.net




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTinQ=5oZdBVrc0X48ojS8KmsFTEgGgCcxsUQ69=t...@mail.gmail.com



root on LVM problem on etch

2007-04-21 Thread Tony Middleton

Wasn't sure where to raise this.

I used to run a sarge system with root on LVM volume on raid1.  ( I 
don't think raid is relevant here but mention it for completeness).


When I upgraded to etch the upgrade seemed to go OK but the system 
wouldn't reboot.  It appeared that the LVM volume wasn't activated.  I 
couldn't sort the problem out and was under time pressure so did a clean 
etch install without LVM.


I've now tried to move back to root on LVM on raid and hit the same 
problem.  After some playing around the problem seems to be my root= 
parameter in Grub.  I have always specified a LVM volume as /dev/vg/lv 
and this worked fine on Sarge.  On Etch it seems you have to use 
/dev/mapper/vg-lv.  Can't be sure that this is exactly the same issue I 
had on the upgrade but seems likely.


This may be documented somewhere but couldn't find it - if it is, 
apologies.


Regards

Tony Middleton.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




LVM problem

2006-12-29 Thread Pierguido
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all.
I've installed etch on a file server with a raid array of 3,5 TB.
With the raid system i've created two virtual disk, sda for the OS and
sdb for the user datas shared via samba.
I've installed lvm for the second disk and i created two logical volumes
data (2TB) and admin (200GB).
I mounted them and everything is ok.
I wanted to extend the data volume to the fill all the free space
(962GB) but when i make:

lvextend -L+962G /dev/mapper/uservg-data

It respond me:

  Volume group mapper doesn't exist

But:

[EMAIL PROTECTED]:~# ls -l /dev/mapper/uservg-data
brw-rw 1 root disk 254, 0 2006-12-29 10:40 /dev/mapper/uservg-data

I searched a bit but nothing found.

Pier
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFlO1w0EvuLV/O0yoRAiBNAKDom1x7y03M5QfGLWdjKw0S6i5IBQCg0nAg
L+wCXuDptIRFX+UlOA/XGSI=
=Cshd
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: LVM problem

2006-12-29 Thread Mike Bird
On Friday 29 December 2006 02:26, Pierguido wrote:
 I wanted to extend the data volume to the fill all the free space
 (962GB) but when i make:

 lvextend -L+962G /dev/mapper/uservg-data

 It respond me:

   Volume group mapper doesn't exist

 But:

 [EMAIL PROTECTED]:~# ls -l /dev/mapper/uservg-data
 brw-rw 1 root disk 254, 0 2006-12-29 10:40 /dev/mapper/uservg-data

LVM probably knows the LV by a different name.  Try:

  lvextend -L+926G /dev/uservg/data

If that doesn't work please check the output of lvscan.

--Mike Bird


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: LVM problem

2006-12-29 Thread Wesley J. Landaker
On Friday 29 December 2006 03:26, Pierguido wrote:
 lvextend -L+962G /dev/mapper/uservg-data

 It respond me:

   Volume group mapper doesn't exist

lvextend -L+962G uservg/data

-- 
Wesley J. Landaker [EMAIL PROTECTED] xmpp:[EMAIL PROTECTED]
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2


pgpQ16CZqsEPu.pgp
Description: PGP signature


Re: LVM problem

2006-03-07 Thread Andrew Cady
On Sun, Mar 05, 2006 at 06:24:34PM -0500, Bernard Fay wrote:
 For any LVM commands I run I receive the following message:
 
 Incorrect metadata area header checksum
 
 and/or 
 
 Volume group mapper doesn't exist

Either your metadata has gotten messed up or you're using the wrong
device.

If the metadata is corrupt, and you have backups of it (you probably do
-- in /etc/lvm/backup), then vgcfgrestore can restore it.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: LVM problem

2006-03-07 Thread Bernard Fay
On Tue, 2006-03-07 at 15:21 -0500, Andrew Cady wrote:
 On Sun, Mar 05, 2006 at 06:24:34PM -0500, Bernard Fay wrote:
  For any LVM commands I run I receive the following message:
  
  Incorrect metadata area header checksum
  
  and/or 
  
  Volume group mapper doesn't exist
 
 Either your metadata has gotten messed up or you're using the wrong
 device.
 
 If the metadata is corrupt, and you have backups of it (you probably do
 -- in /etc/lvm/backup), then vgcfgrestore can restore it.
 
 

I gave it a try and that did not fix it.

vgcfgrestore lnxvg
  Incorrect metadata area header checksum
  Restored volume group lnxvg


and I tried:

vgcfgrestore -l lnxvg
  No archives found in /etc/lvm/archive.

  File: /etc/lvm/backup/lnxvg
  Incorrect metadata area header checksum
  VG name:  lnxvg
  Description:  Created *after* executing '/sbin/vgcfgbackup'
  Backup Time:  Sat Feb 25 21:02:37 2006


I think it does not sound too good.  :(

Something else we could try.

TIA,
Bern




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: LVM problem

2006-03-07 Thread Andrew Cady
On Tue, Mar 07, 2006 at 06:45:06PM -0500, Bernard Fay wrote:

 vgcfgrestore lnxvg
   Incorrect metadata area header checksum
   Restored volume group lnxvg

It said it's restored, but it's still not working?  Not good...

 Something else we could try.

Well, I don't know what.  Try asking on an LVM mailing list.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



LVM problem

2006-03-05 Thread Bernard Fay
For any LVM commands I run I receive the following message:

Incorrect metadata area header checksum

and/or 

Volume group mapper doesn't exist


Someone knows why and how it could be fixed?  I run Debian etch with
kernel 2.6.12-1-386 and lvm2 version 2.01.04-5.

TIA,
Bernard




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: 2.6 LVM problem

2004-05-11 Thread Stephan Seitz
On Mon, May 10, 2004 at 08:49:43PM -0400, Kirill Lapshin wrote:
Actually it works automagically, just install lvm2 and you are fine. I 
did it just this past weekend -- installed debian sarge from scratch 
Here it didn't work. It was a woody installation, upgraded to testing.
lvm10 and lvm2 are installed. 2.6.5 didn't find the lvm partitions
(lvm support in kernel).
using beta4 installer, with kernel 2.4, configured lvm, installed lvm2 
package, compiled kernel 2.6.5, rebooted.. and lvm came up just fine. If 
Here not. Maybe because my 2.4 kernel doesn't have the device mapper
patches?
Shade and sweet water!

	Stephan

--
| Stephan SeitzE-Mail: [EMAIL PROTECTED] |
|  WWW: http://fsing.rootsland.net/~stse/|
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |


signature.asc
Description: Digital signature


Re: 2.6 LVM problem

2004-05-11 Thread Allan Wind
Did you see the LVM 2 faq?
http://www.ibiblio.org/mdw/HOWTO/LVM-HOWTO/lvm2faq.html.

I learned the hard way, that it is not a good idea to convert your meta
data format from lvm1 to 2 till you can boot with at least 1 good kernel
with lvm2 support.  It is always best to only change one thing at a
time, but I thought it was more trouble than it was worth getting 2.4
going with lvm2 support, especially since lvm2 is backwards compatible.

Other than that it was pretty easy, install 2.6.5 with device mapper
support.  Install lvm2.  Boot, fix fstab to new mount points.  Reboot.
I hit a bug (now fixed) that caused the lvm script to fail.


/Allan
-- 
Allan Wind
P.O. Box 2022
Woburn, MA 01888-0022
USA


signature.asc
Description: Digital signature


Re: 2.6 LVM problem

2004-05-11 Thread Andrew Ingram
On Tue, 2004-05-11 at 01:49, Kirill Lapshin wrote:
 Stephan Seitz wrote:
  But you need lvm2 for kernel 2.6.*. And I don't know if there is an
  upgrade path to use the old lvm1 with lvm2. It should be
  backwards-compatible, but it uses different config files.
  
  The lvm2 package doesn't contain any docs for an upgrade (or I didn't
  find them).
 
 Actually it works automagically, just install lvm2 and you are fine. I 
 did it just this past weekend -- installed debian sarge from scratch 
 using beta4 installer, with kernel 2.4, configured lvm, installed lvm2 
 package, compiled kernel 2.6.5, rebooted.. and lvm came up just fine. If 
 lvm2 package is missing than you will get lvm working under 2.4 but not 
 under 2.6. I remember reading somewhere that lvm10 and lvm2 packages are 
 smart, they basically install proxy lvm tools which determine your 
 kernel version and run appropriate userspace lvm tools (10 for 2.4 and 2 
 for 2.6). I don't remember where I've seen this information though...

OK, the plot grows thicker! I installed the lvm2 package. 2.4.22 still
works fine (thankfully!). Now, during the bootup of the 2.6.5 kernel, I
get:

Setting up LVM Volume Groups...
Reading all physical volumes. This may take a while...
Found volume group vg00 using metadata type lvm1
Internal error: unknown device-mapper task 15
Internal error: unknown device-mapper task 15

At this point, it hangs and requires a ctrl-c to move on and continue
booting.

I have done a google and it doesn't turn anything up with that error :(
Any more ideas?

Thanks,
Andrew



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: 2.6 LVM problem

2004-05-10 Thread Kirill Lapshin
Stephan Seitz wrote:
But you need lvm2 for kernel 2.6.*. And I don't know if there is an
upgrade path to use the old lvm1 with lvm2. It should be
backwards-compatible, but it uses different config files.
The lvm2 package doesn't contain any docs for an upgrade (or I didn't
find them).
Actually it works automagically, just install lvm2 and you are fine. I 
did it just this past weekend -- installed debian sarge from scratch 
using beta4 installer, with kernel 2.4, configured lvm, installed lvm2 
package, compiled kernel 2.6.5, rebooted.. and lvm came up just fine. If 
lvm2 package is missing than you will get lvm working under 2.4 but not 
under 2.6. I remember reading somewhere that lvm10 and lvm2 packages are 
smart, they basically install proxy lvm tools which determine your 
kernel version and run appropriate userspace lvm tools (10 for 2.4 and 2 
for 2.6). I don't remember where I've seen this information though...

HTH

--Kirill

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: 2.6 LVM problem

2004-05-10 Thread Andrew Ingram
On Mon, 2004-05-10 at 11:38, David Cannings wrote:
 On Monday 10 May 2004 10:55, Andrew Ingram wrote:
  /dev/mapper/control: open failed: No such device
  Is device-mapper driver missing from kernel?
  Warning: '/proc/partitions' does not match '/dev' directory structure.
  Name change: '/dev/lvma' - '/dev/vg00/mythtvlv'
  Added 2.6.5
  Added 2.4.22-HT *
  Device mapper is installed in the kernel. Some googling showed that 
  this was the sort of message that people using DEVFS in their kernel
  experienced. I'm not using DEVFS however.
 
 Which kernel is device mapper built into?  If you were trying to run lilo 
 from your 2.4 kernel and hadn't got device mapper built into it you would 
 likely get that error.
 
 As for 2.6, don't forget you will also need the newer LVM userspace tools.

David, you were absolutely right. The lilo error was down to the 2.4
kernel not having device mapper built in. Running lilo when running
under 2.6.5 produced no error.

I did update the lvm-common and lvm10 packages to the latest (I'm
running Sid btw). But this produced the same thing (no mounted lvm),
although I've noticed some additional errors during bootup now. Here is
a small bit from /var/log/boot:

...
All modules loaded.
Setting up LVM Volume Groups...
vgscan -- LVM driver/module not loaded?
vgchange -- LVM driver/module not loaded?
...


As far as I know, LVM is built into my kernel. In the menuconfig I
selected to build in the multi device support (didn't bother with RAID
since I dont need it). The section from my .config is as follows:
#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
# CONFIG_MD_MULTIPATH is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_CRYPT is not set


Is this enough or am I missing something?

Regards,
Andrew





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: 2.6 LVM problem

2004-05-10 Thread Stephan Seitz
On Mon, May 10, 2004 at 02:50:29PM +0100, Andrew Ingram wrote:
I did update the lvm-common and lvm10 packages to the latest (I'm
running Sid btw). But this produced the same thing (no mounted lvm),
But you need lvm2 for kernel 2.6.*. And I don't know if there is an
upgrade path to use the old lvm1 with lvm2. It should be
backwards-compatible, but it uses different config files.
The lvm2 package doesn't contain any docs for an upgrade (or I didn't
find them).
Shade and sweet water!

	Stephan

--
| Stephan SeitzE-Mail: [EMAIL PROTECTED] |
|  WWW: http://fsing.rootsland.net/~stse/|
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |


signature.asc
Description: Digital signature


2.6 LVM problem

2004-05-10 Thread Andrew Ingram
I have a box which runs 2.4.22 just fine but wanted to try out 2.6.5 as
some of the extra features from 2.6 would be very welcome. The box has
several normal partitions (ReiserFS) and one partition that is
configured with LVM (for future expansion, at the moment it's just one
partition on the main HDD). Compiling and installing the 2.6.5 kernel
was fine. However, when I came to run lilo after adding the entry for
the new kernel in lilo.conf, I got the following message:

/dev/mapper/control: open failed: No such device
Is device-mapper driver missing from kernel?
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/lvma' - '/dev/vg00/mythtvlv'
Added 2.6.5
Added 2.4.22-HT *

Device mapper is installed in the kernel. Some googling showed that this
was the sort of message that people using DEVFS in their kernel
experienced. I'm not using DEVFS however.

Rebooting and selecting the new kernel resulted in the machine booting
just fine, but the lvm partition wasn't mounted. The error during bootup
was:
mount: /dev/vg00/mythtvlv is not a valid block device


Can anyone tell me what is going wrong here? I can post my .config for
my kernel if that would help.

Thanks,
Andrew


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: 2.6 LVM problem

2004-05-10 Thread David Cannings
On Monday 10 May 2004 10:55, Andrew Ingram wrote:
 /dev/mapper/control: open failed: No such device
 Is device-mapper driver missing from kernel?
 Warning: '/proc/partitions' does not match '/dev' directory structure.
 Name change: '/dev/lvma' - '/dev/vg00/mythtvlv'
 Added 2.6.5
 Added 2.4.22-HT *
 Device mapper is installed in the kernel. Some googling showed that 
 this was the sort of message that people using DEVFS in their kernel
 experienced. I'm not using DEVFS however.

Which kernel is device mapper built into?  If you were trying to run lilo 
from your 2.4 kernel and hadn't got device mapper built into it you would 
likely get that error.

As for 2.6, don't forget you will also need the newer LVM userspace tools.

David


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: lvm problem

2002-12-02 Thread Rainer Ellinger
Benjamin Zeiss schrieb:
 wahrscheinlich habe ich da tatsaechlich irgendwas geaendert.
 offensichtlich entstehen, bei immer laufenden rechnern irgendwelche
 gedaechtnisluecken. ich kann dazu nur sagen: es lebe knoppix. das war
 ein wirklich simpler test, ob das system im ar*** ist.

Mit welchem Ergebnis? Selbst das sagst Du nicht. Was willst Du 
eigentlich? Deine LVM-Config wieder herstellen oder dummes Zeug labern?
Übrigens, Deine Mailsoftware könnte auch mal Pflege gebrauchen, um 
Msg-ID, References und In-Reply-To zu erzeugen.

-- 
[EMAIL PROTECTED]


-- 
Häufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)




Re: lvm problem

2002-12-02 Thread Benjamin Zeiss
Hallo Rainer,

--On Monday, December 02, 2002 10:40:12 AM +0100 Rainer Ellinger 
[EMAIL PROTECTED] wrote:

Benjamin Zeiss schrieb:

wahrscheinlich habe ich da tatsaechlich irgendwas geaendert.
offensichtlich entstehen, bei immer laufenden rechnern irgendwelche
gedaechtnisluecken. ich kann dazu nur sagen: es lebe knoppix. das war
ein wirklich simpler test, ob das system im ar*** ist.


Mit welchem Ergebnis? Selbst das sagst Du nicht. Was willst Du
eigentlich?


ich hatte leider vergessen in aller deutlichkeit zu erwaehnen, dass sich 
das problem erledigt hat. volumegroup ist ok, debian system scheint 
irgendwie einen defekt zu haben. mit knoppix gebootet wird die VG inkl. LV 
und PV's nach entsprechenden scans und aktivierungen erkannt und kann 
problemlos gemountet werden. ich danke fuer eure hilfe...

--
Benjamin Zeiss


--
Häufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: lvm problem

2002-12-01 Thread Benjamin Zeiss
Hallo Rainer,

--On Sonntag, 1. Dezember 2002 08:40 +0100 Rainer Ellinger 
[EMAIL PROTECTED] wrote:

Benjamin Zeiss schrieb:

vgchange -- ERROR: can't get name(s) of physical volumes
vgchange -- Please check, if /proc is mounted


Was macht vgcfgrestore? Vorher Manpage lesen und einen -test machen.


danke erstmal fuer den hinweis. die manpage beschreibeung ist leider etwas 
unzureichend:


vgcfgrestore restores the volume group descriptor area from backup files in 
/etc/lvmconf or from VGConfPath to
the given initialized (see pvcreate(8) ) PhysicalVolumePath.  The default 
backup  file  is
/etc/lvmconf/Vol­umeGroupName.conf.  This command DOES NOT restore data 
contained in logical volume(s), only the LVM configura­tion metadata!


da steht zwar drin, dass die Daten nicht wiederhergestellt werden, aber 
leider *nicht*, ob sie denn uebernommen werden sofern nicht geloescht. 
sollte das logical volume wiederhergestellt werden und sind keine daten 
drauf, dann bringt das auch nicht so furchtbar viel.

bei google gibt es einen ganzen eintrag zum stichwort 'vgcfgrestore' ;-)

--
Benjamin Zeiss
GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc


--
Häufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: lvm problem

2002-12-01 Thread Johannes Hirte
Benjamin Zeiss [EMAIL PROTECTED] schrieb am 01.12.02 11:11:33:
 Hallo Rainer,
 
 --On Sonntag, 1. Dezember 2002 08:40 +0100 Rainer Ellinger 
 [EMAIL PROTECTED] wrote:
 
  Benjamin Zeiss schrieb:
  vgchange -- ERROR: can't get name(s) of physical volumes
  vgchange -- Please check, if /proc is mounted
 
  Was macht vgcfgrestore? Vorher Manpage lesen und einen -test machen.
 
 danke erstmal fuer den hinweis. die manpage beschreibeung ist leider etwas 
 unzureichend:
 
 
 vgcfgrestore restores the volume group descriptor area from backup files in 
 /etc/lvmconf or from VGConfPath to
 the given initialized (see pvcreate(8) ) PhysicalVolumePath.  The default 
 backup  file  is
 /etc/lvmconf/Vol­umeGroupName.conf.  This command DOES NOT restore data 
 contained in logical volume(s), only the LVM configura­tion metadata!
 
 
 da steht zwar drin, dass die Daten nicht wiederhergestellt werden, aber 
 leider *nicht*, ob sie denn uebernommen werden sofern nicht geloescht. 
 sollte das logical volume wiederhergestellt werden und sind keine daten 
 drauf, dann bringt das auch nicht so furchtbar viel.
 
 bei google gibt es einen ganzen eintrag zum stichwort 'vgcfgrestore' ;-)
 
 --
 Benjamin Zeiss
 GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc
 

Mal ein klein wenig Ursachenforschung:

Hast du was am System geändert, bevor du neu gestartet hast?
Was sagt 'fdisk -l' ?

Johannes

__
Keinen passenden Spruch fur die SMS parat? Mit WEB.DE FreeMail 
kein Problem mehr! http://freemail.web.de/features?mc=021149


--
Häufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)




Re: lvm problem

2002-12-01 Thread Benjamin Zeiss
hallo,

--On Montag, 2. Dezember 2002 00:25 +0100 Johannes Hirte 
[EMAIL PROTECTED] wrote:

Mal ein klein wenig Ursachenforschung:

Hast du was am System geändert, bevor du neu gestartet hast?
Was sagt 'fdisk -l' ?


wahrscheinlich habe ich da tatsaechlich irgendwas geaendert. offensichtlich 
entstehen, bei immer laufenden rechnern irgendwelche gedaechtnisluecken. 
ich kann dazu nur sagen: es lebe knoppix. das war ein wirklich simpler 
test, ob das system im ar*** ist.

--
Benjamin Zeiss
GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc


--
Häufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



lvm problem

2002-11-30 Thread Benjamin Zeiss
Hallo,

ich habe ein LVM Problem mit meinem Linux Desktop. Auf dem System ist 
Debian Woody installiert.  Der Rechner ist always on. Nun musste ich 
neulich doch mal neustarten und dann lief der Rechner nicht mehr hoch, 
indem er meinte er könne mein /dev/vg01 (das ist die LVM volume group) 
nicht aktivieren;  gefunden hat er es mit vgscan, aber das vgchange -a y 
verweigert mit

vgchange -- ERROR: can't get name(s) of physical volumes
vgchange -- Please check, if /proc is mounted

den Dienst.

Mein /proc ist gemountet und in /proc/lvm /global steht:

Total:  0 VGs   0 PVs   0 LVs  (LVs open)
Global: 152 bytes malloced  IOP version 10   0:05:06 active

Bei der Recherche auf Google habe ich immer wieder gefunden, das dieses 
Verhalten mit devfs zusammenhängt, dieses benutze ich aber nicht. Auch das 
/dev Verzeichnis ist da und funktioniert.

Das LVM für meine Homeverzeichnisse (/home) besteht aus zwei Partitionen 
/dev/hde4 und /dev/hdg1
Auf /dev/hde3 ist / gemountet. Ein Hardwarefehler schliesst sich also aus.

Wenn ich /home aus der /etc/fstab austrage, dann läuft der Rechner hoch und 
root kann ganz normal arbeiten. Die User natürlich nicht, da deren 
Homeverzeichnisse fehlen ja.

Einen Dump des Debugging vgchange findest Du unter:
http://www.kellnerweg.de/~dz/vgchangedump

Gibt es einen Weg das LVM wieder zu aktivieren _ohne_ Datenverlust?

Vielen Dank im voraus


--
Benjamin Zeiss
GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc


--
Häufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: lvm problem

2002-11-30 Thread Johannes Hirte
Benjamin Zeiss [EMAIL PROTECTED] schrieb am 30.11.02 11:20:05:
 Hallo,
 
 ich habe ein LVM Problem mit meinem Linux Desktop. Auf dem System ist 
 Debian Woody installiert.  Der Rechner ist always on. Nun musste ich 
 neulich doch mal neustarten und dann lief der Rechner nicht mehr hoch, 
 indem er meinte er könne mein /dev/vg01 (das ist die LVM volume group) 
 nicht aktivieren;  gefunden hat er es mit vgscan, aber das vgchange -a y 
 verweigert mit

was spuckt vgscan aus?
welche Kernelvesion nutzt du? Ich gehe mal davon aus, dass du den LVM
aus Woddy installiert hast.

 
 vgchange -- ERROR: can't get name(s) of physical volumes
 vgchange -- Please check, if /proc is mounted
 
 den Dienst.
 
 Mein /proc ist gemountet und in /proc/lvm /global steht:
 
 Total:  0 VGs   0 PVs   0 LVs  (LVs open)
 Global: 152 bytes malloced  IOP version 10   0:05:06 active
 
 Bei der Recherche auf Google habe ich immer wieder gefunden, das dieses 
 Verhalten mit devfs zusammenhängt, dieses benutze ich aber nicht. Auch das 
 /dev Verzeichnis ist da und funktioniert.
 
 Das LVM für meine Homeverzeichnisse (/home) besteht aus zwei Partitionen 
 /dev/hde4 und /dev/hdg1
 Auf /dev/hde3 ist / gemountet. Ein Hardwarefehler schliesst sich also aus.
 
 Wenn ich /home aus der /etc/fstab austrage, dann läuft der Rechner hoch und 
 root kann ganz normal arbeiten. Die User natürlich nicht, da deren 
 Homeverzeichnisse fehlen ja.
 
 Einen Dump des Debugging vgchange findest Du unter:
 http://www.kellnerweg.de/~dz/vgchangedump

bin noch am lesen...

 
 Gibt es einen Weg das LVM wieder zu aktivieren _ohne_ Datenverlust?
 
 Vielen Dank im voraus
 
 
 --
 Benjamin Zeiss
 GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc
 

Johannes
__
SMS verschicken und die Telefonnummer gleich im Adressbuch speichern.
Geht nicht? -  Geht doch! - http://freemail.web.de/features/?mc=021150


--
Häufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)




Re: lvm problem

2002-11-30 Thread Benjamin Zeiss
Hallo Johannes,

--On Samstag, 30. November 2002 17:20 +0100 Johannes Hirte 
[EMAIL PROTECTED] wrote:

ich habe ein LVM Problem mit meinem Linux Desktop. Auf dem System ist
Debian Woody installiert.  Der Rechner ist always on. Nun musste ich
neulich doch mal neustarten und dann lief der Rechner nicht mehr hoch,
indem er meinte er könne mein /dev/vg01 (das ist die LVM volume group)
nicht aktivieren;  gefunden hat er es mit vgscan, aber das vgchange -a y
verweigert mit


was spuckt vgscan aus?


hier sind noch ein paar weitere debuggingausgaben:

http://www.kellnerweg.de/~dz/vgscan-dump
http://www.kellnerweg.de/~dz/pvscan-dump
http://www.kellnerweg.de/~dz/vgchangedump


welche Kernelvesion nutzt du?


debian 2.4.18-686


Ich gehe mal davon aus, dass du den LVM aus Woddy installiert hast.


ja. direkt aus der kommandozeile mit den lvm/ext3 tools und hat auch vorher 
nach neustarts funktioniert.

--
Benjamin Zeiss
GPG Public Key: http://www.kellnerweg.de/~bzeiss/pubkey.asc


--
Häufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: lvm problem

2002-11-30 Thread Rainer Ellinger
Benjamin Zeiss schrieb:
 vgchange -- ERROR: can't get name(s) of physical volumes
 vgchange -- Please check, if /proc is mounted

Was macht vgcfgrestore? Vorher Manpage lesen und einen -test machen. 

-- 
[EMAIL PROTECTED]


-- 
Häufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)