Buffer I/o Error On Device Dm-0 Logical Block 1
Contents |
Wiki Search Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Software [SOLVED] buffer i o error on device sdb logical block 0 Buffer I/O error on device dm-0 User Name Remember Me? Password Linux
Buffer I O Error On Device Sdc Logical Block 0
- Software This forum is for Software issues. Having a problem installing a new program? Want to know buffer i o error on device sr0 logical block 0 which application is best for the job? Post your question in this forum. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest.
Buffer I O Error On Device Sdc1 Logical Block
By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit buffer i o error on device sda logical block the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 07-24-2
hp com>, Alasdair G Kergon
Kernel Buffer I/o Error On Device Dm-2 Logical Block
wrote: Hi Alasdair, We are seeing an IO error problem on a DM
Buffer I/o Error On Device Dm-3
device, when the HBA ports of another host , seen through the same switch are disabled/enable . We are not buffer i/o error on device dm-0 logical block redhat understanding on why the paths are failed when ports on other hosts are disabled. Please explain. Below is the problem description and steps to reproduce. Problem : I/O Error on DM device on http://www.linuxquestions.org/questions/linux-software-2/buffer-i-o-error-on-device-dm-0-a-4175512149/ one host when HBA ports of another host are disabled. OS distros : RHEL4.0 U2/U3. HOW-TO reproduce the problem : 1. Configure 2 storage arrays (A1 , A2) and two host (H1, H2) in the same zone, so that both the hosts can see both the arrays. Create and p resent LUNs (L1, L2) from array (A1) to host (H1) 2. Stop the multipathd daemon (for testing https://www.redhat.com/archives/dm-devel/2006-March/msg00160.html purpose on why the IO error when ports of other hosts are failed) . Not stopping it may take long time to reproduce the problem. 3. Start I/O on DM device representing luns L1 and L2 on host H1. We used dt tool for IO exercising. 4. Disable host ports of host H2 or any port of array A2 one after the other (few times) OR disable and enable the same port of the other host – few times (may be 4-5 times). 5. Application (dt tool) aborts with IO error on host H1. ===== Snippet of sys log output (while do ing I/O on /dev/dm-0 ) Feb 1 11:47:14 apwtest52 kernel: SCSI error : <2 0 0 1> return code = 0x20000 Feb 1 11:47:14 apwtest52 kernel: end_request: I/O error, dev sda, sector 1584600 Feb 1 11:47:14 apwtest52 kernel: device-mapper: dm-multipath: Failing path 8:0. <=================path failed, after disabling/enabling the H2 host port 1 Feb 1 11:47:14 apwtest52 kernel: end_request: I/O error, dev sda, sector 1584608 Feb 1 11:47:45 apwtest52 kernel: SCSI error : <3 0 1 1> return code = 0x20000 Feb 1 11:47:45 apwtest52 kernel: end_request: I/O error, dev sdg, sector 861400 Feb 1 11:47:45
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & http://unix.stackexchange.com/questions/98208/i-o-errors-on-linux-lvm Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody http://askubuntu.com/questions/520358/logical-block-number-in-the-buffer-i-o-error can ask a question Anybody can answer The best answers are voted up and rise to the top I/O errors on Linux LVM up vote 4 down vote favorite I have a CentOS 6 box with LVM setup and one of the PVs is error on a USB disk (I know). One of them is getting the error: Oct 30 10:57:07 alpha01 kernel: lost page write due to I/O error on dm-3 Oct 30 10:57:07 alpha01 kernel: Buffer I/O error on device dm-3, logical block 4 Which is causing problems with all of the LVs on it. pvs shows the PV as unknown device. I can ls to the logical volumes and they show up in lvdisplay, but first I get a bunch of IO errors. I made sure the cables are secure between the error on device USB drive. What should I do to get this back up and running for the meanwhile? Should I unmount each LV and run an fsck.ext4 on each one like fsck.ext4 -y /dev/vg1/lv_logvolname ? linux lvm fsck share|improve this question asked Oct 30 '13 at 15:06 Gregg Leventhal 2,29032752 In addition to fsck, if the external drive is SMART capable, checking the drive status/health and running the drive self tests may be useful. Backing up all the data may also be important. –rickhg12hs Oct 30 '13 at 15:44 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted I usually don't go the route of running an fsck and assume the disk is failing or has bad sectors. I definitely wouldn't run the fsck using the -y, since this will give fsck to attempt to start moving blocks which may exacerbate the problem. Instead I'll run a tool such as Spinrite (Commercial) or HDAT2 (freeware) on the disk to do the analysis & potential repair. What else? See my other answers to these questions for additional methods: fsck -cc /dev/sdb1 gives this result. Is everything okay> Detect damaged audio CD The 2nd link provides details about another tool, safecopy for attempting to recover data from a failed/failing drive. It doesn't attempt to do any repairing of hte HDD. share|improve this answer edited Aug 4 '15 at 22:28 answered Oct 30 '13 at 16:19 slm♦ 164k40299469 Is there a linux spinrite that can be run from a normal runlevel 3 without a boot cd, and simply analyze speci
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Logical Block number in the “Buffer I/O error” up vote 2 down vote favorite I was trying to determine a bad PV which was causing the LV to report Buffer I/O error and found this interesting behaviour in the "Buffer I/O error" message. On a Large LV that is mapped to different PVs, I tried to use the "logical block" reported in the error, to match with the dmsetup table to find out which target device it was on. However this method doesn't seem to be reliable. I used dmsetup to create a device mapper device, with one or a number of holes in it. And the error messages are very interesting and I can't make sense of the pattern. It seems the "Logical Block" number in the error message depends on the size of the hole and also it's position. Is there a definitive way to locate the actual bad block? Here are the tests that I did +++ TEST 1 error block at 8, buffer i/o error at LB 8 root@ubuntu:~# dmsetup create test x.tab root@ubuntu:~# dmsetup table test 0 8 linear 8:16 0 8 1 error 9 1000 linear 8:16 8 root@ubuntu:~# dd if=/dev/mapper/test of=/dev/null bs=512 count=1000 dd: error reading ‘/dev/mapper/test’: Input/output error 8+0 records in