diff options
Diffstat (limited to 'doc/bugs/unable_to_decommit_memory__58___Invalid_argument')
10 files changed, 0 insertions, 112 deletions
diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment deleted file mode 100644 index 15dde50f8..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 10""" - date="2016-12-19T19:53:11Z" - content=""" -The only way the files could be in lost+found is if the system crashed or -there was a disk error etc. Can't be due to this bug. So, it may be that -this bug did not actually cause any data loss. The screwed up symlinks could -have been caused by a disk error. -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_1_b76704adf6b6aa441a35bf9458d3950d._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_1_b76704adf6b6aa441a35bf9458d3950d._comment deleted file mode 100644 index 3fe7af8dd..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_1_b76704adf6b6aa441a35bf9458d3950d._comment +++ /dev/null @@ -1,15 +0,0 @@ -[[!comment format=mdwn - username="0xloem@0bd8a79a57e4f0dcade8fc81d162c37eae4d6730" - nickname="0xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="Corrupt Links Produced, Significant Data Loss" - date="2016-12-10T12:31:31Z" - content=""" -Additionally, I added a mess of files with this release of git-annex, and of the 200 files added, three of the links produced were corrupt. I'm still searching for where these files have gone to recover the data. - -The files look like this in `ls -l`, they were bup files: - - lrwxrwxrwx 1 user user 338 Jun 17 22:36 bup.git/objects/pack/pack-47b493a3bbbd22200d2b390c277e49ce713243cc.pack -> *??:?;J????????? - lrwxrwxrwx 1 user user 336 Jun 17 21:41 bup.git/objects/pack/pack-4d202b3929b187d4acaf1602526e7344eef1edc8.pack -> ?p???GWj??????ܥ??{b?#???>C??%??????~à???/hjT;?p??d?8??oyE?K?)6?uL+??h??&???SB}?'s??֫{?>^i?&?f??^{ш??aD??t4?C?sBTk>d6H???5h3?ڋ6fAa??=?r????j?????a8K??????????B?~????I͕?T7?Y??=???b?7C???鋤??8???\"?????#???M?????}z?A??9?C>?-?GD??7?ј;'P?H??ɑ??Zr?/U???W?G??3@\"??Ȧ?z?h???U??Ԇ???R??u??I????62??>@??@?a??x???}?????)d?G;(???m_?^3?????T - lrwxrwxrwx 1 user user 332 Jul 20 07:32 bup.git/objects/pack/pack-5328381f3b023c1356581c22d1e74d4eda0b46a3.idx -> c??'w??????????m?q#?ٱCO??o????ʃ?Ʃڌ??[???Ѐ??*?;.?c?N?0?????D$ o?r????8BGn?96gY?B?Z1?=???{??z?71????!aG?>?u)???i\?G[???:?Kk??%??.mu???n???K??ǚ????q&Z-?E???]??/?6???} -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_2_3469bfd3ba5e7935f3350f0bd78a0c94._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_2_3469bfd3ba5e7935f3350f0bd78a0c94._comment deleted file mode 100644 index 52932cd5e..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_2_3469bfd3ba5e7935f3350f0bd78a0c94._comment +++ /dev/null @@ -1,24 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 2""" - date="2016-12-10T15:13:44Z" - content=""" -I think that the "x86-32, for ancient kernels" build should avoid this -problem. <http://git-annex.branchable.com/install/Linux_standalone/> - -It's very surprising if this lead to symlinks being created that apparently -contain garbage in their link targets. Perhaps glibc is failing in a way -with the old kernel that leads to memory corruption? I have asked the GHC -developers if that could be the case in -<https://ghc.haskell.org/trac/ghc/ticket/12865> - -I hope that the content of your files is in fact somewhere under -`.git/annex/objects/` -- look around, and with some luck, you may find it. -Unfortunately, the information about, which object file goes with which -working tree has apparently been lost. (Also, you might check if these -symlinks have been staged in git; it's possible though unlikely that the -correct link target got staged in git.) - -I have filed a bug on Debian's ghc to get them to fast-track getting the -patch into ghc. <https://bugs.debian.org/847677> -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_3_886756620cdbb6ab838269fe2f00db4e._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_3_886756620cdbb6ab838269fe2f00db4e._comment deleted file mode 100644 index b5316c0de..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_3_886756620cdbb6ab838269fe2f00db4e._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="0xloem@0bd8a79a57e4f0dcade8fc81d162c37eae4d6730" - nickname="0xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="comment 3" - date="2016-12-11T00:26:41Z" - content=""" -Thank you so much for the prompt response. My system wouldn't shut down cleanly after this, either, so there may have been something else screwy going on. Still, I'll be using the build for ancient kernels exclusively for the near future. Thank you. -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_3_a4499b5506c0624f01d436e14ccce909._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_3_a4499b5506c0624f01d436e14ccce909._comment deleted file mode 100644 index 7aea3d6af..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_3_a4499b5506c0624f01d436e14ccce909._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 3""" - date="2016-12-11T19:35:21Z" - content=""" -All Linux standalone builds have been updated with a version of ghc that -has that bug fixed. Can you please upgrade and verify it's fixed? -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_4_2440227de9b6bc77ae1c73b69a36f7a5._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_4_2440227de9b6bc77ae1c73b69a36f7a5._comment deleted file mode 100644 index 801f70223..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_4_2440227de9b6bc77ae1c73b69a36f7a5._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="0xloem@0bd8a79a57e4f0dcade8fc81d162c37eae4d6730" - nickname="0xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="Verification" - date="2016-12-11T00:59:50Z" - content=""" -I saw the new comment on the download page and tried running `git annex test`. I can confirm that `git annex test` eventually segfaults using the normal build on my system, whereas it passes successfully using the 'ancient kernels' build. The version strings output for the two are identical. -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_5_c5e3dc25acf0cfb98d7068fe7f83e63a._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_5_c5e3dc25acf0cfb98d7068fe7f83e63a._comment deleted file mode 100644 index 9dec23b00..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_5_c5e3dc25acf0cfb98d7068fe7f83e63a._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="0xloem@0bd8a79a57e4f0dcade8fc81d162c37eae4d6730" - nickname="0xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="Nope a Fluke" - date="2016-12-11T13:26:29Z" - content=""" -Apologies. I can't reproduce the segfault running the tests again. The corruption and crashing seems to have been some horrifying fluke. -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment deleted file mode 100644 index 08e3364ca..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_7_e31ee8f49bf5f73620209c524f1edb3d._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="joey" - subject="""comment 7""" - date="2016-12-12T17:30:03Z" - content=""" -Can you please check if the current builds still have the "unable to -decommit memory" problem or not? - -(What it does after that error is probably nondeterministic, fixing that -error is the crucial thing.) -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_8_038a8e39ec0e91cb04af738eaf9095e1._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_8_038a8e39ec0e91cb04af738eaf9095e1._comment deleted file mode 100644 index 6d8994155..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_8_038a8e39ec0e91cb04af738eaf9095e1._comment +++ /dev/null @@ -1,9 +0,0 @@ -[[!comment format=mdwn - username="0xloem@0bd8a79a57e4f0dcade8fc81d162c37eae4d6730" - nickname="0xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="comment 8" - date="2016-12-13T15:52:34Z" - content=""" -It looks like the errors are gone. Thank you so much. -"""]] diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_9_6c3f4d165bca7a27683df286363bc19b._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_9_6c3f4d165bca7a27683df286363bc19b._comment deleted file mode 100644 index 42a14f12a..000000000 --- a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_9_6c3f4d165bca7a27683df286363bc19b._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="Coda" - date="2016-12-18T14:56:17Z" - content=""" -The missing files turned up in 'lost+found' the next time I ran fsck =) -"""]] |