<div> </div>
<div>It look like an hard drive issue not an LVM problem.</div>
<div> </div>
<div>Look at your DMA setting.</div>
<div> </div>
<div>Marc Picornell de Louvigny<br><br> </div>
<div><span class="gmail_quote">On 8/5/05, <b class="gmail_sendername">Peter Kjellström</b> <<a href="mailto:cap@nsc.liu.se">cap@nsc.liu.se</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br><br>You probably have a bad disk under there (hda). Copy data of it as fast as<br>you can, maybe you'll get some of it before it bites the dust completely.
<br>Of course if you have backups, just sit back and feel good ;-)<br><br>The thing that speaks most clearly for a hard error on disk level is:<br>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=43072608, sector=43072608
<br><br>good luck,<br>Peter<br><br>On Friday 05 August 2005 16.54, James B. Byrne wrote:<br>> I was creating some directories (mkdir xxxx) while cd'ed to a mounted<br>> LV. The first couple of directories were created but subsequent
<br>> attempts give the following error:<br>><br>> #mkdir: cannot create directory `xxxxx': Input/output error<br>><br>> The contents of /var/log/messages shows this:<br>><br>> Aug 5 10:48:57 inet05 kernel: hda: dma_intr: status=0x51 {
<br>> DriveReady SeekComplete Error }<br>> Aug 5 10:48:57 inet05 kernel: hda: dma_intr: error=0x40 {<br>> UncorrectableError }, LBAsect=43072608, sector=43072608<br>> Aug 5 10:48:57 inet05 kernel: ide: failed opcode was: unknown
<br>> Aug 5 10:48:57 inet05 kernel: end_request: I/O error, dev hda,<br>> sector 43072608<br>> Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4):<br>> read_block_bitmap: Cannot read block bitmap - block_group = 68,
<br>> block_bitmap = 2228224<br>> Aug 5 10:48:57 inet05 kernel: Aborting journal on device dm-4.<br>> Aug 5 10:48:57 inet05 kernel: ext3_abort called.<br>> Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4):
<br>> ext3_journal_start_sb: Detected aborted journal<br>> Aug 5 10:48:57 inet05 kernel: Remounting filesystem read-only<br>> Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in<br>> ext3_reserve_inode_write: Journal has aborted
<br>> Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in<br>> start_transaction: Journal has aborted<br>> Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in<br>> ext3_mkdir: Journal has aborted
<br>><br>> What is going on? How do I fix it?<br>><br>> Regards,<br>> Jim<br>><br>> The favour of a direct response is requested as I am a diges<br>> subscriber.<br><br>--<br>------------------------------------------------------------
<br>Peter Kjellström |<br>National Supercomputer Centre |<br>Sweden | <a href="http://www.nsc.liu.se">http://www.nsc.liu.se</a><br><br><br>_______________________________________________
<br>CentOS mailing list<br><a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br><a href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</a><br><br><br><br></blockquote>
</div><br>