chyba I/O

Začína to byť zaujímavé, práve dobehlo if=/dev/hda of=/dev/null ale bez chyby. Ale stále mi nefunguje:

$ cat interface.xml
cat: interface.xml: Input/output error

7.11.2005 16:13 Pavel Stárek | skóre: 43 | blog: Tady bloguju já :-) | Kolín
Rozbalit Rozbalit vše Re: chyba I/O

Hmm, a co napíše:

strace cat interface.xml ?

Kdo chce, hledá způsob; kdo nechce, hledá důvod.

7.11.2005 16:19 secido | skóre: 27
Rozbalit Rozbalit vše Re: chyba I/O

execve("/bin/cat", ["cat", "interface.xml"], [/* 13 vars */]) = 0
uname({sys="Linux", node="wan1.lv", ...}) = 0
brk(0)                                  = 0x804d000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=17893, ...}) = 0
old_mmap(NULL, 17893, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/tls/libc.so.6", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1254468, ...}) = 0
old_mmap(NULL, 1264780, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001d000
old_mmap(0x40147000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x129000) = 0x40147000
old_mmap(0x40150000, 7308, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40150000
close(3)                                = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40152000
set_thread_area({entry_number:-1 -> 6, base_addr:0x401522a0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0x40018000, 17893)               = 0
brk(0)                                  = 0x804d000
brk(0x806e000)                          = 0x806e000
brk(0)                                  = 0x806e000
fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 1), ...}) = 0
open("interface.xml", O_RDONLY|O_LARGEFILE) = -1 EIO (Input/output error)
write(2, "cat: ", 5cat: )                    = 5
write(2, "interface.xml", 13interface.xml)           = 13
write(2, ": Input/output error", 20: Input/output error)    = 20
write(2, "\n", 1
)                       = 1
close(1)                                = 0
exit_group(1)                           = ?

7.11.2005 16:17 Tomáš Srnka | skóre: 7 | Bratislava/Praha
Rozbalit Rozbalit vše Re: chyba I/O

presne ten isty problem mam aj ja :-(

vid: Problem s Mrznutim PC.

Five words: "WHY ARE WE DOING THIS?!?!?!?!?" | vpsFree.cz

7.11.2005 16:25 secido | skóre: 27
Rozbalit Rozbalit vše Re: chyba I/O

Neviem, či je to ten istý problém. Možno niečo podobné.

# dmesg|grep hda
Kernel command line: root=/dev/hda2 ro
    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
hda: ST313520A, ATA DISK drive
hda: max request size: 128KiB
hda: 26520480 sectors (13578 MB) w/2048KiB Cache, CHS=26310/16/63, UDMA(33)
Adding 497972k swap on /dev/hda1.  Priority:-1 extents:1
EXT3 FS on hda2, internal journal
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0xd0 { Busy }
hda: DMA disabled
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status error: status=0x50 { DriveReady SeekComplete }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE
hda: status timeout: status=0xd0 { Busy }
hda: no DRQ after issuing WRITE

7.11.2005 16:29 secido | skóre: 27
Rozbalit Rozbalit vše Re: chyba I/O

Vyzerá to na poškodený filesystem, ale chyby budú pravdepodobne spôsobené vadným diskom, lebo disk bol vždy odmontovaný korektne. Budem musieť spustiť badblock nech ho riadne pretestuje.

# fsck.ext3 -n /dev/hda2
e2fsck 1.37 (21-Mar-2005)
Warning!  /dev/hda2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/hda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 1042946 was part of the orphaned inode list.  IGNORED.
Inode 1042947 was part of the orphaned inode list.  IGNORED.
Inode 1042948 was part of the orphaned inode list.  IGNORED.
Inode 1042945, i_size is 1373, should be 8192.  Fix? no

Inode 1042945, i_blocks is 8, should be 16.  Fix? no

Deleted inode 1237892 has zero dtime.  Fix? no

Inode 1237893 was part of the orphaned inode list.  IGNORED.
Inode 1237894 was part of the orphaned inode list.  IGNORED.
Duplicate blocks found... invoking duplicate block passes.
Pass 1B: Rescan for duplicate/bad blocks
Duplicate/bad block(s) in inode 1042945: 32
Pass 1C: Scan directories for inodes with dup blocks.
Pass 1D: Reconciling duplicate blocks
(There are 1 inodes containing duplicate/bad blocks.)

File /usr/share/cacti/resource/snmp_queries.bad/host_disk.xml (inode #1042945, mod time Sun Dec 19 21:01:48 2004)
  has 1 duplicate block(s), shared with 1 file(s):
        <filesystem metadata>
Clone duplicate/bad blocks? no

Delete file? no

Pass 2: Checking directory structure
Entry 'sess_d1cdf9b67a6c0f0d6e9c0b94f54e6e8f' in /var/lib/php4 (929927) has deleted/unused inode 931501.  Clear? no

Entry 'net-snmp_disk.xml' in /usr/share/cacti/resource/snmp_queries.bad (1042497) has deleted/unused inode 1042948.  Clear? no

Entry 'net-snmp_disk.xml' in /usr/share/cacti/resource/snmp_queries.bad (1042497) has an incorrect filetype (was 1, should be 0).
Fix? no

i_file_acl for inode 1042945 (/usr/share/cacti/resource/snmp_queries.bad/host_disk.xml) is 5206, should be zero.
Clear? no

Entry 'interface.xml' in /usr/share/cacti/resource/snmp_queries.bad (1042497) has deleted/unused inode 1042946.  Clear? no

Entry 'kbridge.xml' in /usr/share/cacti/resource/snmp_queries.bad (1042497) has deleted/unused inode 1042947.  Clear? no

Entry 'kbridge.xml' in /usr/share/cacti/resource/snmp_queries.bad (1042497) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'localhost_2.log' in /var/www/mrtg (1205563) has deleted/unused inode 1205547.  Clear? no

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached zero-length inode 1205549.  Clear? no

Unattached inode 1205549
Connect to /lost+found? no

Pass 5: Checking group summary information
Block bitmap differences:  +1872056 -1872057 -(1877141--1877145) +(1877146--1877151) -1877152 -1890420 -1898500 +1988936 -1988937 -2109150 -(2112411--2112414) +(2428942--2428955) -(2430976--2430981) +(2430990--2431009) -(2443264--2443277) -2445649 +2445657 -2449745 +2449753 -(2451456--2451469)
Fix? no

Free blocks count wrong for group #57 (23064, counted=23062).
Fix? no

Free blocks count wrong for group #64 (15946, counted=15945).
Fix? no

Free blocks count wrong (2488480, counted=2524001).
Fix? no

Inode bitmap differences:  -931501 -(1042946--1042948) -1205547 +1205549 -(1237892--1237894)
Fix? no

Free inodes count wrong for group #57 (11688, counted=11687).
Fix? no

Free inodes count wrong (1545034, counted=1544892).
Fix? no


/dev/hda2: ********** WARNING: Filesystem still has errors **********

/dev/hda2: 51190/1596224 files (0.3% non-contiguous), 700422/3188902 blocks

7.11.2005 16:34 Tomáš Srnka | skóre: 7 | Bratislava/Praha
Rozbalit Rozbalit vše Re: chyba I/O

mne PowerMAX hlasi, ze disky su bez chyb, dd if=/dev/hdX of=/dev/null vzdy prejde taktiez bez chyb. Nechapem...

Five words: "WHY ARE WE DOING THIS?!?!?!?!?" | vpsFree.cz

Dotaz: chyba I/O

Odpovědi