{"thread":{"id":"1910","subject":"'bad file' error updating from Linus","startedAt":"2005-09-22T11:40:13Z","lastAt":"2005-09-23T19:43:07Z","messageCount":6,"participants":["walt","porpen@gmail.com","Linus Torvalds","H. Peter Anvin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"9103","messageId":"dgu56t$d2p$1@sea.gmane.org","threadId":"1910","inReplyTo":null,"subject":"'bad file' error updating from Linus","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2005-09-22T11:40:13Z","receivedAt":"2005-09-22T11:40:13Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"cg-update this morning is giving me this error:\n\nreceiving file list ... done\nv2.6.14-rc2\n\nwrote 134 bytes  read 1116 bytes  833.33 bytes/sec\ntotal size is 738  speedup is 0.59\nTree change: 044a500e46742d39d22f1781cfb64ba93b463e39:e98c07b9eabedfb1d7ebef61af475bdebe1dd64d\nerror: unable to find e98c07b9eabedfb1d7ebef61af475bdebe1dd64d\nfatal: git-cat-file e98c07b9eabedfb1d7ebef61af475bdebe1dd64d: bad file\nerror: unable to find e98c07b9eabedfb1d7ebef61af475bdebe1dd64d\nfatal: git-cat-file e98c07b9eabedfb1d7ebef61af475bdebe1dd64d: bad file\nInvalid tree id: e98c07b9eabedfb1d7ebef61af475bdebe1dd64d\n\nIs this a kernel.org rsync problem, perhaps?\n\n(I'm running the latest releases of cogito and git from kernel.org.)\n"},{"id":"9107","messageId":"509c8057050922054272b823fe@mail.gmail.com","threadId":"1910","inReplyTo":"dgu56t$d2p$1@sea.gmane.org","subject":"Re: 'bad file' error updating from Linus","fromName":"","fromEmail":"porpen@gmail.com","sentAt":"2005-09-22T12:42:23Z","receivedAt":"2005-09-22T12:42:23Z","isPatch":false,"sender":{"key":"porpen@gmail.com","avatar":null},"body":"You aren't alone.  I had a look at http://www.kernel.org/git/  only to\nfind that the 2.6 kernel has been taken off the list...  /me thinks\nLinus is pushing an update as I type.\n\nOn a whim, I'll suggest we relax and go get some breakfast. ;-)   and\ntry again a little later...\n\nCheers!\n-P\n\nOn 9/22/05, walt <wa1ter@myrealbox.com> wrote:\n> cg-update this morning is giving me this error:\n>\n> receiving file list ... done\n> v2.6.14-rc2\n>\n> wrote 134 bytes  read 1116 bytes  833.33 bytes/sec\n> total size is 738  speedup is 0.59\n> Tree change: 044a500e46742d39d22f1781cfb64ba93b463e39:e98c07b9eabedfb1d7ebef61af475bdebe1dd64d\n> error: unable to find e98c07b9eabedfb1d7ebef61af475bdebe1dd64d\n"},{"id":"9139","messageId":"dgv8jv$amv$1@sea.gmane.org","threadId":"1910","inReplyTo":"509c8057050922054272b823fe@mail.gmail.com","subject":"Re: 'bad file' error updating from Linus","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2005-09-22T21:44:34Z","receivedAt":"2005-09-22T21:44:34Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"porpen@gmail.com wrote:\n> You aren't alone.  I had a look at http://www.kernel.org/git/  only to\n> find that the 2.6 kernel has been taken off the list...  /me thinks\n> Linus is pushing an update as I type...\n\nI think it was a disk failure, but no matter -- it's fixed now.\n\nFor the benefit of future googlers with the same 'bad file' error:\n\nAfter I repeated the cg-update (successfully) I was still left with\nthe 'bad file' error.  I tried 'cg-restore' and the error went away.\nVery nifty!\n"},{"id":"9145","messageId":"Pine.LNX.4.58.0509221630200.2553@g5.osdl.org","threadId":"1910","inReplyTo":"dgv8jv$amv$1@sea.gmane.org","subject":"Re: 'bad file' error updating from Linus","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-09-22T23:32:22Z","receivedAt":"2005-09-22T23:32:22Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 22 Sep 2005, walt wrote:\n> \n> I think it was a disk failure, but no matter -- it's fixed now.\n\nNope, it's not.\n\nIt just depends on which IP address you happen to get when you look at \nwww.kernel.org.\n\nwww.kernel.org resolves to two addresses:\n\n\tName:   zeus-pub.kernel.org\n\tAddress: 204.152.191.5\n\tName:   zeus-pub.kernel.org\n\tAddress: 204.152.191.37\n\nand the .5 address is working, but the .37 address has the broken mirror.\n\nI thought hpa took it out of service while it was re-syncing, but \napparently not. \n\n\t\tLinus\n"},{"id":"9150","messageId":"dgvjs3$4so$1@sea.gmane.org","threadId":"1910","inReplyTo":"dgv8jv$amv$1@sea.gmane.org","subject":"Re: 'bad file' error updating from Linus","fromName":"walt","fromEmail":"wa1ter@myrealbox.com","sentAt":"2005-09-23T00:56:34Z","receivedAt":"2005-09-23T00:56:34Z","isPatch":false,"sender":{"key":"wa1ter@myrealbox.com","avatar":null},"body":"walt wrote:\n[...]\n> After I repeated the cg-update (successfully) I was still left with\n> the 'bad file' error.  I tried 'cg-restore' and the error went away.\n\nOops -- correction!\n\nAfter encountering the same problem on a different machine, I find\nthat 'cg-reset' is the one which fixed the error, not 'cg-restore'.\n\nI believe that I tried both commands on the first machine, so I was\nuncertain which one actually did the fix.\n"},{"id":"9188","messageId":"43345ACB.1080201@zytor.com","threadId":"1910","inReplyTo":"Pine.LNX.4.58.0509221630200.2553@g5.osdl.org","subject":"Re: 'bad file' error updating from Linus","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2005-09-23T19:43:07Z","receivedAt":"2005-09-23T19:43:07Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Linus Torvalds wrote:\n> \n> Nope, it's not.\n> \n> It just depends on which IP address you happen to get when you look at \n> www.kernel.org.\n> \n> www.kernel.org resolves to two addresses:\n> \n> \tName:   zeus-pub.kernel.org\n> \tAddress: 204.152.191.5\n> \tName:   zeus-pub.kernel.org\n> \tAddress: 204.152.191.37\n> \n> and the .5 address is working, but the .37 address has the broken mirror.\n> \n> I thought hpa took it out of service while it was re-syncing, but \n> apparently not. \n> \n\nWell, it had resynched, but the time and date stamp on the \nrefs/heads/master file were correct - just the data wrong - so rsync \ndidn't flag the file.  I forced rsync --checksum and it's correct now.\n\n\t-hpa\n"}]}