Error Reading Blocks From Snapshot
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have error reading block short read Meta Discuss the workings and policies of this site About Us
Error Reading Block Invalid Argument
Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with
Error Reading Block Force Rewrite
us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. 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 r1soft agent is failing with the error: “write error while sending code: Broken pipe” up vote 1 down vote favorite I have an Ubuntu 10.04.4 LTS server with r1soft agent installed in it. Recently, the backups are failing with the following error. -------- write error while sending code: Broken pipe -------- I have reinstalled the buagent but to no avail. On checking the server logs, I could see the following errors listed in it: -------- # tail -f /var/log/messages |grep -i buagent Nov 17 03:35:06 microscope buagent: Need to back up 126 sectors Nov 17 03:35:06 microscope buagent: (Righteous Backup Linux Agent) 1.79.0 build 12433 Nov 17 03:35:06 microscope buagent: allowing control from backup server (10.128.136.195) with valid RSA key Nov 17 03:35:06 microscope buagent: allowing control from backup server (10.128.136.201) with valid RSA key Nov 17 03:35:06 microscope buagent: sending auth challenge for allowed host at (10.128.136.201) port (47890) Nov 17 03:35:06 microscope buagent: host (10.128.136.201) port (47890) authentication successful Nov 17 03:35:06 microscope buagent: Backup request accepted. Starting backup. Nov 17 03:35:06 microscope buagent: Snapshot completed in 0.010 seconds. Nov 17 03:45:03 microscope buagent: Error reading blocks from snapshot. Nov 17 03:45:03 microscope buagent: Reading block
[x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug174742 - corrupted snapshot filesystems: Error reading/writing snapshot Summary: corrupted snapshot filesystems: Error reading/writing snapshot Status: CLOSED NOTABUG Aliases: None Product: Red Hat Enterprise Linux 4 Classification: Red Hat Component: lvm2 (Show other bugs) Sub Component: --- Version: http://serverfault.com/questions/449676/r1soft-agent-is-failing-with-the-error-write-error-while-sending-code-broken 4.3 Hardware: All Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Alasdair Kergon QA Contact: Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2005-12-01 15:43 EST by Corey Marthaler Modified: 2007-11-30 17:07 EST (History) CC List: 4 users (show) agk jbrassow https://bugzilla.redhat.com/show_bug.cgi?id=174742 kanderso rkenna See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2006-01-25 14:11:41 EST Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Corey Marthaler 2005-12-01 15:43:20 EST Description of problem: Unlike bz 173209 where the origin fs becomes corrupt, here the 2nd snapshot of that fs becomes corrupt # snapper test output: Creating origin volume Logical volume "origin" created Placing an ext filesystem on origin volume mke2fs 1.35 (28-Feb-2004) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 1310720 inodes, 2621440 blocks 131072 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=2684354560 80 block groups 32768 blocks per group,
Functionality Database Disk Image Malformed Tools Attachments (0) Page History Restrictions Info Link to this Page… View in Hierarchy View Wiki Markup Export to PDF Export to Word Database Disk Image Malformed Skip to end of metadata Page http://wiki.r1soft.com/display/kb3/Database+Disk+Image+Malformed restrictions apply Added by Internal, last edited by Internal on Jul 10, 2013 (view change) Comment: Go to start of metadata Symptom Server Backup returns the following error message: "Error Server [11] reset(): http://documentation.commvault.com/commvault/v10/article?p=products/vs_vmware/snap/troubleshooting.htm database disk image is malformed(11)" Cause This error may be caused by a hardware, file system or Operating System fault causing corruption to the Disk Safe file. Disk Safe viability, in part, relies on error reading the stability of the underlying hardware and Operating System of the host storage device. Resolution The safest solution is to create a new Disk Safe as soon as Server Backup reports that the database disk image is malformed. In some situations, the Disk Safe may still be usable for restoring recovery points that were created before the Disk Safe reported a corruption. However, we have no way error reading block to determine the extent of the corruption or if the workaround mentioned below will be able to repair the Disk Safe. In addition, we do not expect that a corrupt Disk Safe will be successful in a bare metal restore. Workaround You may attempt to repair the Disk Safe by running a Disk Safe Verification (DSV) task (introduced in Server Backup v5.2.0) against the Disk Safe with the malformed image. The DSV will check the most recent recovery point to ensure all blocks are accounted for. If the disk safe fails to verify, a repair attempt will be made during the next replication task which will attempt to reconcile any missing blocks from the recovery point. NoteFor more information on DSV, please review our documentation: http://wiki.r1soft.com/display/ServerBackup/Scheduling+Disk+Safe+Verification Please note that DSV verifies only those recovery points with an available status. DSV does not verify recovery points with a locked or incomplete status. Additional Suggestions If DSV does not find any errors with the recovery point, the problem may have originated outside of the disk safe. In this case, we recommend that you create a new Disk Safe and also check the disks that host the Disk Safe and also revie
with one or more errors SS0002: While performing IntelliSnap backup on a Linux VM, metadata collection is not included in the backup SS0003: Mount operations on an ESX server are failing using NFS protocol SS0004: Two snapshots are created SS0005: File level revert is not supported for a Virtual Machine SS0006: Exchange mining operation fails SS0007: The Operation is not allowed in the current state SS0008: Driver cannot be found SS0010: Discovery Failed. Unable to access host VMW0064: Changed block tracking verification failed for disk [%s] on virtual machine [%s] SS0011: NFS datastore becomes inaccessible after the mounting the snapshot VMW0070: File-level restore fails when destination client has a MediaAgent SS0012: Unable to create a Virtual Machine snapshot SS0013: VMware snapshot removal failures VMW0036: Virtual server machine names are created with '_1' appended to the original client name VMW0039: You do not have access rights to this file VMW0068: Reset Changed Block Tracking (CBT) for VMware backups VMW0040: Failed to start the virtual machine SS0021: Unable to browse files on snapshot for Windows 2008 R2 virtual machine - Disk:[