Hi,
>> /var/log/kernel/warnings
>> ------------------------
>> Oct 27 09:19:12 smbserver kernel: xfs_force_shutdown(md(9,5),0x8)
>> called from line 1039 of file xfs_trans.c. Return address =
>> 0xe08ae312
>> Oct 27 09:19:12 smbserver kernel: Corruption of in-memory data
>> detected. Shutting down filesystem: md(9,5)
>> Oct 27 09:19:12 smbserver kernel: Please umount the filesystem, and
>> rectify the problem(s)
>>
>> /var/log/kernel/errors
>> ----------------------
>> Oct 27 10:36:44 smbserver kernel: Unknown bridge resource 2: assuming
>> transparent
>> Oct 27 10:36:44 smbserver kernel: PCI: Unable to handle 64-bit
>> address space for
>> Oct 27 10:36:44 smbserver kernel: PCI: Unable to handle 64-bit
>> address space for
>> Oct 27 10:36:44 smbserver kernel: Unknown bridge resource 2: assuming
>> transparent
>> Oct 27 10:36:44 smbserver kernel: PCI: Device 00:1f.1 not available
>> because of resource collisions
>
> Sounds a bit like IRQ sharing. You can try freeing up those by
> switching off things like serial and parallel ports.
I disabled USB, Serial (RS232) and have no cards plug to the PCI slots of
the system. The following is my /proc/interrupts. It does show anything
conclusive. The XFS partitions would disappear from Samba shares. If I tried
to unmount it, system says it is busy. May I ask how do I force XFS fsck
equivalent on XFS paritions? Is it safe?
CPU0 CPU1 CPU2 CPU3
0: 359126 0 0 0 IO-APIC-edge timer
1: 11 0 0 0 IO-APIC-edge keyboard
2: 0 0 0 0 XT-PIC cascade
8: 1 0 0 0 IO-APIC-edge rtc
12: 35 0 0 0 IO-APIC-edge PS/2 Mouse
15: 7 0 0 0 IO-APIC-edge ide1
30: 113223 0 0 0 IO-APIC-level eth1
31: 746889 0 0 0 IO-APIC-level eth0
49: 4134628 0 0 0 IO-APIC-level aic7xxx
50: 16 0 0 0 IO-APIC-level aic7xxx
NMI: 0 0 0 0
LOC: 358982 358980 358980 358980
ERR: 0
MIS: 0
Regards,
Norman
|