Lost Page Write Due To I O Error On Dm
Contents |
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway buffer i/o error on device dm-2 logical block (Formerly Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and kernel buffer i/o error on device dm-2 logical block Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products
Buffer I/o Error On Device Dm-3
XenServer XenServer Product Family Storage Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. lost page write
Lost Page Write Due To I/o Error On Dm-1
due to I/O error Started by James Larcombe , 04 February 2014 - 03:17 PM Login to Reply 9 replies to this topic James Larcombe Members #1 James Larcombe 37 posts Posted 04 February 2014 - 03:17 PM Hi, I have a 3 x Xenservers running 5.6 Sp2. These connect to 2 Open-E sans and run approx kernel: buffer i/o error on device dm-0, logical block 90 vm's spread across them. This morning it was reported to me that one of the VM's had gone read only. We rebooted and had to run fsck to fix some corruption. On closer inspection this seems to have happened after running nightly snapshot of the running vm and then coalescing. In /var/log/messages I see the following: Feb 4 07:53:51 xen1 tapdisk[15916]: ERROR: errno 0 at tapdisk_vbd_make_response: returning BLKIF_RSP -1 Feb 4 07:53:52 xen1 last message repeated 30 times Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 5498349 Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 6022533 Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 4450005 Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 6022549 Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 6022709 Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 11264141 Feb 4 07:53:52 xen1 kernel: end_request: I/O error, dev tdn, sector 17816117 Feb 4 07:5
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
Buffer I O Error On Device Dm 0 Logical Block Redhat
developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question buffer i/o error on dev logical block async page read _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; lost page write due to i/o error on sdb1 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 on Linux LVM up vote 4 down vote http://discussions.citrix.com/topic/347727-lost-page-write-due-to-io-error/ 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 the PV as unknown device. I can ls to the logical volumes http://unix.stackexchange.com/questions/98208/i-o-errors-on-linux-lvm 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 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
titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches Recent Posts Menu Forums Forums Quick Links Search Forums Recent Posts Members Members Quick https://forum.proxmox.com/threads/lost-page-write-due-to-i-o-error.6277/ Links Notable Members Current Visitors Recent Activity New Profile Posts Menu Log in Sign up http://www.saout.de/pipermail/dm-crypt/2011-February/001518.html Proxmox Support Forum Forums > Retired and read only forums > Proxmox VE 1.x: Installation and configuration > This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. lost page write due to I/O error Discussion in 'Proxmox VE 1.x: Installation and configuration' started by Cayuga, May 3, 2011. Cayuga Member Joined: May o error 3, 2011 Messages: 63 Likes Received: 0 I installed Proxmox a couple of weeks ago and am currently running with a three node cluster. Some of my Linux clients (2.6.32) are getting the following errors: [ 1491.167866] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 1491.167869] sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor] [ 1491.167872] Descriptor sense data with sense descriptors (in hex): [ 1491.167874] 72 0b 00 00 00 00 00 0c 00 0a 80 00 o error on 00 00 00 00 [ 1491.167886] 01 af 96 40 [ 1491.167889] sd 0:0:0:0: [sda] Add. Sense: No additional sense information [ 1491.167893] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 01 af 96 40 00 00 08 00 [ 1491.167900] end_request: I/O error, dev sda, sector 28284480 [ 1491.167905] Buffer I/O error on device dm-0, logical block 3410328 [ 1491.167906] lost page write due to I/O error on dm-0 I've tried with and without virtio and it makes no difference. The underlying storage is iSCSI if that matters. Any ideas about what I should look for or what I might be able to change to make these errors go away? #1 Cayuga, May 3, 2011 dietmar Proxmox Staff Member Staff Member Joined: Apr 28, 2005 Messages: 14,430 Likes Received: 86 Are there any error logs on the host too? #2 dietmar, May 4, 2011 Cayuga Member Joined: May 3, 2011 Messages: 63 Likes Received: 0 Dietmar, Thanks for asking. The only logs that were modified when the error last happened were: /var/log/daemon.log /var/log/syslog /var/log/auth.log and none of them showed any errors. I did see the following entries that don't have a time correlation to the guest errors: May 2 10:07:11 danish kernel: scsi 2:0:0:0: Direct-Access OPNFILER VIRTUAL-DISK 0 PQ: 0 ANSI: 4 May 2 10:07:11 danish kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0 May 2 10:07:11 danish kernel: sd 2:
crash leads to I/O errors when accessing partition [FIXED] Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] SUMMARY After a power outage an encrypted partition is inaccessible, as is a regular one, and perhaps the disk as a whole. Is there a way to recover, or at least diagnose? The disk is in an external USB dock. I'm hoping a reboot might help, but I'd like advice before I do anything that might cause further damage. As I investigated and discovered the problem extends beyond the encrypted volume this query may be a bit off topic. On topic, is it reasonable to expect the encrypted partition to be recoverable in these circumstances? I'd appreciate off-topic advice as well :) Please cc me directly to help me see this even though my mail system is broken because of this problem. DETAILS The physical disk is a Western Digital WD-20EARS 2TB SATA 3GBPS (5400 RPM) mounted on Unitek SATA HDD Docking Station with Hub Y-1063. It is connected via USB to a Pentium 4 system running linux kernel 2.6.26-2-686, Debian GNU/Linux, mostly lenny. The disk has 2 partitions with a GPT. The first partition is a spare; the 2nd, larger, one is part of an LVM volume group that includes other disks. One logical volume (LV) serves as the raw partition for a luks encrypted device which backs the mail spool. Another LV serves directly as a spare backup area. The docking station has surge suppression only; the main computer went through the brief power failure without shutting down. Since then I get I/O errors when I attempt to access the encrypted partition: Wed Feb 16 04:57:47 PST 2011 Power failure. Wed Feb 16 04:57:53 PST 2011 Running on UPS batteries. Wed Feb 16 04:58:14 PST 2011 Mains returned. No longer on UPS batteries. Wed Feb 16 04:58:14 PST 2011 Power is back. UPS running on mains. led to Feb 16 04:57:46 corn kernel: [59153.907186] sd 2:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK Feb 16 04:57:46 corn kernel: [59153.907186] end_request: I/O error, dev sdc, sector 345805680 Feb 16 04:57:46 corn kernel: [59153.907186] ReiserFS: dm-15: warning: zam-7001: io error in reiserfs_find_entry Feb 16 04:57:46 corn kernel: [59153.907186] usb 5-3.1: U