Your message dated Tue, 12 Dec 2006 11:36:47 +0000
with message-id <[EMAIL PROTECTED]>
and subject line lvm 1 removed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: lvm10
Version: 1.0.1rc3-1
Severity: normal

Hi

I show you my script, it should say everything:

--------
Script started on Mon Nov 26 10:13:19 2001
[EMAIL PROTECTED]:~# dmesg
[EMAIL PROTECTED]:~# fdisk -l /dev/hda

Disk /dev/hda: 255 heads, 63 sectors, 4111 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1         2     16033+  83  Linux
/dev/hda2             3       133   1052257+  83  Linux
/dev/hda3           134       150    136552+  82  Linux swap
/dev/hda4           151      4111  31816732+  8e  Linux LVM
[EMAIL PROTECTED]:~# pvcreate /dev/hda4
pvcreate -- physical volume "/dev/hda4" successfully created

[EMAIL PROTECTED]:~# dmesg
[EMAIL PROTECTED]:~# vgcreate mainvg /dev/hda4
vgcreate -- INFO: using default physical extent size 4.00 MB
vgcreate -- INFO: maximum logical volume size is 255.99 Gigabyte
vgcreate -- doing automatic backup of volume group "mainvg"
vgcreate -- volume group "mainvg" successfully created and activated

[EMAIL PROTECTED]:~# dmesg
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
[EMAIL PROTECTED]:~# exit
exit

Script done on Mon Nov 26 10:14:13 2001
--------

It could also be a kernel-problem (2.4.16-pre1), I don't know.

I also tested the stable version of lvm, but that doesn't work at all.
(invalid protocol or such ...)


Jochen

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux james 2.4.16-pre1 #1 Sun Nov 25 15:47:56 CET 2001 i586
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages lvm10 depends on:
ii  libc6                         2.2.4-3    GNU C Library: Shared libraries an
ii  lvm-common                    1.3        The Logical Volume Manager for Lin



--- End Message ---
--- Begin Message ---
lvm version 1 has been removed from Debian etch and unstable.
Please migrate to version 2 (package lvm2).  If the bug you reported
against lvm10 still exists in lvm2, please open a new bug or let me
know.  Thanks.
-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---

Reply via email to