[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] Re: upgrade from kernel 2.4 to 2.6



On Wed, Feb 25, 2004 at 08:36:31PM +0100, Luca Berra wrote:
| On Tue, Feb 24, 2004 at 08:49:50PM -0500, Derrick 'dman' Hudson wrote:
| >On Tue, Feb 24, 2004 at 11:25:22PM +0100, Luca Berra wrote:
| >| look in /etc/lvm/lvm.conf
| >| there is a log section, you can make lvm log to a different file, so
| >| you can save and post logs from lvm activation commands.
| >
| >Ok, I found that.
| >
| >Here is the log file, in its entirety :
| >
| >----
| >toollib.c:298 vgscan  No volume groups found
| >----
| >
| >I did set verbosity=3 because the comments in lvm.conf said that is
| >the highest verbosity.
| try changing other parameters in the log {} section, eg 'level'

Ah, finally I find some real information in the log!  Thanks for your
patience.

---- booting with kernel 2.6.3
filters/filter-composite.c:22 vgscan  Using /dev/hdb
device/dev-io.c:315 vgscan  Opened /dev/hdb
label/label.c:174 vgscan  /dev/hdb: No label detected
device/dev-io.c:339 vgscan  Closed /dev/hdb
label/label.c:266 vgscan  <backtrace>
filters/filter-composite.c:22 vgscan  Using /dev/hdb1
device/dev-io.c:315 vgscan  Opened /dev/hdb1
label/label.c:174 vgscan  /dev/hdb1: No label detected
device/dev-io.c:339 vgscan  Closed /dev/hdb1
label/label.c:266 vgscan  <backtrace>
toollib.c:298 vgscan  No volume groups found
filters/filter-persistent.c:170 vgscan  Dumping persistent device cache to /etc/lvm/.cache
----

The label wasn't found.  I guess that's a good enough reason to not
find the vg.

---- kernel 2.4.23
filters/filter-composite.c:22 vgscan  Using /dev/hdb
device/dev-io.c:315 vgscan  Opened /dev/hdb
label/label.c:174 vgscan  /dev/hdb: No label detected
device/dev-io.c:339 vgscan  Closed /dev/hdb
label/label.c:266 vgscan  <backtrace>
filters/filter-composite.c:22 vgscan  Using /dev/hdb1
device/dev-io.c:315 vgscan  Opened /dev/hdb1
label/label.c:156 vgscan  /dev/hdb1: lvm2 label detected
device/dev-io.c:339 vgscan  Closed /dev/hdb1
device/dev-io.c:315 vgscan  Opened /dev/hdb1
device/dev-io.c:339 vgscan  Closed /dev/hdb1
filters/filter-persistent.c:209 vgscan  /dev/initrd: Skipping (cached)
locking/file_locking.c:154 vgscan  Locking /var/lock/lvm/V_MaxtorDisk RB
toollib.c:309 vgscan  Finding volume group "MaxtorDisk"
device/dev-io.c:315 vgscan  Opened /dev/hdb1
label/label.c:156 vgscan  /dev/hdb1: lvm2 label detected
format_text/format-text.c:279 vgscan  Read MaxtorDisk metadata (1) from /dev/hdb1 at 2560 size 1469
vgscan.c:41 vgscan  Found volume group "MaxtorDisk" using metadata type lvm2
locking/file_locking.c:51 vgscan  Unlocking /var/lock/lvm/V_MaxtorDisk
device/dev-io.c:339 vgscan  Closed /dev/hdb1
filters/filter-persistent.c:170 vgscan  Dumping persistent device cache to /etc/lvm/.cache
----

The second log continues to find the lvs and works there.


Any ideas as to why it doesn't find the lvm label with kernel 2.6?
What should I do to try correcting it?

TIA,
-D

-- 
Pride only breeds quarrels,
but wisdom is found in those who take advice.
        Proverbs 13:10
 
www: http://dman13.dyndns.org/~dman/            jabber: dman dman13 dyndns org

Attachment: signature.asc
Description: Digital signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]