search for: check_interval

...kernel: aacraid: SCSI bus appears hung Jul 6 18:28:02 virt kernel: Calling adapter init Jul 6 18:28:41 virt kernel: IRQ 16/aacraid: IRQF_DISABLED is not guaranteed on shared IRQs Jul 6 18:28:41 virt kernel: Acquiring adapter information Jul 6 18:28:41 virt kernel: update_interval=30:00 check_interval=86400s Jul 6 18:32:05 virt kernel: aacraid: aac_fib_send: first asynchronous command timed out. Jul 6 18:32:05 virt kernel: Usually a result of a PCI interrupt routing problem; Jul 6 18:32:05 virt kernel: update mother board BIOS or consider utilizing one of Jul 6 18:32:05 virt kernel:...

Hi! I would like to know how well ext3/(ext2) will tolerate underlaying errors (I am planning to use loop-AES backed ext3 fs). So if there is 1024 bytes corruption of data what will be the worst case: - If this data belongs to some file, this part of data(file) has been lost? - If this data belongs to superblock, I have to repair ext3 and use another superblock? - If this data belongs to

> I guess we have to look at the conf files then, first these two: Thank you for the config file snippets. I can confirm mine were almost identical, so I've tweaked them so that they are now exactly the same as yours except for the "--require-membership-of=example\authorization_groupname" line in ntlm_auth. Unfortunately it's still erroring out: (7) mschap: Creating

Hi all, I have upgraded a test machine from OpenSuSE 11.1 to 11.2. I have found following bug: the server is a 2x quadcore intel box also 2x4=8cpu If you limit the dom0 cpu with dom0-cpus= [1-7]: - [xenwatch_cb] is running 100% cpu and makes var log entry every 65 sec BUG: soft lockup - CPU#X stuck for 61s! - xm commands not work - xend is dead if set dom0-cpus to 0 or 8: - everything looks