iscsi initiator and mounting lvm on startup

Sun Jan 28 20:45:46 UTC 2007

On Sun, 2007-01-28 at 19:09 +0100, Ambrogio wrote:
> Il giorno mer, 24/01/2007 alle 19.19 +0100, Sander Hoentjen ha scritto:
> > Thank you very much for taking the time to answer!
> > The machine is remote so I cannot see it when booting. Is there any way
> > to see the errors after startup?
> You can check with the dmesg command or reading the log.
> First /var/log/messages... and after some other log, but it depends.
> Normally the messages is enough
> 
Well that doesn't give me the Starting service  [ OK ] stuff, what I was
looking for. It does give me some kernel error:

Jan 28 21:19:10 storagevrt kernel: scsi4 : iSCSI Initiator over TCP/IP
Jan 28 21:19:10 storagevrt avahi-daemon[3299]: Service "SFTP File Transfer on storagevrt" (/services/sftp-ssh.service) successfully established.
Jan 28 21:19:12 storagevrt kernel: 
Jan 28 21:19:12 storagevrt kernel: ======================================================
Jan 28 21:19:12 storagevrt kernel: [ INFO: hard-safe -> hard-unsafe lock order detected ]
Jan 28 21:19:12 storagevrt kernel: 2.6.19-1.2914.fc7 #1
Jan 28 21:19:12 storagevrt kernel: ------------------------------------------------------
Jan 28 21:19:12 storagevrt kernel: iscsid/3369 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
Jan 28 21:19:12 storagevrt kernel:  (&session->lock){-+..}, at: [<f8aafbed>] iscsi_queuecommand+0x48/0x18e [libiscsi]
Jan 28 21:19:12 storagevrt kernel: 
Jan 28 21:19:12 storagevrt kernel: and this task is already holding:
Jan 28 21:19:12 storagevrt kernel:  (shost->host_lock){.+..}, at: [<f885fb72>] scsi_dispatch_cmd+0x1a0/0x2b0 [scsi_mod]
<SNIP>
Jan 28 21:19:13 storagevrt kernel:  [<c0478b73>] vfs_write+0xaf/0x163
Jan 28 21:19:13 storagevrt kernel:  [<c04791c1>] sys_write+0x3d/0x61
Jan 28 21:19:13 storagevrt kernel:  [<c0404058>] syscall_call+0x7/0xb
Jan 28 21:19:13 storagevrt kernel:  =======================
Jan 28 21:19:13 storagevrt kernel: scsi 4:0:0:0: Direct-Access     IFT      A12E-G2121-2     342D PQ: 0 ANSI: 3
Jan 28 21:19:13 storagevrt kernel: sdb : very big device. try to use READ CAPACITY(16).
Jan 28 21:19:13 storagevrt kernel: SCSI device sdb: 9762385920 512-byte hdwr sectors (4998342 MB)
Jan 28 21:19:13 storagevrt kernel: sdb: Write Protect is off
Jan 28 21:19:13 storagevrt kernel: SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 28 21:19:13 storagevrt kernel: sdb : very big device. try to use READ CAPACITY(16).
Jan 28 21:19:13 storagevrt kernel: SCSI device sdb: 9762385920 512-byte hdwr sectors (4998342 MB)
Jan 28 21:19:13 storagevrt kernel: sdb: Write Protect is off
Jan 28 21:19:13 storagevrt kernel: SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 28 21:19:13 storagevrt kernel:  sdb: unknown partition table
Jan 28 21:19:13 storagevrt kernel: sd 4:0:0:0: Attached scsi disk sdb
Jan 28 21:19:13 storagevrt kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Jan 28 21:19:28 storagevrt iscsid: recvpool leak: 8256 bytes
Jan 28 21:19:29 storagevrt smartd[3412]: smartd version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen 
Jan 28 21:19:29 storagevrt smartd[3412]: Home page is http://smartmontools.sourceforge.net/  
Jan 28 21:19:29 storagevrt smartd[3412]: Opened configuration file /etc/smartd.conf 
Jan 28 21:19:29 storagevrt smartd[3412]: Configuration file /etc/smartd.conf parsed. 
Jan 28 21:19:29 storagevrt smartd[3412]: Device: /dev/sda, opened 
Jan 28 21:19:29 storagevrt smartd[3412]: Device: /dev/sda, found in smartd database. 
Jan 28 21:19:29 storagevrt smartd[3412]: Device: /dev/sda, is SMART capable. Adding to "monitor" list. 
Jan 28 21:19:29 storagevrt smartd[3412]: Monitoring 1 ATA and 0 SCSI devices 
Jan 28 21:19:29 storagevrt smartd[3414]: smartd has fork()ed into background mode. New PID=3414. 
Jan 28 21:19:39 storagevrt iscsid: connection0:0 is operational after recovery (1 attempts)

Is this something I should report, and where? To the fedora kernel or upstream kernel?

then after the service netfs start:
Jan 28 21:39:03 storagevrt kernel: kjournald starting.  Commit interval 5 seconds
Jan 28 21:39:03 storagevrt kernel: EXT3 FS on dm-70, internal journal
Jan 28 21:39:03 storagevrt kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 28 21:39:03 storagevrt kernel: kjournald starting.  Commit interval 5 seconds
Jan 28 21:39:03 storagevrt kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 28 21:39:03 storagevrt kernel: EXT3 FS on dm-71, internal journal
Jan 28 21:39:03 storagevrt kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 28 21:39:03 storagevrt kernel: kjournald starting.  Commit interval 5 seconds
Jan 28 21:39:03 storagevrt kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 28 21:39:03 storagevrt kernel: EXT3 FS on dm-40, internal journal
Jan 28 21:39:03 storagevrt kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 28 21:39:03 storagevrt kernel: kjournald starting.  Commit interval 5 seconds
Jan 28 21:39:03 storagevrt kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 28 21:39:03 storagevrt kernel: EXT3 FS on dm-69, internal journal
Jan 28 21:39:03 storagevrt kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 28 21:39:03 storagevrt kernel: kjournald starting.  Commit interval 5 seconds
Jan 28 21:39:03 storagevrt kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Jan 28 21:39:03 storagevrt kernel: EXT3 FS on dm-42, internal journal
Jan 28 21:39:03 storagevrt kernel: EXT3-fs: mounted filesystem with ordered data mode.
etc.

> > 
> > # ls /etc/rc.d/rc3.d/
> > K02avahi-dnsconfd            K69rpcsvcgssd      K89netplugd         S05kudzu        S13iscsi       S25bluetooth  S55cups      S95anacron
> > K02dhcdbd                    K73ypbind          K89pand             S06cpuspeed     S13mcstrans    S25netfs      S55sshd      S95atd
> > K02NetworkManager            K74nscd            K89rdisc            S08ip6tables    S13portmap     S25pcscd      S58ntpd      S97yum-updatesd
> > K02NetworkManagerDispatcher  K80kdump           K91capi             S09isdn         S14nfslock     S26apmd       S60vsftpd    S98avahi-daemon
> > K05saslauthd                 K85mdmpd           K92iptables         S10network      S15mdmonitor   S26hidd       S80sendmail  S98haldaemon
> > K10psacct                    K87multipathd      K99microcode_ctl    S10restorecond  S18rpcidmapd   S28autofs     S85gpm       S99firstboot
> > K20nfs                       K88wpa_supplicant  K99readahead_later  S12syslog       S19rpcgssd     S44acpid      S85httpd     S99local
> > K24irda                      K89dund            S04readahead_early  S13irqbalance   S22messagebus  S55apf        S90crond     S99smartd
> > 
> > So If I understand correctly network goes up, then iscsi and then netfs.. That should be the right order I think. I hope you have some more suggestions.
> 
> This should be the right sequence.
> I don't understand what appens.
> Maybe something need a modules that can't be loaded at boot time,
> because you need to recreate the init ram disk (initrd).
> This can explain why you can use it after boot.
How can I check if this is needed?

> 
> What kind of partition are /boot and /?

/boot is primary ext3 partition (/dev/sda1)
/ is logical ext3 partition (/dev/sda5)

Thanks again,

Sander