[linux-lvm] LVM problems

[linux-lvm] LVM problems

[Tobias Hahn]

Hi!

I have serious trouble trying to get LVM to work again since I upgraded my lvm-tools to 0.9beta6. I cannot access my vg (and needless to say, almost all of my system is on that vg :-( ). The problem is that the kernel complains about an unsupported ioctl. I looked up this problem in lvm-related mailinglists and figured out that this is a version mismatch between kernel lvm and user lvm. At that point I was using kernel 2.4.3. According to the mailing list, the problem should be fixed in kernel 2.4.4. However, kernel 2.4.5 (downloaded from ftp.kernel.org) still contains 0.9beta2. So I downloaded the lvm-source from ftp.sistina.com (both beta6 and beta7) and tried to patch kernel 2.4.5 following the instructions in PATCHES/README. The patched kernel, however, does not link any longer.

All I'm asking for is a way to get my data back - either by telling me how lvm can be convinced to run or by just getting that stuff off lvm and removing lvm from my system. It would be very nice if someone could at least acknowledge receipt of this problem report, my last mail seems to have vanished out in the void.

Thanx everyone for reading this mail!

Regards, Tobias Hahn

ld -m elf_i386 -T /tmp/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
        --start-group \
        arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
         drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/isdn/isdn.a drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o drivers/md/mddev.o \
        net/network.o \
        /tmp/linux/arch/i386/lib/lib.a /tmp/linux/lib/lib.a /tmp/linux/arch/i386/lib/lib.a \
        --end-group \
        -o vmlinux
drivers/md/mddev.o: In function `__update_hardblocksize':
drivers/md/mddev.o(.text+0x7e01): undefined reference to `get_hardblocksize'
drivers/md/mddev.o(.text+0x7e3d): undefined reference to `get_hardblocksize'
make: *** [vmlinux] Error 1

______________________________________________________________________________
Ferienklick.de - Jede Menge Urlaub auf einen Blick!
Hier geht's zu Ihrem Traumstrand: http://ferienklick.de/?PP=2-0-100-105-1

Re: [linux-lvm] LVM problems

[Ilya Martynov]

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



TH> [..skip..]

TH> ld -m elf_i386 -T /tmp/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \
TH>         --start-group \
TH>         arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
TH>          drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/char/agp/agp.o drivers/isdn/isdn.a drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o drivers/md/mddev.o \
TH>         net/network.o \
TH>         /tmp/linux/arch/i386/lib/lib.a /tmp/linux/lib/lib.a /tmp/linux/arch/i386/lib/lib.a \
TH>         --end-group \
TH>         -o vmlinux
TH> drivers/md/mddev.o: In function `__update_hardblocksize':
TH> drivers/md/mddev.o(.text+0x7e01): undefined reference to `get_hardblocksize'
TH> drivers/md/mddev.o(.text+0x7e3d): undefined reference to `get_hardblocksize'
TH> make: *** [vmlinux] Error 1

It is known problem and should be fixed in future releases.
For now use attached patch.

I've found it in archives of this maillist when I've faced simular problem.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: lvm-0.9.1_beta7-2.4.5-get_hardblocksize.patch --]
[-- Type: text/x-patch, Size: 680 bytes --]

--- lvm.c~	Wed Jun 13 15:57:06 2001
+++ lvm.c	Wed Jun 13 15:58:10 2001
@@ -1791,7 +1791,7 @@
 	int max_hardblocksize = 0, hardblocksize;
 
 	for (le = 0; le < lv->lv_allocated_le; le++) {
-		hardblocksize = get_hardblocksize(lv->lv_current_pe[le].dev);
+		hardblocksize = get_hardsect_size(lv->lv_current_pe[le].dev);
 		if (hardblocksize == 0)
 			hardblocksize = 512;
 		if (hardblocksize > max_hardblocksize)
@@ -1801,7 +1801,7 @@
 	if (lv->lv_access & LV_SNAPSHOT) {
 		for (e = 0; e < lv->lv_remap_end; e++) {
 			hardblocksize =
-				get_hardblocksize(
+				get_hardsect_size(
 					lv->lv_block_exception[e].rdev_new);
 			if (hardblocksize == 0)
 				hardblocksize = 512;

[-- Attachment #3: Type: text/plain, Size: 382 bytes --]

-- 
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Ilya Martynov (http://martynov.org/)                                    |
| GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80  E4AE BE1A 53EB 323B DEE6 |
| AGAVA Software Company (http://www.agava.com/)                          |
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] LVM problems

[Andreas Dilger]

Tobias Hahn writes:
> I have serious trouble trying to get LVM to work again since I upgraded
> my lvm-tools to 0.9beta6. I cannot access my vg (and needless to say,
> almost all of my system is on that vg :-( ). The problem is that the
> kernel complains about an unsupported ioctl. I looked up this problem in
> lvm-related mailinglists and figured out that this is a version mismatch
> between kernel lvm and user lvm.

But this message is only a warning, and not a real source of problems.
If you are having problems, it is from something else.  If you were using
the beta2 tools or earlier, there is a chance your VGDA is slightly broken
(UUID problems).  Please search the mailing list about this for instructions
on how to fix.

> At that point I was using kernel
> 2.4.3. According to the mailing list, the problem should be fixed in
> kernel 2.4.4. However, kernel 2.4.5 (downloaded from ftp.kernel.org) still
> contains 0.9beta2.

There are some LVM fixes in the -ac kernel patch, but none in the Linus
tree yet (sigh).

> So I downloaded the lvm-source from ftp.sistina.com
> (both beta6 and beta7) and tried to patch kernel 2.4.5 following the
> instructions in PATCHES/README. The patched kernel, however, does not
> link any longer.

> drivers/md/mddev.o(.text+0x7e01): undefined reference to `get_hardblocksize'
> drivers/md/mddev.o(.text+0x7e3d): undefined reference to `get_hardblocksize'

I could have sworn this problem was fixed already, but maybe only in CVS?
Time for a new patch release I guess.  As someone else already mentioned,
simply change get_hardblocksize to get_hardsect_size() in lvm.c.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

Re: [linux-lvm] LVM problems

[AJ Lewis]

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

On Tue, Jun 19, 2001 at 11:27:11AM -0600, Andreas Dilger wrote:
> I could have sworn this problem was fixed already, but maybe only in CVS?
> Time for a new patch release I guess.  As someone else already mentioned,
> simply change get_hardblocksize to get_hardsect_size() in lvm.c.

I dropped a patch on the FTP site:
ftp://ftp.sistina.com/pub/LVM/0.9.1_beta/lvm_0.9.1_beta7-get_hardblocksize.patch

apply this to your LVM source tree and regenerate the kernel patch.

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
A)bort, R)etry, I)nfluence with large hammer.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

RE: [linux-lvm] LVM problems

[Gonyou, Austin]

Why in the hell is this NOT in the source tree by default. This has really
got be boggled. I've seen tons of others have this proble, I've had this
problem, and still it doesn't seem to get itself into the tree. Is this
because it is a temporary problem or something?

-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com 

> -----Original Message-----
> From: AJ Lewis [mailto:lewis@sistina.com]
> Sent: Tuesday, June 19, 2001 2:24 PM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] LVM problems
> 
> 
> On Tue, Jun 19, 2001 at 11:27:11AM -0600, Andreas Dilger wrote:
> > I could have sworn this problem was fixed already, but 
> maybe only in CVS?
> > Time for a new patch release I guess.  As someone else 
> already mentioned,
> > simply change get_hardblocksize to get_hardsect_size() in lvm.c.
> 
> I dropped a patch on the FTP site:
> ftp://ftp.sistina.com/pub/LVM/0.9.1_beta/lvm_0.9.1_beta7-get_h
> ardblocksize.patch
> 
> apply this to your LVM source tree and regenerate the kernel patch.
> 
> Regards,
> -- 
> AJ Lewis
> Sistina Software Inc.                  Voice:  612-638-0500
> 1313 5th St SE, Suite 111              Fax:    612-638-0500
> Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
> http://www.sistina.com
> 
> Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 
> 1261 0029 2648
> Get my key at: http://www.sistina.com/~lewis/gpgkey
>  (Unfortunately, the PKS-type keyservers do not work with 
> multiple sub-keys)
> 
> -----Begin Obligatory Humorous 
> Quote----------------------------------------
> A)bort, R)etry, I)nfluence with large hammer.
> -----End Obligatory Humorous 
> Quote------------------------------------------
> 

Re: [linux-lvm] LVM problems

[AJ Lewis]

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

On Tue, Jun 19, 2001 at 02:28:05PM -0500, Gonyou, Austin wrote:
> Why in the hell is this NOT in the source tree by default. This has really
> got be boggled. I've seen tons of others have this proble, I've had this
> problem, and still it doesn't seem to get itself into the tree. Is this
> because it is a temporary problem or something?

It *is* in the source tree by default.  It is in the CVS.  It is not in
LVM 0.9.1 Beta7 because LVM 0.9.1 Beta7 was released before linux 2.4.4,
which is when the problem surfaced.  We have not had a release since then,
so it is not in the latest release.

You can now grab the patch and apply it to beta7, which fixes the problem,
or you can use the CVS repository.  I really don't know what else you expect
us to do.

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
 (Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)

-----Begin Obligatory Humorous Quote----------------------------------------
geep!
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

RE: [linux-lvm] LVM problems

[Gonyou, Austin]

Ahhh..that explains a lot. My sincere apologies. I was not aware that it was
fixed in CVS. I'd never seen anyone be referenced to that. Thanks for info.

-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com 

> -----Original Message-----
> From: AJ Lewis [mailto:lewis@sistina.com]
> Sent: Tuesday, June 19, 2001 4:19 PM
> To: linux-lvm@sistina.com
> Subject: Re: [linux-lvm] LVM problems
> 
> 
> On Tue, Jun 19, 2001 at 02:28:05PM -0500, Gonyou, Austin wrote:
> > Why in the hell is this NOT in the source tree by default. 
> This has really
> > got be boggled. I've seen tons of others have this proble, 
> I've had this
> > problem, and still it doesn't seem to get itself into the 
> tree. Is this
> > because it is a temporary problem or something?
> 
> It *is* in the source tree by default.  It is in the CVS.  It 
> is not in
> LVM 0.9.1 Beta7 because LVM 0.9.1 Beta7 was released before 
> linux 2.4.4,
> which is when the problem surfaced.  We have not had a 
> release since then,
> so it is not in the latest release.
> 
> You can now grab the patch and apply it to beta7, which fixes 
> the problem,
> or you can use the CVS repository.  I really don't know what 
> else you expect
> us to do.
> 
> Regards,
> -- 
> AJ Lewis
> Sistina Software Inc.                  Voice:  612-638-0500
> 1313 5th St SE, Suite 111              Fax:    612-638-0500
> Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
> http://www.sistina.com
> 
> Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B  52A0 941E 
> 1261 0029 2648
> Get my key at: http://www.sistina.com/~lewis/gpgkey
>  (Unfortunately, the PKS-type keyservers do not work with 
> multiple sub-keys)
> 
> -----Begin Obligatory Humorous 
> Quote----------------------------------------
> geep!
> -----End Obligatory Humorous 
> Quote------------------------------------------
> 

Re: [linux-lvm] LVM problems

[Ed Tomlinson]

On Tuesday 19 June 2001 17:19, AJ Lewis wrote:
> On Tue, Jun 19, 2001 at 02:28:05PM -0500, Gonyou, Austin wrote:
> > Why in the hell is this NOT in the source tree by default. This has
> > really got be boggled. I've seen tons of others have this proble, I've
> > had this problem, and still it doesn't seem to get itself into the tree.
> > Is this because it is a temporary problem or something?
>
> It *is* in the source tree by default.  It is in the CVS.  It is not in
> LVM 0.9.1 Beta7 because LVM 0.9.1 Beta7 was released before linux 2.4.4,
> which is when the problem surfaced.  We have not had a release since then,
> so it is not in the latest release.
>
> You can now grab the patch and apply it to beta7, which fixes the problem,
> or you can use the CVS repository.  I really don't know what else you
> expect us to do.

Actually getting the up-to-date lvm in the kernel would be nice.  Last time
I asked 2.4.<x>-ac<y> was about half way there.  What is happening?  Have the cvs
procedures been modified to enable producing Linus friendly patches?  When
can we expect a kernel with a current lvm?

Please read the above as just as a request for info.  LVM is working ok here.
Its just a bit of a pita to have to patch everything every time I rebuild a
tree...

TIA,
Ed Tomlinson <tomlins@cam.org>

Re: [linux-lvm] LVM problems

[Paul Jakma]

On Tue, 19 Jun 2001, AJ Lewis wrote:

> or you can use the CVS repository.  I really don't know what else you expect
> us to do.

make releases on a more timely basis?

>
> Regards,
>

-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org
PGP5 key: http://www.clubi.ie/jakma/publickey.txt
-------------------------------------------
Fortune:
He:	Let's end it all, bequeathin' our brains to science.
She:	What?!?  Science got enough trouble with their OWN brains.
		-- Walt Kelly

Re: [linux-lvm] LVM problems

[Heinz J. Mauelshagen]

On Tue, Jun 19, 2001 at 09:11:23PM -0400, Ed Tomlinson wrote:
> On Tuesday 19 June 2001 17:19, AJ Lewis wrote:
> > On Tue, Jun 19, 2001 at 02:28:05PM -0500, Gonyou, Austin wrote:
> > > Why in the hell is this NOT in the source tree by default. This has
> > > really got be boggled. I've seen tons of others have this proble, I've
> > > had this problem, and still it doesn't seem to get itself into the tree.
> > > Is this because it is a temporary problem or something?
> >
> > It *is* in the source tree by default.  It is in the CVS.  It is not in
> > LVM 0.9.1 Beta7 because LVM 0.9.1 Beta7 was released before linux 2.4.4,
> > which is when the problem surfaced.  We have not had a release since then,
> > so it is not in the latest release.
> >
> > You can now grab the patch and apply it to beta7, which fixes the problem,
> > or you can use the CVS repository.  I really don't know what else you
> > expect us to do.
> 
> Actually getting the up-to-date lvm in the kernel would be nice.  Last time
> I asked 2.4.<x>-ac<y> was about half way there.  What is happening?  Have the cvs
> procedures been modified to enable producing Linus friendly patches?  When
> can we expect a kernel with a current lvm?
> 
> Please read the above as just as a request for info.  LVM is working ok here.
> Its just a bit of a pita to have to patch everything every time I rebuild a
> tree...

Ed,
Linus *never* answered when we send hom patches even though I've send them
multiple times.
We are working together with Alan Cox since weeks to get his -ac tree updated.

Once he has it in he will push it to Linus.
Hopefully small changes in the future will make it in easier (sigh).

Regards,
Heinz    -- The LVM Guy --

> 
> TIA,
> Ed Tomlinson <tomlins@cam.org>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

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

Re: [linux-lvm] LVM problems

[Paul Jakma]

On Wed, 20 Jun 2001, Heinz J. Mauelshagen wrote:

> Ed,

> Linus *never* answered when we send hom patches even though I've
> send them multiple times.

and linus has said many many times on l-k: he gets loads and loads of
mail, he reads it with his finger on the D key, if you hear nothing
from him, keep sending.

also, you can almost take it as given that he won't look at anything
but emails that contain an inline diff (unified format) that tackles
one specific problem/update. URL or mime attachment -> deleted.

> We are working together with Alan Cox since weeks to get his -ac
> tree updated.
>
> Once he has it in he will push it to Linus.  Hopefully small
> changes in the future will make it in easier (sigh).

hopefully so and look forward to it.

>
> Regards,
> Heinz    -- The LVM Guy --

again, just like Ed, i have to say that i'm not bitching.. i think
LVM is just about the best thing since sliced bread - truly my
favourite linux kernel feature. so all i want to point out is that
LVM'd be just that -> <- much better if you guys kept LVM closely
in-sync with Linus. and best of all, for everyone ultimately, if
you'd ditch your private CVS tree altogether and just sync through
Linus very regularly..

(we don't care if sometimes you introduce bugs by sending patches
very frequently to Linus, cause we'll know that you just as regularly
send fixes.  but don't accumulate bug-fixes over many months in a cvs
tree and sit on them.)

but i do love LVM.

regards,
-- 
Paul Jakma	paul@clubi.ie	paul@jakma.org
PGP5 key: http://www.clubi.ie/jakma/publickey.txt
-------------------------------------------
Fortune:
That government is best which governs least.
		-- Henry David Thoreau, "Civil Disobedience"

Re: [linux-lvm] LVM problems

[Heinz J. Mauelshagen]

On Wed, Jun 20, 2001 at 02:15:30AM +0100, Paul Jakma wrote:
> On Tue, 19 Jun 2001, AJ Lewis wrote:
> 
> > or you can use the CVS repository.  I really don't know what else you expect
> > us to do.
> 
> make releases on a more timely basis?

Please calm down folks!

If you had followed the thread here you had seen that people recommended
to wait with 1.0 till vanilla is updated.

We plan to release 1.0 on Friday when at least -ac will hopefully be up to date.

Thanks Alan! :-)

> 
> >
> > Regards,
> >
> 
> -- 
> Paul Jakma	paul@clubi.ie	paul@jakma.org
> PGP5 key: http://www.clubi.ie/jakma/publickey.txt
> -------------------------------------------
> Fortune:
> He:	Let's end it all, bequeathin' our brains to science.
> She:	What?!?  Science got enough trouble with their OWN brains.
> 		-- Walt Kelly
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] LVM problems

[Heinz J. Mauelshagen]

On Thu, Jun 21, 2001 at 01:58:32AM +0100, Paul Jakma wrote:
> On Wed, 20 Jun 2001, Heinz J. Mauelshagen wrote:
> 
> > Ed,
> 
> > Linus *never* answered when we send hom patches even though I've
> > send them multiple times.
> 
> and linus has said many many times on l-k: he gets loads and loads of
> mail, he reads it with his finger on the D key, if you hear nothing
> from him, keep sending.

Yes, we kept sending (sigh).
Thanks to Alan, we'll hopefully make it soon into vanilla.

> 
> also, you can almost take it as given that he won't look at anything
> but emails that contain an inline diff (unified format) that tackles
> one specific problem/update. URL or mime attachment -> deleted.

We never have send attachements.

> 
> > We are working together with Alan Cox since weeks to get his -ac
> > tree updated.
> >
> > Once he has it in he will push it to Linus.  Hopefully small
> > changes in the future will make it in easier (sigh).
> 
> hopefully so and look forward to it.

We too.

> 
> >
> > Regards,
> > Heinz    -- The LVM Guy --
> 
> again, just like Ed, i have to say that i'm not bitching.. i think
> LVM is just about the best thing since sliced bread - truly my
> favourite linux kernel feature.

Thanks :-)

> so all i want to point out is that
> LVM'd be just that -> <- much better if you guys kept LVM closely
> in-sync with Linus. and best of all, for everyone ultimately, if
> you'd ditch your private CVS tree altogether and just sync through
> Linus very regularly..

That's exactly what we want to conform to.
It just takes a hole lot of time (several weeks now) to feed it into -ac.

And believe me, Alan is *very* helpful here but he can't work on just LVM
integration for sure.

Once we've got -ac updated, we'll try setting up a cron job to feed in the
small patches we are going to send to Alan/Linus ;-))

> 
> (we don't care if sometimes you introduce bugs by sending patches
> very frequently to Linus, cause we'll know that you just as regularly
> send fixes.  but don't accumulate bug-fixes over many months in a cvs
> tree and sit on them.)

Accepted.

> 
> but i do love LVM.

We too ;-)

> 
> regards,
> -- 
> Paul Jakma	paul@clubi.ie	paul@jakma.org
> PGP5 key: http://www.clubi.ie/jakma/publickey.txt
> -------------------------------------------
> Fortune:
> That government is best which governs least.
> 		-- Henry David Thoreau, "Civil Disobedience"
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[linux-lvm]LVM Problems

[David Rohrer]

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

I had set up a Red Hat 9.0 Box with no xwindows on it just mainly the basic install.
The /boot, / , and swap are all on HDA....then on HDG and HDH I set up a LVM during the install.

After I filled the drives in the LVM with data I tried to add to more drives to it they were HDC and HDD.
 I'm not the best at this, so I was reading how on the interent...I first tried to just do vgextend and it would error, so i done a pvcreate for each drive and then done a vgextend then I rebooted, I never did a change. so now when it boots it errors out trying to mount the volume and I would have to go into maintenance and edit the fstab and comment out the volume so it will boot

This is what I get when I do a pvscan:
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/hdg1"  is associated to unknown VG "Volume00" (run vgscan)
pvscan -- inactive PV "/dev/hdh1"  is associated to unknown VG "Volume00" (run vgscan)
pvscan -- total: 2 [38.03 GB] / in use: 2 [38.03 GB] / in no VG: 0 [0]

And this is what I get from a vgscan:
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/hdg1"  is associated to unknown VG "Volume00" (run vgscan)
pvscan -- inactive PV "/dev/hdh1"  is associated to unknown VG "Volume00" (run vgscan)
pvscan -- total: 2 [38.03 GB] / in use: 2 [38.03 GB] / in no VG: 0 [0]


I can send you a vgscan -d if you like but it is quite long, I have data on the volume and would like to fix it, is there a way to fallback to how it was before I tried to add the other 2 hard drives? And if so how do I add the new ones properly?

Thank You
Dio
There are 3 types of people in the world
Those who can count
and thos who can't

[linux-lvm] LVM problems

[Kelly Harding]

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

Hi,

I've just brought my Debian Linux box back up after a power failure and 
now my LVM set up seems to be non-functional.

I'm not very clued up on LVM tbh, but it has worked so far fine for ages.

I get the following error if I try  to run 'vgchange -a y 3diskvolume:

device-mapper ioctl cmd 11 failed: Invalid argument
   _deps: task run failed for (254:0)
   Failed to add device (254:0) to dtree
   1 logical volume(s) in volume group "3diskvolume" now active

It obviously won't mount after that as mount tells me it can't find the 
superblock etc.

any ideas? is one of the discs dead?

Thanks,

Kelly

[-- Attachment #2: kelly.harding.vcf --]
[-- Type: text/x-vcard, Size: 149 bytes --]

begin:vcard
fn:Miss Kelly Harding
n:Harding;Kelly
adr:;;;;;;UK
email;internet:kelly.harding@ntlworld.com
x-mozilla-html:FALSE
version:2.1
end:vcard

Re: [linux-lvm] LVM problems

[Kelly Harding]

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

Hi again,

Forgot to add details:

PC: dual PII/350mhz (p/pro overdrive), 512mb ram, SCSI LVD 80mb/s.

The VG is across 3 36gb scsi drives attached to an adaptect 2940U2W card.

I'm running kernel version 2.4.27 (2.6 doesn't seem to like this system).

I noticed from the dmesg output the following:

device-mapper: one of name or uuid must be supplied, cmd(11)

This appears when the previously mentioned command is run.

I've no idea what this means or if it isa case of a re-install of the 
base system might fix this? maybe something with the
base system has gone a bit fubar?

any help or advice on this would be greatly appreciated.

If it comes ot it that I lose the data and have to format and star the 
LVM VG over again it won't be ideal but it won't
be losing anything vital either (just video files, etc).

Kelly

[-- Attachment #2: kelly.harding.vcf --]
[-- Type: text/x-vcard, Size: 149 bytes --]

begin:vcard
fn:Miss Kelly Harding
n:Harding;Kelly
adr:;;;;;;UK
email;internet:kelly.harding@ntlworld.com
x-mozilla-html:FALSE
version:2.1
end:vcard

Re: [linux-lvm] LVM problems

[Anil Kumar Sharma]

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

Recently I also suffered problems with LVM(2)

These are very basic things I presume U might have already done but just in
case if not ...

imho pl boot with rescue disk (or mode)
As a precaution select read-only mount of file system
if required chroot to /mnt/sysimage
# mount  ! look for lvm things specifically a word - mapper
# pvdisplay
# vgdisplay
# lvdisplay
# pvscan
# vgscan
# lvscan

thiese will tell status of lvm things
 Then check /etc/fstab (carefully)

U may then "very very carefully" use e2fsck or fsck [{("after dismounting
the volumes")}] as you may you deem fit.
"very very carefully"  means, as a minimum, first read both manpages, try
these commands in read-only mode + do not modify anything + verbose.

### use vgck with caution and also checkout /etc/lvm/lvm.conf

U may try in init 1 mode also but more caution requested.

good luck & Pl post if U get it right this way or anyway.

--
Anil Kumar Shrama

[-- Attachment #2: Type: text/html, Size: 1369 bytes --]

Re: [linux-lvm] LVM problems

[Alasdair G Kergon]

On Wed, Dec 07, 2005 at 01:47:49AM +0000, Kelly Harding wrote:
> I've just brought my Debian Linux box back up after a power failure and 
> now my LVM set up seems to be non-functional.
 
> device-mapper ioctl cmd 11 failed: Invalid argument
>   _deps: task run failed for (254:0)
>   Failed to add device (254:0) to dtree
>   1 logical volume(s) in volume group "3diskvolume" now active
 
This development version of LVM2 requires a 2.6 kernel - it relies
on patches added to 2.6 upstream about a year ago.

Either upgrade to a 2.6 kernel or downgrade your lvm2 & device-mapper 
packages.

It would be straightforward to backport the changes to 2.4 but
nobody's done it yet.  Patches welcome!

  ftp://sources.redhat.com/pub/dm/patches/2.6-unstable/2.6.9-rc3/2.6.9-rc3-udm1/00004.patch

Alasdair
-- 
agk@redhat.com