Mike Fedyk <mfedyk@xxxxxxxxxxxxx> writes: > Nicolas.Kowalski@xxxxxxx wrote: >> Hello. >> On a server running 2.4.25, I have the two following errors in the >> kernel logfile: >> Unexpected dirty buffer encountered at do_get_write_access:618 >> (08:11 blocknr 920707) >> Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) >> > > It's probably a driver problem. > >> Should I worry about them (disk failure, filesystem damage) ? > > It's possible, depending on which driver is having trouble. Here is the SCSI adapter output: SCSI subsystem driver Revision: 1.00 Loading Adaptec I2O RAID: Version 2.4 Build 5 Detecting Adaptec I2O RAID controllers... sym0: <896> rev 0x5 on pci bus 5 device 5 function 0 irq 24 sym0: using 64 bit DMA addressing sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: SCSI BUS has been reset. sym1: <896> rev 0x5 on pci bus 5 device 5 function 1 irq 25 sym1: using 64 bit DMA addressing sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: SCSI BUS has been reset. scsi0 : sym-2.1.17a scsi1 : sym-2.1.17a blk: queue c1654418, I/O limit 1048575Mb (mask 0xffffffffff) Vendor: HP Model: 9.10GB C 68-BX02 Rev: BX02 Type: Direct-Access ANSI SCSI revision: 02 blk: queue c1654218, I/O limit 1048575Mb (mask 0xffffffffff) Vendor: HP Model: 9.10GB C 68-BX02 Rev: BX02 Type: Direct-Access ANSI SCSI revision: 02 blk: queue dfeb3e18, I/O limit 1048575Mb (mask 0xffffffffff) sym0:0:0: tagged command queuing enabled, command queue depth 16. sym0:1:0: tagged command queuing enabled, command queue depth 16. Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 > Did you run fsck? Not yes. It is planned for next reboot (touch /forcefsck), which will happen next monday. >> Thanks. >> As an addition what does the pair '08:11' means ? Is this the >> major/minor of the hard disk partition where the filesystem is located ? > > Yes, check /proc/partitions. Then, I am just more confused. This 08:11 pair does match anything... olan:~# cat /proc/partitions major minor #blocks name 8 0 8886762 sda 8 1 195568 sda1 8 2 976896 sda2 8 3 1952768 sda3 8 4 5761024 sda4 8 16 8886762 sdb 8 17 8886256 sdb1 Thanks for your reply. -- Nicolas _______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
