I O Error On Device Dm
Contents |
hp com>, Alasdair G Kergon
Kernel Buffer I/o Error On Device Dm-2 Logical Block
through the same switch are disabled/enable . We are not understanding on why the paths are failed when ports on other hosts
Buffer I/o Error On Device Dm-3
are disabled. Please explain. Below is the problem description and steps to reproduce. Problem : I/O Error on DM device on one host when HBA ports of another host are disabled. OS distros : RHEL4.0 U2/U3. HOW-TO
Buffer I/o Error On Device Dm-0 Logical Block Redhat
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 purpose on why the IO error when ports of other hosts are failed) . Not stopping it may take long time to reproduce the lost page write due to i/o error on dm-0 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 apwtest52 kernel: device-mapper: dm-multipath: Failing path 8:96. <=================path failed, after disabling/enabling the H2 host port 2 Feb 1 11:47:45 apwtest52 kernel: end_request: I/O error, dev sdg, sector 861408 Feb 1 11:47:45 apwtest52 kernel: SCSI error : <3 0 0 1> return code = 0x20000 Feb 1 11:47:45 apwtest52 kernel: end
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 buffer i/o error on device dm-7 logical block Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags buffer i/o error on device logical block Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and lost page write due to i/o error on dm-2 other Un*x-like operating systems. 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 I/O errors https://www.redhat.com/archives/dm-devel/2006-March/msg00160.html on Linux LVM up vote 4 down vote favorite I have a CentOS 6 box with LVM setup and one of the PVs is 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 http://unix.stackexchange.com/questions/98208/i-o-errors-on-linux-lvm 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 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,31032752 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
Errors? Sun, 21/09/2008 - 2:06pm — Homer A couple of days ago I started getting these errors whenever I ran anything that scanned for logical volumes (Linux LVM2): Buffer I/O error on device dm-6, logical block 0 http://slated.org/device_mapper_weirdness Buffer I/O error on device dm-7, logical block 0 Buffer I/O error on device http://forums.fedoraforum.org/showthread.php?t=309039 dm-8, logical block 0 Buffer I/O error on device dm-9, logical block 0 My first reaction was panic, as I initially believed my HDD was failing, but after some investigation I realised that the above devices simply didn't exist. Yes, that is strange. Why would device mapper suddenly think there were devices there that ... well, o error weren't? I had a look in the /sys/block/ directory, and sure enough there were entries for dm-6; dm-7; dm-8 and dm-9, but looking in their respective slaves/ directory revealed the problem ... the soft links to the actual block devices were broken. Broken links to non-existent device nodes? It gets stranger. So then I thought I'd just try to delete those broken links, after all they pointed to non-existent hardware o error on (for some reason that hadn't yet occurred to me), but alas the /sys/ directory is read-only, even for root. Hmm, what now? Then I suddenly remembered that a couple of days previously I'd inserted a USB thumb-drive, copied some files off it, then unplugged it. I did make sure that I'd unmounted it first, but I'd completely forgotten that logical volumes need to be explicitly deactivated first (using "lvm vgchange -an {volume group}"), before you remove them, and I hadn't done that. Oops. Unfortunately the lvm command simply returned a "device busy" error, so I found myself back at square one. Although the error messages were not fatal, since no actual hardware was damaged, and no data loss was likely, it was still very annoying to see these Buffer I/O error messages every time I did anything related to LVM. Rebooting would have fixed the problem of course, but I'm deeply averse to utilising Windows-style solutions on Linux systems that should be repairable without rebooting. Also, this is a server, and I hated the thought of losing uptime, and having to restart everything and check all the services were working properly, just to solve some stupid "non-existent logical volumes" problem. Sigh! It looked like I'd have to solve t
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Hardware & Laptops Buffer I/O error on device dm-0 FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with your hardware, including laptop issues Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 1st March 2016, 06:03 PM pmeni Offline Registered User Join Date: Mar 2016 Location: AR Posts: 2 Buffer I/O error on device dm-0 Hi, I have problems with Fedora 23, (Fedora 22 works fine, doesn't have this kind of errors), with no reason the disk fail an run into read-only. I changed the disk to a new one and the same issue. Anyone have this errors?, May be I can try to install Fedora whit no LVM and see if this solve the problem. Tested with this kernel versions: kernel.x86_64 4.3.5-300.fc23 kernel.x86_64 4.4.2-301.fc23 Full log: http://ur1.ca/ol96o Mar 01 12:51:48 NORC kernel: ata6.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x6 frozen Mar 01 12:52:48 NORC kernel: ata6.00: failed command: WRITE FPDMA QUEUED Mar 01 12:52:48 NORC kernel: ata6.00: cmd 61/50:50:08:6c:1b/00:00:06:00:00/40 tag 10 ncq 40960 out res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 01 12:52:48 NORC kernel: ata6.00: status: { DRDY } Mar 01 12:52:48 NORC kernel: ata6: hard resetting link Mar 01 12:52:48 NORC kernel: ata6: link is slow to respond, please be patient (ready=0) Mar 01 12:52:48 NORC kernel: ata6: COMRESET failed (errno=-16) Mar 01 12:52:48 NORC kernel: EXT4-fs warning (device dm-0): ext4_end_bio:329: I/O error -5 writing to inode 2368435 (offset 0 size 0 starting block 4954560) Mar 01 12:52:48 NORC kernel: Buffer I/O error on device dm-0, logical block 4954560 Mar 01 12:52:48 NORC kernel: EXT4-fs warning (device dm-0): ext4_end_bio:329: I/O error -5 writing to inode 2368435 (offset 0 size 0 starting block 4954561) Mar 01 12:52:48 NORC kernel: Buffer I/O error on device dm-0, logical block 4954561 Mar 01 12:52:48 NORC kernel: Buffer I/O error on device dm-0, logical block 4954562 Mar 01 12:52:48 NORC kernel: Buffer I/O error on device dm-0, logical block 4954563 Mar 01 12:52:48 NORC kernel: Buffer I/O error on device dm-0, logical block 4954564 Mar 01 12:52:48 NORC kernel: Buffer I/O error on de