[Pacemaker] starting resources: Interrupted system call

[Bernd Schubert]

Never mind, seems to be fixed in 1.0.9

Thanks,
Bernd

On Thursday, July 01, 2010, Bernd Schubert wrote:
> Hi all,
> 
> there seems to be a new regression in pacemaker-1.0.8 (or cluster-glue
> or whatever, really difficult to differentiate the layers).
> 
> ul 01 15:04:37 phys-oss2 lustre_server[8571]: [8602]: INFO: Running start
> for /dev/mapper/ost_demofs_8 on /lustre/demofs/ost_8 Jul 01 15:04:38
> phys-oss2 lustre_server[8571]: [8620]: INFO: Running mount -t lustre 
> /dev/mapper/ost_demofs_8 /lustre/demofs/ost_8 Jul 01 15:04:41 phys-oss2
> cib: [8901]: info: write_cib_contents: Archived previous version as
> /var/lib/heartbeat/crm/cib-57.raw Jul 01 15:04:42 phys-oss2 cib: [8901]:
> info: write_cib_contents: Wrote version 0.638.0 of the CIB to disk
> (digest: 13003c55305a60f2178e455f50 9530df)
> Jul 01 15:04:43 phys-oss2 cib: [8901]: info: retrieveCib: Reading cluster
> configuration from: /var/lib/heartbeat/crm/cib.KkBEWh (digest: /var
> /lib/heartbeat/crm/cib.QRl46D)
> Jul 01 15:04:46 phys-oss2 cib: [8946]: info: write_cib_contents: Archived
> previous version as /var/lib/heartbeat/crm/cib-58.raw Jul 01 15:04:48
> phys-oss2 cib: [8946]: info: write_cib_contents: Wrote version 0.639.0 of
> the CIB to disk (digest: 0d88dd459c597542895265d5f8 bedb3a)
> Jul 01 15:04:49 phys-oss2 cib: [8946]: info: retrieveCib: Reading cluster
> configuration from: /var/lib/heartbeat/crm/cib.qsk62F (digest: /var
> /lib/heartbeat/crm/cib.dhAidm)
> Jul 01 15:04:50 phys-oss2 cib: [8948]: info: write_cib_contents: Archived
> previous version as /var/lib/heartbeat/crm/cib-59.raw Jul 01 15:04:51
> phys-oss2 cib: [8948]: info: write_cib_contents: Wrote version 0.640.0 of
> the CIB to disk (digest: 8103866a901b72c8ff77443eb5 d2ae0f)
> Jul 01 15:04:51 phys-oss2 cib: [8948]: info: retrieveCib: Reading cluster
> configuration from: /var/lib/heartbeat/crm/cib.6xOswj (digest: /var
> /lib/heartbeat/crm/cib.BHtHgd)
> Jul 01 15:04:52 phys-oss2 cib: [8950]: info: write_cib_contents: Archived
> previous version as /var/lib/heartbeat/crm/cib-60.raw Jul 01 15:04:53
> phys-oss2 cib: [8950]: info: write_cib_contents: Wrote version 0.641.0 of
> the CIB to disk (digest: dce9a7bf8b8d4f3fe53c6ca2ce399fb4)
> Jul 01 15:04:54 phys-oss2 cib: [8950]: info: retrieveCib: Reading cluster
> configuration from: /var/lib/heartbeat/crm/cib.VaA9y7 (digest:
> /var/lib/heartbeat/crm/cib.x5WXTb)
> Jul 01 15:04:54 phys-oss2 cib: [7987]: WARN: G_SIG_dispatch: Dispatch
> function for SIGCHLD was delayed 240 ms (> 100 ms) before being called
> (GSource: 0xef73700)
> Jul 01 15:04:54 phys-oss2 cib: [7987]: info: G_SIG_dispatch: started at
> 486502645 should have started at 486502621 Jul 01 15:04:55 phys-oss2 cib:
> [8951]: info: write_cib_contents: Archived previous version as
> /var/lib/heartbeat/crm/cib-61.raw Jul 01 15:04:56 phys-oss2 cib: [8951]:
> info: write_cib_contents: Wrote version 0.642.0 of the CIB to disk
> (digest: 72358cbb47103129ea2ec4db0ca09fa5)
> Jul 01 15:04:57 phys-oss2 cib: [8951]: info: retrieveCib: Reading cluster
> configuration from: /var/lib/heartbeat/crm/cib.AwzNsn (digest:
> /var/lib/heartbeat/crm/cib.U8PVzD)
> Jul 01 15:05:08 phys-oss2 lustre_server[8571]: [8957]: ERROR: cmd "mount -t
> lustre  /dev/mapper/ost_demofs_8 /lustre/demofs/ost_8" failed:
> mount.lustre: mount /dev/mapper/ost_demofs_8 at /lustre/demofs/ost_8
> failed: Interrupted system call Jul 01 15:05:09 phys-oss2 crmd: [7991]:
> info: process_lrm_event: LRM operation ost_demofs_8_start_0 (call=103,
> rc=1, cib-update=220, confirmed=true) unknown error
> 
> 
> Now the start timeout is set to 600s, so it I don't see why it should abort
> the mount command:
> 
> primitive ost_demofs_8 ocf:ddn:lustre_server \
>         params device="/dev/mapper/ost_demofs_8"
> directory="/lustre/demofs/ost_8" \ op monitor interval="120" timeout="600"
> \
>         op start interval="0" timeout="700" \
>         op stop interval="0" timeout="300" \
>         meta resource-stickiness="0" target-role="Started"
> is-managed="true"
> 
> 
> 
> Shall I open a bug entry and attach hb_report or is it a know issue?
> 
> 
> Thanks,
> Bernd