* Help with a possibly corrupt repo
@ 2010-05-10 19:37 Jonathan Leto
2010-05-10 20:17 ` Dmitry Potapov
0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Leto @ 2010-05-10 19:37 UTC (permalink / raw)
To: git
Howdy,
Due to a network (or possibly disk) error, I started getting this error:
$ git --version
git version 1.7.1.166.gf2086
error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
fatal: object 66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba is corrupte$ git reflog
291cf66 HEAD@{0}: commit: Class::MethodMaker
44c9cdb HEAD@{1}: commit: TAP::Harness::Archive
89053c5 HEAD@{2}: HEAD^: updating HEAD
b6eb92a HEAD@{3}: commit: TAP::Harness::Archive
89053c5 HEAD@{4}: commit: Bio::Perl 1.006001
c745fed HEAD@{5}: commit: MooseX::Declare
d4097d4 HEAD@{6}: commit (initial): Initial .modulebuildrc
error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
fatal: object 66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba is corrupted
$ uname -a
Linux datura 2.6.31-21-generic #59-Ubuntu SMP Wed Mar 24 07:28:27 UTC
2010 x86_64 GNU/Linux
This git was built from the 'next' branch a few days ago. Is there
anyway to fix my repo? I can provide a copy of my .git directory if
needed, but it is 54MB. As for background, this repo contained a set
of CPAN modules, via local::lib, so it had many files but only a few
commits.
I tried "git gc", but it borks on the corrupt sha1:
$ git gc
error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
fatal: object 66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba is corrupted
error: failed to run repack
Thanks for any help anybody can give.
Duke
--
Jonathan "Duke" Leto
jonathan@leto.net
http://leto.net
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Help with a possibly corrupt repo
2010-05-10 19:37 Help with a possibly corrupt repo Jonathan Leto
@ 2010-05-10 20:17 ` Dmitry Potapov
2010-05-10 21:05 ` Jonathan Leto
0 siblings, 1 reply; 6+ messages in thread
From: Dmitry Potapov @ 2010-05-10 20:17 UTC (permalink / raw)
To: Jonathan Leto; +Cc: git
On Mon, May 10, 2010 at 12:37:36PM -0700, Jonathan Leto wrote:
> Due to a network (or possibly disk) error, I started getting this error:
>
> $ git --version
> git version 1.7.1.166.gf2086
> error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
The object is "loose", so it should be a file:
.git/objects/66/fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba
it would be interesting to look at it to see what is wrong...
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Help with a possibly corrupt repo
2010-05-10 20:17 ` Dmitry Potapov
@ 2010-05-10 21:05 ` Jonathan Leto
2010-05-10 21:28 ` Dmitry Potapov
0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Leto @ 2010-05-10 21:05 UTC (permalink / raw)
To: Dmitry Potapov; +Cc: git
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Howdy,
I have attached the loose file, hopefully that will help. This may
also be useful:
$ hexdump .git/objects/66/fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba|tail
0002060 b379 5619 df70 0a6f 6bdf 570d 9a52 9257
0002070 045a d552 68d8 bd31 ddaf 7bed 73b8 dcf1
0002080 3dd9 f773 3874 824d e419 5891 019c 9252
0002090 3efb fdc4 99f8 9f85 f697 926c f9bf 5cb1
00020a0 ff7a eb8c 5055 8283 8a4b f332 41d2 ea8a
00020b0 480f e52b 6e97 947c a2ea a65e 393b d98b
00020c0 deed 3541 7800 56dd 005c 0000 0000 0000
00020d0 0000 0000 0000 0000 0000 0000 0000 0000
*
0003000
error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
fatal: object 66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba is corrupted
Duke
--
Jonathan "Duke" Leto
jonathan@leto.net
http://leto.net
[-- Attachment #2: fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba --]
[-- Type: application/octet-stream, Size: 12288 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Help with a possibly corrupt repo
2010-05-10 21:05 ` Jonathan Leto
@ 2010-05-10 21:28 ` Dmitry Potapov
2010-05-20 14:57 ` Jonathan Leto
0 siblings, 1 reply; 6+ messages in thread
From: Dmitry Potapov @ 2010-05-10 21:28 UTC (permalink / raw)
To: Jonathan Leto; +Cc: git
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
On Mon, May 10, 2010 at 02:05:09PM -0700, Jonathan Leto wrote:
> 00020c0 deed 3541 7800 56dd 005c 0000 0000 0000
> 00020d0 0000 0000 0000 0000 0000 0000 0000 0000
> *
> 0003000
> error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
> fatal: object 66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba is corrupted
The object is "tree", and it contains a lot of zeros at end.
I have truncated them, and it appears to fix the problem.
I have attached the corrected file.
But the important question is how it could happen. What filesystem
do you use? Do you store it on the local disk or network share?
Dmitry
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba --]
[-- Type: text/plain; charset=utf-8, Size: 203 bytes --]
x\x01+)JMU024c040031Qp,*J¬Ô+Èe˜Õd¼2h›®ô·[‰ÒëÕ/q]\x14Ä
U㔟Ÿ\x03RÒÛk¾}‰¨kÑÄå3d\x15~ŸxQyq–"T‰s~J*H‰L¿S7\aï÷Vé}y³\x19Vpßo
ßk\rWRšW’Z\x04RÕØh1½¯Ýí{¸sñÜÙ=s÷t8M‚\x19ä‘Xœ\x01R’û>Äýø™…Ÿ—öl’¿ù±\zÿŒëUPƒ‚KŠ2óÒAŠê\x0fH+å—n|”ê¢^¦;9‹ÙíÞA5\0xÝV\
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Help with a possibly corrupt repo
2010-05-10 21:28 ` Dmitry Potapov
@ 2010-05-20 14:57 ` Jonathan Leto
2010-05-21 2:59 ` Dmitry Potapov
0 siblings, 1 reply; 6+ messages in thread
From: Jonathan Leto @ 2010-05-20 14:57 UTC (permalink / raw)
To: Dmitry Potapov; +Cc: git
Howdy,
I ran into this corruption issue using ecryptfs with an ext4
filesystem (on a local SSD drive) on Ubuntu 9.10. The corruption seems
to coincide with getting these errors in my dmesg output:
[12773.772426] ecryptfs_decrypt_page: Error attempting to read lower
page; rc = [-22]
[12773.772431] ecryptfs_readpage: Error decrypting page; rc = [-22]
[12796.061574] ecryptfs_read_lower: octets_read = [-4]; expected [4096]
[12796.061584] ecryptfs_read_and_validate_header_region: Error reading
header region; rc = [-22]
I am lead to believe that ecryptfs+ext4 is not yet production-ready,
although it could be a weird failure mode of my drive. I have not had
more time to test this setup with other hardware.
Duke
On Mon, May 10, 2010 at 2:28 PM, Dmitry Potapov <dpotapov@gmail.com> wrote:
> On Mon, May 10, 2010 at 02:05:09PM -0700, Jonathan Leto wrote:
>> 00020c0 deed 3541 7800 56dd 005c 0000 0000 0000
>> 00020d0 0000 0000 0000 0000 0000 0000 0000 0000
>> *
>> 0003000
>> error: garbage at end of loose object '66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba'
>> fatal: object 66fdbaef5ae12a8402f6b0f7c1a73a3ce72e8eba is corrupted
>
> The object is "tree", and it contains a lot of zeros at end.
> I have truncated them, and it appears to fix the problem.
> I have attached the corrected file.
>
> But the important question is how it could happen. What filesystem
> do you use? Do you store it on the local disk or network share?
>
>
> Dmitry
>
--
Jonathan "Duke" Leto
jonathan@leto.net
http://leto.net
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Help with a possibly corrupt repo
2010-05-20 14:57 ` Jonathan Leto
@ 2010-05-21 2:59 ` Dmitry Potapov
0 siblings, 0 replies; 6+ messages in thread
From: Dmitry Potapov @ 2010-05-21 2:59 UTC (permalink / raw)
To: Jonathan Leto; +Cc: git
On Thu, May 20, 2010 at 07:57:30AM -0700, Jonathan Leto wrote:
>
> I ran into this corruption issue using ecryptfs with an ext4
> filesystem (on a local SSD drive) on Ubuntu 9.10.
> to coincide with getting these errors in my dmesg output:
>
> [12773.772426] ecryptfs_decrypt_page: Error attempting to read lower
> page; rc = [-22]
> [12773.772431] ecryptfs_readpage: Error decrypting page; rc = [-22]
> [12796.061574] ecryptfs_read_lower: octets_read = [-4]; expected [4096]
> [12796.061584] ecryptfs_read_and_validate_header_region: Error reading
> header region; rc = [-22]
>
> I am lead to believe that ecryptfs+ext4 is not yet production-ready,
Sounds like this bug:
https://bugs.launchpad.net/ecryptfs/+bug/509180
and maybe related to this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/490005
I don't think it is caused by combination of ecryptfs+ext4. I have seen
a similar bug report for ecryptfs+ext3 as well. In fact, a lot of bug
fixes were merged for ecryptfs during 2.6.34 development cycle.
Perhaps, those fixes were also back ported to 2.6.32, but Ubuntu 9.10
has 2.6.31, so it does not have them, and without them, it looks like
a beta-quality filesystem. So, make sure you have regular backups!
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-05-21 3:00 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-10 19:37 Help with a possibly corrupt repo Jonathan Leto
2010-05-10 20:17 ` Dmitry Potapov
2010-05-10 21:05 ` Jonathan Leto
2010-05-10 21:28 ` Dmitry Potapov
2010-05-20 14:57 ` Jonathan Leto
2010-05-21 2:59 ` Dmitry Potapov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).