[gentoo-user] LVM boot problem

[gentoo-user] LVM boot problem

[Fredrik Tolf]

Hi list!

I'm having a bit of a problem with LVM2 on Gentoo. See, I have a
computer with a couple of hard drives in an LVM, and when it boots, I
can see it loading the driver modules for the controller cards properly
(I've added them to /etc/modules.autoload.d), but then when it comes to
initializing the LVM, it complains that it cannot find all the PVs to
initialize the VG. In fact, it complains about _all_ the PVs, as though
it found none.

Later, when the system is booted, I can log in as root and just run
"vgchange -ay" to get the VG up. Note that I don't have to run pvscan
first, which I'm assuming has to mean that it has somehow managed to
find the PVs somewhere in the meantime.

This problem is quite annoying, since it means that I have to restart
NFS and boot the system without the network cable plugged in (if it was,
the NFS clients would try to reconnect and get handles to the wrong
filesystem, which makes them mark the mount points as stale). Does
anyone have any idea what could cause it?

Thanks for your time!

Fredrik Tolf


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[John Jolet]

On Apr 6, 2006, at 11:44 AM, Fredrik Tolf wrote:

> Hi list!
>
> I'm having a bit of a problem with LVM2 on Gentoo. See, I have a
> computer with a couple of hard drives in an LVM, and when it boots, I
> can see it loading the driver modules for the controller cards  
> properly
> (I've added them to /etc/modules.autoload.d), but then when it  
> comes to
> initializing the LVM, it complains that it cannot find all the PVs to
> initialize the VG. In fact, it complains about _all_ the PVs, as  
> though
> it found none.
>
> Later, when the system is booted, I can log in as root and just run
> "vgchange -ay" to get the VG up. Note that I don't have to run pvscan
> first, which I'm assuming has to mean that it has somehow managed to
> find the PVs somewhere in the meantime.
>
> This problem is quite annoying, since it means that I have to restart
> NFS and boot the system without the network cable plugged in (if it  
> was,
> the NFS clients would try to reconnect and get handles to the wrong
> filesystem, which makes them mark the mount points as stale). Does
> anyone have any idea what could cause it?
>
> Thanks for your time!
>
> Fredrik Tolf
>
sounds like you're using device mapper as a module...compile it into  
the kernel.  module loading happens too late

>
> -- 
> gentoo-user@gentoo.org mailing list
>

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Fredrik Tolf]

On Thu, 2006-04-06 at 11:51 -0500, John Jolet wrote:
> sounds like you're using device mapper as a module...compile it into  
> the kernel.  module loading happens too late

Thanks for your reply, but I seriously doubt that to be the problem,
since /etc/rcscripts/addons/lvm-start explicitly contains the following
code:

        if [[ -e /proc/modules ]] && \
           ! grep -qs 'device-mapper' /proc/{devices,misc}
        then
                modprobe dm-mod &>/dev/null
        fi

Also, if the dm module wasn't loaded, I think that is what the LVM tools
would complain at, not at not finding the PVs, right?

Fredrik Tolf


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[John Jolet]

On Apr 6, 2006, at 12:03 PM, Fredrik Tolf wrote:

> On Thu, 2006-04-06 at 11:51 -0500, John Jolet wrote:
>> sounds like you're using device mapper as a module...compile it into
>> the kernel.  module loading happens too late
>
> Thanks for your reply, but I seriously doubt that to be the problem,
> since /etc/rcscripts/addons/lvm-start explicitly contains the  
> following
> code:
>
>         if [[ -e /proc/modules ]] && \
>            ! grep -qs 'device-mapper' /proc/{devices,misc}
>         then
>                 modprobe dm-mod &>/dev/null
>         fi
>
> Also, if the dm module wasn't loaded, I think that is what the LVM  
> tools
> would complain at, not at not finding the PVs, right?
>
> Fredrik Tolf

well, i've not had this problem, so i'm speculating...but if for  
whatever reason the dm code isn't resident, it would, in fact,  
complain about not being able to find pvs...pvcreate is the first  
step to creating a volume group.  i can't recall right now what  
happens if you try to run pvcreate without the dm extensions loaded.   
I did do that once apon a time.  maybe it let me do that, but died on  
the lv creation.  modprobe will fail on my system, because i always  
compile that into the kernel....but i can't say at what stage of the  
boot process lvm-start gets called.  i'm probably way off base....but  
if the /etc/rcscripts/addons/lvm-start script resides on an lv, or  
calls a binary that's say in /usr, which on my system is on an lv, it  
would naturally fail at that point....
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Alexander Skwar]

John Jolet wrote:

> sounds like you're using device mapper as a module...compile it into  
> the kernel.  module loading happens too late

If so, then this is not a general problem. I've also got
dm as a module and everything works fine.

Alexander Skwar
-- 
Would you people stop playing these stupid games?!?!?!!!!
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Richard Fish]

On 4/6/06, Fredrik Tolf <fredrik@dolda2000.com> wrote:
> Hi list!
>
> I'm having a bit of a problem with LVM2 on Gentoo.

Can you please the output of:

1. dmesg

2. grep -v -e "^ *#.*$" -e "^ *$" /etc/lvm/lvm.conf

3. grep -v -e "^ *#.*$" -e "^ *$" /etc/modules.autoload.d/kerrnel-2.6

4. lsmod

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Fredrik Tolf]

On Thu, 2006-04-06 at 10:09 -0700, Richard Fish wrote:
> On 4/6/06, Fredrik Tolf <fredrik@dolda2000.com> wrote:
> > Hi list!
> >
> > I'm having a bit of a problem with LVM2 on Gentoo.

Actually, it worked now that I just rebooted it! I noticed that the time
it took to load the modules was longer than usual (I just added another
controller card, so I'm guessing that's why), so I'm beginning to
suspect that it's just a race condition. Could it be that the kernel is
scanning for partitions in a background thread, so that the disks simply
haven't finished scanning by the time the LVM scans for PVs?

I'll give you the data you requested anyway, though. Please tell me if
something is strange.

Fredrik Tolf

--

(dmesg output moved to the end of the mail)

Bonus data:
# pvs
  PV         VG   Fmt  Attr PSize   PFree 
  /dev/hde1  vg1  lvm2 a-   111.79G     0 
  /dev/hdf1  vg1  lvm2 a-   111.79G     0 
  /dev/hdg1  vg1  lvm2 a-   111.79G     0 
  /dev/hdh1  vg1  lvm2 a-   111.79G 60.68G
  /dev/sdb1  vg1  lvm2 a-   279.46G     0 
  /dev/sdc1  vg1  lvm2 a-   279.46G     0 

> 2. grep -v -e "^ *#.*$" -e "^ *$" /etc/lvm/lvm.conf

devices {
    dir = "/dev"
    scan = [ "/dev" ]
    filter = [ "a/.*/" ]
    cache = "/etc/lvm/.cache"
    write_cache_state = 1
    sysfs_scan = 1
    md_component_detection = 1
}
log {
    verbose = 0
    syslog = 1
    overwrite = 0
    level = 0
    indent = 1
    command_names = 0
    prefix = "  "
}
backup {
    backup = 1
    backup_dir = "/etc/lvm/backup"
    archive = 1
    archive_dir = "/etc/lvm/archive"
    retain_min = 10
    retain_days = 30
}
shell {
    history_size = 100
}
global {
    umask = 077
    test = 0
    activation = 1
    proc = "/proc"
    locking_type = 1
    locking_dir = "/var/lock/lvm"
}
activation {
    missing_stripe_filler = "/dev/ioerror"
    mirror_region_size = 512
    reserved_stack = 256
    reserved_memory = 8192
    process_priority = -18
}

> 3. grep -v -e "^ *#.*$" -e "^ *$" /etc/modules.autoload.d/kerrnel-2.6

pcspkr
pdc202xx_new           <-- This is for my P-ATA controller card
sata_sil               <-- This is for my two S-ATA controller cards
sd_mod
rpcsec_gss_krb5

> 4. lsmod

Module                  Size  Used by
ehci_hcd               30344  0 
psmouse                35972  0 
parport_pc             25060  0 
parport                32360  1 parport_pc
floppy                 57956  0 
tulip                  47584  0 
crc32                   3808  1 tulip
i2c_piix4               7568  0 
i2c_core               17168  1 i2c_piix4
uhci_hcd               30928  0 
intel_agp              20412  1 
agpgart                29160  1 intel_agp
usbcore               117188  3 ehci_hcd,uhci_hcd
xfs                   606840  2 
reiserfs              259600  1 
nfsd                  233700  17 
exportfs                5088  2 xfs,nfsd
lockd                  62280  2 nfsd
nfs_acl                 2816  1 nfsd
dm_mod                 52472  4 
rpcsec_gss_krb5         8072  0 
auth_rpcgss            38496  3 rpcsec_gss_krb5
sunrpc                136892  15
nfsd,lockd,nfs_acl,rpcsec_gss_krb5,auth_rpcgss
sd_mod                 15056  4 
sata_sil                6468  2 
libata                 55084  1 sata_sil
scsi_mod               87240  2 sd_mod,libata
pdc202xx_new            7872  0 [permanent]
pcspkr                  1476  0 

> 1. dmesg

Linux version 2.6.15-gentoo-r1 (root@pc5) (gcc version 3.4.4 (Gentoo
3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #1 PREEMPT Mon Feb 27 02:00:44 CET
2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
 BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e6c00 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000040fd800 (usable)
 BIOS-e820: 00000000040fd800 - 00000000040ff800 (ACPI data)
 BIOS-e820: 00000000040ff800 - 00000000040ffc00 (ACPI NVS)
 BIOS-e820: 00000000040ffc00 - 0000000010000000 (usable)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
256MB LOWMEM available.
On node 0 totalpages: 65536
  DMA zone: 4096 pages, LIFO batch:0
  DMA32 zone: 0 pages, LIFO batch:0
  Normal zone: 61440 pages, LIFO batch:15
  HighMem zone: 0 pages, LIFO batch:0
DMI 2.1 present.
ACPI: RSDP (v000 PTLTD                                 ) @ 0x000f6bb0
ACPI: RSDT (v001 PTLTD    RSDT   0x00000001 PTL  0x01000000) @
0x040fdbcb
ACPI: FADT (v001 DELL   KUBLAI   0x20001013 PTL  0x000f4240) @
0x040ff78c
ACPI: DSDT (v001  Intel  S2440BX 0x00000001 MSFT 0x01000004) @
0x00000000
Allocating PCI resources starting at 20000000 (gap: 10000000:eff80000)
Built 1 zonelists
Kernel command line: ro root=/dev/hda2
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01201000)
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 498.920 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 255824k/262144k available (2254k kernel code, 5720k reserved,
601k data, 172k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Calibrating delay using timer specific routine.. 999.22 BogoMIPS
(lpj=1998453)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000
00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel Pentium III (Katmai) stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
ACPI: setting ELCR to 0200 (from 0e08)
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfd993, last bus=1
PCI: Using configuration type 1
ACPI: Subsystem revision 20050902
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI quirk: region 8000-803f claimed by PIIX4 ACPI
PCI quirk: region 7000-700f claimed by PIIX4 SMB
Boot video device is 0000:00:0d.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: Power Resource [PFAN] (on)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 11 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a
report
pnp: 00:00: ioport range 0x7000-0x700f has been reserved
pnp: 00:00: ioport range 0x8000-0x803f could not be reserved
PCI: Bridge: 0000:00:01.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
Machine check exception polling timer started.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Limiting direct PCI/PCI transfers.
ACPI: Power Button (FF) [PWRF]
ACPI: Fan [FAN1] (on)
Using specific hotkey driver
ACPI: CPU0 (power states: C1[C1] C2[C2])
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MICE] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
mice: PS/2 mouse device common for all mice
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1000-0x1007, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
input: AT Translated Set 2 keyboard as /class/input/input0
hda: ST340810A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63,
UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
Using IPI Shortcut mode
ACPI wakeup devices: 
PCI0 USB0 UAR1  KBC MICE 
ACPI: (supports S0 S1 S5)
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: hda2: orphan cleanup on readonly fs
kjournald starting.  Commit interval 5 seconds
ext3_orphan_cleanup: deleting unreferenced inode 3973543
ext3_orphan_cleanup: deleting unreferenced inode 3973542
ext3_orphan_cleanup: deleting unreferenced inode 3973541
EXT3-fs: hda2: 3 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 172k freed
Adding 506008k swap on /dev/hda1.  Priority:-1 extents:1 across:506008k
EXT3 FS on hda2, internal journal
input: PC Speaker as /class/input/input1
PDC20268: IDE controller at PCI slot 0000:00:0e.0
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKB] -> GSI 10 (level,
low) -> IRQ 10
PDC20268: chipset revision 2
PDC20268: ROM enabled at 0x20130000
PDC20268: 100% native mode on irq 10
    ide2: BM-DMA at 0x1010-0x1017, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x1018-0x101f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: WDC WD1200JB-00DUA3, ATA DISK drive
hdf: WDC WD1200JB-00DUA3, ATA DISK drive
ide2 at 0x1050-0x1057,0x1046 on irq 10
hde: max request size: 1024KiB
hde: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
hde: cache flushes supported
 hde: hde1
hdf: max request size: 1024KiB
hdf: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
hdf: cache flushes supported
 hdf: hdf1
Probing IDE interface ide3...
hdg: WDC WD1200JB-00DUA0, ATA DISK drive
hdh: WDC WD1200JB-00EVA0, ATA DISK drive
ide3 at 0x1048-0x104f,0x1042 on irq 10
hdg: max request size: 1024KiB
hdg: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
hdg: cache flushes supported
 hdg: hdg1
hdh: max request size: 1024KiB
hdh: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63,
UDMA(100)
hdh: cache flushes supported
 hdh: hdh1
SCSI subsystem initialized
libata version 1.20 loaded.
sata_sil 0000:00:0f.0: version 0.9
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKC] -> GSI 3 (level, low)
-> IRQ 3
ata1: SATA max UDMA/100 cmd 0xD084A080 ctl 0xD084A08A bmdma 0xD084A000
irq 3
ata2: SATA max UDMA/100 cmd 0xD084A0C0 ctl 0xD084A0CA bmdma 0xD084A008
irq 3
ata3: SATA max UDMA/100 cmd 0xD084A280 ctl 0xD084A28A bmdma 0xD084A200
irq 3
ata4: SATA max UDMA/100 cmd 0xD084A2C0 ctl 0xD084A2CA bmdma 0xD084A208
irq 3
ata1: dev 0 cfg 49:2f00 82:346b 83:7f61 84:4003 85:3469 86:3c41 87:4003
88:207f
ata1: dev 0 ATA-6, max UDMA/133, 390721968 sectors: LBA48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
ata3: no device found (phy stat 00000000)
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
  Vendor: ATA       Model: WDC WD2000JD-00H  Rev: 08.0
  Type:   Direct-Access                      ANSI SCSI revision: 05
ACPI: PCI Interrupt 0000:00:11.0[A] -> Link [LNKC] -> GSI 3 (level, low)
-> IRQ 3
ata5: SATA max UDMA/100 cmd 0xD0854880 ctl 0xD085488A bmdma 0xD0854800
irq 3
ata6: SATA max UDMA/100 cmd 0xD08548C0 ctl 0xD08548CA bmdma 0xD0854808
irq 3
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
SCSI device sda: drive cache: write back
 sda: sda1
sd 0:0:0:0: Attached scsi disk sda
ata5: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023
88:207f
ata5: dev 0 ATA-7, max UDMA/133, 586072368 sectors: LBA48
ata5: dev 0 configured for UDMA/100
scsi4 : sata_sil
ata6: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023
88:207f
ata6: dev 0 ATA-7, max UDMA/133, 586072368 sectors: LBA48
ata6: dev 0 configured for UDMA/100
scsi5 : sata_sil
  Vendor: ATA       Model: ST3300622AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdb: 586072368 512-byte hdwr sectors (300069 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 586072368 512-byte hdwr sectors (300069 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1
sd 4:0:0:0: Attached scsi disk sdb
  Vendor: ATA       Model: ST3300622AS       Rev: 3.AA
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdc: 586072368 512-byte hdwr sectors (300069 MB)
SCSI device sdc: drive cache: write back
SCSI device sdc: 586072368 512-byte hdwr sectors (300069 MB)
SCSI device sdc: drive cache: write back
 sdc: sdc1
sd 5:0:0:0: Attached scsi disk sdc
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
ReiserFS: dm-2: found reiserfs format "3.6" with standard journal
ReiserFS: dm-2: using ordered data mode
ReiserFS: dm-2: journal params: device dm-2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: dm-2: checking transaction log (dm-2)
ReiserFS: dm-2: Using r5 hash to sort names
SGI XFS with ACLs, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem dm-0
Ending clean XFS mount for filesystem: dm-0
XFS mounting filesystem dm-1
Ending clean XFS mount for filesystem: dm-1
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 64M @ 0xf8000000
USB Universal Host Controller Interface driver v2.3
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
PCI: setting IRQ 9 as level-triggered
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 9 (level, low)
-> IRQ 9
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 9, io base 0x00001020
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
piix4_smbus 0000:00:07.3: Found 0000:00:07.3 device
piix4_smbus 0000:00:07.3: Host SMBus controller not enabled!
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Enabling device 0000:00:10.0 (0114 -> 0117)
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKD] -> GSI 9 (level, low)
-> IRQ 9
tulip0:  MII transceiver #1 config 3100 status 7869 advertising 05e1.
eth0: ADMtek Comet rev 17 at d086a400, 00:08:A1:55:AA:C7, IRQ 9.
FDC 0 is a post-1991 82077
pnp: Device 00:08 activated.
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,EPP]
0000:00:10.0: tulip_stop_rxtx() failed
eth0: Setting full-duplex based on MII#1 link partner capability of
45e1.
process `named' is using obsolete setsockopt SO_BSDCOMPAT
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
directory
NFSD: starting 90-second grace period


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Richard Fish]

On 4/6/06, Fredrik Tolf <fredrik@dolda2000.com> wrote:
> I'll give you the data you requested anyway, though. Please tell me if
> something is strange.

Actually, I forgot a question, that is "what version of baselayout are
you using?".

There are 2 possible race conditions that I see in your current setup:

1. As you mention, I believe the detection of disks and partitions
happens asynchronously after the module is loaded.  I haven't checked
the kernel source to be sure however.  Since these volumes are on
different buses than your root filesystem, loads of modules (dm_mod
for example) or the programs (lvm2), are not going to block waiting
for the IOs on these buses to complete.  Still, the detection happens
pretty quick, and I'm not convinced this is the problem.

2. The second case for a race condition is with udev.  Since each disk
and partition detected is going to generate a hotplug event to udev,
and again these events are handled asynchronously to anything else on
the system, there could be a small delay between the detection of the
device and when the node actually appears in /dev.  The mechanism used
for the kernel and udev to communicate varies depending upon the
kernel and udev version, so one kernel may exhibit this problem while
another would not.

I am assuming at this point that you are running the stable
baselayout, 1.11.14-r6.  Because with the current ~x86 baselayout, I
don't see how your setup could work at all.  The call to start_volumes
has been moved from checkfs to the /sbin/rc script, right after udev
is started, but before the critical boot services are run (e.g,
modules).

I really think the right thing to do would be to recompile your
kerrnel and build the bus and sd_mod drivers into your kernel.  This
should ensure that all of the drives and partitions are detected
before the /sbin/rc script runs, and the device nodes will be created
when udev starts.

If you are reallly against building those into your kerrnel, I would
make a /etc/modules.d/lvm file that contains:

install dm_mod /sbin/modprobe sd_mod pdc202xx_new sata_sil; \
    /sbin/modprobe --ignore-install dm_mod; \
    /bin/sleep 0.2

Then run modules-update to recreate /etc/modules.conf.  This will
cause those modules to be loaded before dm_mod, give some time for the
devices to be detected and nodes to be created, and ensure that your
system survives a baselayout change.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Boyd Stephen Smith Jr.]

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

On Thursday 06 April 2006 11:44, Fredrik Tolf <fredrik@dolda2000.com> wrote 
about '[gentoo-user] LVM boot problem':
> I'm having a bit of a problem with LVM2 on Gentoo. See, I have a
> computer with a couple of hard drives in an LVM, and when it boots, I
> can see it loading the driver modules for the controller cards properly
> (I've added them to /etc/modules.autoload.d), but then when it comes to
> initializing the LVM, it complains that it cannot find all the PVs to
> initialize the VG. In fact, it complains about _all_ the PVs, as though
> it found none.

Is / on LVM?  Are you using an initrd / initramfs?  Does your early 
userspace start a /dev daemon?  Does your early userspace have a different 
lvm.conf then your final userspace?

> Later, when the system is booted, I can log in as root and just run
> "vgchange -ay" to get the VG up. Note that I don't have to run pvscan
> first, which I'm assuming has to mean that it has somehow managed to
> find the PVs somewhere in the meantime.

Are all of your pvs standard disks or disk partitions?  What modules are 
being loaded by the gentoo /etc/modules.autoload system?  What is your 
RC_VOLUME_ORDER in /etc/conf.d/rc?  Does 
your /lib/rcscripts/addons/lvm-start.sh 
contain "/sbin/vgscan --mknodes --ignorelockingfailure >/dev/null"?

> This problem is quite annoying, since it means that I have to restart
> NFS and boot the system without the network cable plugged in (if it was,
> the NFS clients would try to reconnect and get handles to the wrong
> filesystem, which makes them mark the mount points as stale).

You might investigate the mpt= /etc/exports option to only export 
filesystems that have been successfully mounted, at least temporarily.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

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

Re: [gentoo-user] LVM boot problem

[Fredrik Tolf]

On Thu, 2006-04-06 at 15:50 -0500, Boyd Stephen Smith Jr. wrote:
> On Thursday 06 April 2006 11:44, Fredrik Tolf <fredrik@dolda2000.com> wrote 
> about '[gentoo-user] LVM boot problem':
> > I'm having a bit of a problem with LVM2 on Gentoo. See, I have a
> > computer with a couple of hard drives in an LVM, and when it boots, I
> > can see it loading the driver modules for the controller cards properly
> > (I've added them to /etc/modules.autoload.d), but then when it comes to
> > initializing the LVM, it complains that it cannot find all the PVs to
> > initialize the VG. In fact, it complains about _all_ the PVs, as though
> > it found none.
> 
> Is / on LVM?  Are you using an initrd / initramfs?

Nope. Here's my fstab (minus pseudo-FS:s):
/dev/hda2         /       ext3         defaults,acl,user_xattr   0 1
/dev/hda1         none    swap         sw                        0 0
/dev/vg1/newhome  /home         reiserfs defaults,acl,user_xattr 0 2
/dev/vg1/dlwsroot /srv/dlwsroot xfs      defaults                0 3
/dev/vg1/site     /usr/site     xfs      defaults                0 4

> Does your early userspace start a /dev daemon?

If you mean udev, yes.

> Does your early userspace have a different lvm.conf then your final userspace?

Nope.

> > Later, when the system is booted, I can log in as root and just run
> > "vgchange -ay" to get the VG up. Note that I don't have to run pvscan
> > first, which I'm assuming has to mean that it has somehow managed to
> > find the PVs somewhere in the meantime.
> 
> Are all of your pvs standard disks or disk partitions?

Partitions. Here's the output of pvs:
  PV         VG   Fmt  Attr PSize   PFree  
  /dev/hde1  vg1  lvm2 a-   111.79G      0 
  /dev/hdf1  vg1  lvm2 a-   111.79G      0 
  /dev/hdg1  vg1  lvm2 a-   111.79G      0 
  /dev/hdh1  vg1  lvm2 a-   111.79G  60.68G
  /dev/sda1  vg1  lvm2 a-   186.30G 186.30G
  /dev/sdb1  vg1  lvm2 a-   279.46G      0 
  /dev/sdc1  vg1  lvm2 a-   279.46G      0 


> What modules are being loaded by the gentoo /etc/modules.autoload system?

pcspkr
pdc202xx_new
sata_sil
sd_mod
rpcsec_gss_krb5

> What is your RC_VOLUME_ORDER in /etc/conf.d/rc?

RC_VOLUME_ORDER="raid evms lvm dm"

> Does your /lib/rcscripts/addons/lvm-start.sh 
> contain "/sbin/vgscan --mknodes --ignorelockingfailure >/dev/null"?

Yep.

> > This problem is quite annoying, since it means that I have to restart
> > NFS and boot the system without the network cable plugged in (if it was,
> > the NFS clients would try to reconnect and get handles to the wrong
> > filesystem, which makes them mark the mount points as stale).
> 
> You might investigate the mpt= /etc/exports option to only export 
> filesystems that have been successfully mounted, at least temporarily.

Interesting. I'll definitely use that. For completeness, though, I
should mention that looking at the manpage, it seems to be named "mp"
rather than "mpt".

Thanks!

Fredrik Tolf


-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] LVM boot problem

[Mirco Bakker]

Hi

Two days ago, I changed my USE flags (added bzip2) and tried to emerge world with the update, deep and newuse options. Because the new UDEV Package conflicted with coldplug I unmerged coldplug first (which is obsolete I think?).
Today I rebooted for the first time since then. As the system came up a few error messages showed up, indicating that my ethernet interface was not found (probably module not loaded). Is there a connection to coldplug?

Anyway after that I thought it would be a good idea to update to the latest Kernel before fixing that Problem (2.6.18-gentoo-r3). I used genkernel to create a generic kernel, modules and initrd with lvm2 support (as my root device is on a lvm2 volume). Since then the system stopped booting completely.

The first problem was that the busybox mdev link was missing (therefor I created it manually). Now linuxrc (actually vgchange) claims, that there is no more space left on the device to create the device nodes for my lvm volumes. But dumpe2fs on the initrd reports, that I still have 45 free blocks and 44 free inodes. Shouldn't this be enough for 3 device nodes? Any ideas what could be wrong?

TIA, Mirco


-- 
"Ein Herz für Kinder" - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de
Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht!
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Mirco Bakker]

Hi

For the archives: Problems solved. The missing ethernet interface resulted from two missing links in /sbin (udev_run_devd, udev_run_hotplugd). I've created them now manually. I think they should get installed when emerging udev. A this point I have no idea why they were missing on my system (if someone has an idea please reply). Anyway it works fine again.

The boot problem originated from using an old genkernel.conf (and ignoring emerge!). Not yet tested but pretty obvious (I'm compiling the new kernel and initrd at the moment).

Regards, Manuel

-------- Original-Nachricht --------
Datum:  Wed, 06 Dec 2006 18:59:26 +0100
Von: "Mirco Bakker" <lister1@gmx.net>
An: gentoo-user@lists.gentoo.org
Betreff:  [gentoo-user] LVM boot problem

> Hi
> 
> Two days ago, I changed my USE flags (added bzip2) and tried to emerge
> world with the update, deep and newuse options. Because the new UDEV Package
> conflicted with coldplug I unmerged coldplug first (which is obsolete I
> think?).
> Today I rebooted for the first time since then. As the system came up a
> few error messages showed up, indicating that my ethernet interface was not
> found (probably module not loaded). Is there a connection to coldplug?
> 
> Anyway after that I thought it would be a good idea to update to the
> latest Kernel before fixing that Problem (2.6.18-gentoo-r3). I used genkernel to
> create a generic kernel, modules and initrd with lvm2 support (as my root
> device is on a lvm2 volume). Since then the system stopped booting
> completely.
> 
> The first problem was that the busybox mdev link was missing (therefor I
> created it manually). Now linuxrc (actually vgchange) claims, that there is
> no more space left on the device to create the device nodes for my lvm
> volumes. But dumpe2fs on the initrd reports, that I still have 45 free blocks
> and 44 free inodes. Shouldn't this be enough for 3 device nodes? Any ideas
> what could be wrong?
> 
> TIA, Mirco
> 
> 
> -- 
> "Ein Herz für Kinder" - Ihre Spende hilft! Aktion:
> www.deutschlandsegelt.de
> Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's
> Cup-Yacht!
> -- 
> gentoo-user@gentoo.org mailing list

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Richard Fish]

On 12/6/06, Mirco Bakker <lister1@gmx.net> wrote:
> Hi
>
> For the archives: Problems solved. The missing ethernet interface resulted from two missing links in /sbin (udev_run_devd, udev_run_hotplugd). I've created them now manually. I think they should get installed when emerging udev. A this point I have no idea why they were missing on my system (if someone has an idea please reply). Anyway it works fine again.

No, you should not have any udev utilities in /sbin now.  They now
live in /lib/udev.  In the udev rules files, you should not specify
any path for any utilities that you want to run (use PROGRAM="foo"
instead of PROGRAM="/path/foo").  Also rules files owned by udev (like
50-udev.rules) should show an update required when you run etc-update,
and you should accept the new file, rather than keeping any changes
you made.  You should only make changes to 10-local.rules.

Also, there might be some orphans in /etc/udev/rules.d.  You can find
these with "equery belongs /etc/udev.d/rules.d/<filename>".  Anything
that doesn't belong to a package (other than 10-local.rules, and
70-persistent-*.rules) could probably be removed.

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Richard Fish]

On 12/6/06, Richard Fish <bigfish@asmallpond.org> wrote:
> No, you should not have any udev utilities in /sbin now.

Bah. s/utilities/helpers/g
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] LVM boot problem

[Mick]

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

On Wednesday 06 December 2006 20:41, Mirco Bakker wrote:
> Hi
>
> For the archives: Problems solved. The missing ethernet interface resulted
> from two missing links in /sbin (udev_run_devd, udev_run_hotplugd). I've
> created them now manually. I think they should get installed when emerging
> udev. A this point I have no idea why they were missing on my system (if
> someone has an idea please reply). Anyway it works fine again.

Hmm, this is what I've got on my system:

# ls -la /sbin/udev*
-rwxr-xr-x 1 root root 40168 Dec  1 19:55 /sbin/udev
-rwxr-xr-x 1 root root  8548 Dec  1 19:55 /sbin/udevcontrol
-rwxr-xr-x 1 root root 50296 Dec  1 19:55 /sbin/udevd
-rwxr-xr-x 1 root root 14440 Dec  1 19:55 /sbin/udevsettle
-rwxr-xr-x 1 root root 43432 Dec  1 19:55 /sbin/udevstart
-rwxr-xr-x 1 root root 18568 Dec  1 19:55 /sbin/udevtrigger

The two you mention are here:

# ls -la /lib/udev/udev*
-rwxr-xr-x 1 root root 7468 Dec  1 19:55 /lib/udev/udev_run_devd
-rwxr-xr-x 1 root root 7272 Dec  1 19:55 /lib/udev/udev_run_hotplugd

No links - should there be any?
-- 
Regards,
Mick

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