corruption

SQLite3 database or disk is full / the database disk image is malformed

女生的网名这么多〃 提交于 2019-11-26 18:27:15
My database is about 25 MB, and I've verified that the username accessing it, as well as the file permissions haven't changed in months. I'm having a problem where queries are failing due to a "database or disk is full" and then sometimes "database disk image is malformed" issue. Unless I'm reading this wrong, my disk isn't anywhere near full (this is an Ubuntu server, 9.10, if it makes any difference) Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 19610300 2389596 16224560 13% / udev 10240 128 10112 2% /dev none 254136 0 254136 0% /dev/shm none 254136 36 254100 1% /var/run none

resolving corruption in SQL Server Compact Edition database files

ε祈祈猫儿з 提交于 2019-11-26 18:16:50
问题 This is not a query. Its a summary of our solution to get around the problem of corruption in SQL Compact Database files with (almost) definite success. SQLCE Corruption is a very common problem. We've received tremendous help from earlier posts in StackOverflow, and hence this post. Our product is a 3-tier architecture with the server running as a Windows Service connected to Rich Clients through .Net Remoting. Our product uses SQLCE since 2006. We have moved from v3.1, to v3.5 and now v4.0.

Avoid Android VideoView corruption when rotating back to portrait

前提是你 提交于 2019-11-26 14:09:07
问题 I've managed to write a limited video player able to view a .3gp file from internet. The video will be shown centered full screen, maintaining the video aspect ratio. Also, rotations don't interrupt the video, which keeps playing without problems. Everything seems fine, but... on my HTC Legend when you rotate back to portrait, the video is corrupted, and instead of showing full screen it is displayed at its native pixel size. But rotating again to landscape works and is shown perfectly. Any

How to resolve “Error: bad index – Fatal: index file corrupt” when using Git

一曲冷凌霜 提交于 2019-11-26 11:56:43
After git init , I added and committed a few files, made some changes, added and committed. Set up the git daemon (running under Cygwin on WinXP) and cloned the repository once. Now, I get this error with the cloned repository: $ git status error: bad index file sha1 signature fatal: index file corrupt Is there any way to fix this, other than getting a new copy of the repository? If the problem is with the index as the staging area for commits (i.e. .git/index ), you can simply remove the index (make a backup copy if you want), and then restore index to version in the last commit: On OSX/Linux

How to resolve “Error: bad index – Fatal: index file corrupt” when using Git

随声附和 提交于 2019-11-26 02:15:56
问题 After git init , I added and committed a few files, made some changes, added and committed. Set up the git daemon (running under Cygwin on WinXP) and cloned the repository once. Now, I get this error with the cloned repository: $ git status error: bad index file sha1 signature fatal: index file corrupt Is there any way to fix this, other than getting a new copy of the repository? 回答1: If the problem is with the index as the staging area for commits (i.e. .git/index ), you can simply remove

How to recover Git objects damaged by hard disk failure?

▼魔方 西西 提交于 2019-11-26 01:46:50
问题 I have had a hard disk failure which resulted in some files of a Git repository getting damaged. When running git fsck --full I get the following output: error: .git/objects/pack/pack-6863e0a0e4b4ded6090fac5d12eba6ca7346b19c.pack SHA1 checksum mismatch error: index CRC mismatch for object 6c8cae4994b5ec7891ccb1527d30634997a978ee from .git/objects/pack/pack-6863e0a0e4b4ded6090fac5d12eba6ca7346b19c.pack at offset 97824129 error: inflate: data stream error (invalid code lengths set) error:

How to recover Git objects damaged by hard disk failure?

感情迁移 提交于 2019-11-25 20:49:51
I have had a hard disk failure which resulted in some files of a Git repository getting damaged. When running git fsck --full I get the following output: error: .git/objects/pack/pack-6863e0a0e4b4ded6090fac5d12eba6ca7346b19c.pack SHA1 checksum mismatch error: index CRC mismatch for object 6c8cae4994b5ec7891ccb1527d30634997a978ee from .git/objects/pack/pack-6863e0a0e4b4ded6090fac5d12eba6ca7346b19c.pack at offset 97824129 error: inflate: data stream error (invalid code lengths set) error: cannot unpack 6c8cae4994b5ec7891ccb1527d30634997a978ee from .git/objects/pack/pack