[9fans] p9p vac issue
X-No-Archive: Yes This is not much of a solution to the problem, however I have temporarily resolved my issue by performing vac/unvac using my p9p tree from mid-March, and then resorting to the latest p9p for vacfs/9pfuse in order to mount my archives. For those researching the issue, I think some change between the middle of March and now is causing the inability of vac to write to a venti archive on p9p with the error: create bsize 8192 psize 8160vac: vacfscreate: vacfileroot: read too small: asked for 0 need at least 389 _ Windows Live helps you keep up with all your friends, in one place. http://go.microsoft.com/?linkid=9660826
Re: [9fans] p9p vac issue
Indeed, this works for me as well. I've just migrated the arenas, bloom and isect to another machine with a p9p tree from mid February and I had no problem unvacing my data there. And for what it's worth, checkindex on that machine didn't report any problem while it did on the machine with the recent p9p install (which gives me the same vac/unvac issues as the ones already reported by a few people). So the data seems to be ok, which is already quite a relief. Cheers, Mathieu --- Begin Message --- X-No-Archive: Yes This is not much of a solution to the problem, however I have temporarily resolved my issue by performing vac/unvac using my p9p tree from mid-March, and then resorting to the latest p9p for vacfs/9pfuse in order to mount my archives. For those researching the issue, I think some change between the middle of March and now is causing the inability of vac to write to a venti archive on p9p with the error: create bsize 8192 psize 8160vac: vacfscreate: vacfileroot: read too small: asked for 0 need at least 389 _ Windows Live helps you keep up with all your friends, in one place. http://go.microsoft.com/?linkid=9660826--- End Message ---
Re: [9fans] p9p venti problem
On Jun 12, 10:14Â am, m...@acm.jhu.edu (Venkatesh Srinivas) wrote: > > % unvac -t vac:8ab4746b0fb06da481158624afb7509cefc35e07 > > unvac: vacfsopen: read too small 1: asked for 0 need at least 300 > > > %venti/copy 'tcp!localhost!17034' 'tcp!localhost!17034' > > vac:8ab4746b0fb06da481158624afb7509cefc35e07 > >venti/copy: reading block > > (type 16): read asked for got > > da39a3ee5e6b4b0d3255bfef95601890afd80709 > > I think you've run into the same bug I did in > February:http://9fans.net/archive/2009/02/198 > Or at least a close cousin. > > da39a3ee5e6b4b0d3255bfef95601890afd80709 is the sha1sum of the empty > string; somehow someone is looking for the all-zero score instead... > > -- vs Hello, It seems like I've just hit the same issue: lejat...@oenone:~/tmp$ unvac -h localhost ../work/venti/20090605.vac unvac: vacfsopen: read too small 1: asked for 0 need at least 300 At first I thought the index was corrupted because I had to hard reboot that machine while venti was running. checkindex -f detects some errors but does not seem to be fixing them: lejat...@oenone:~/work/venti$ /usr/local/plan9/bin/venti/checkindex - f venti.conf /home/lejatorn/tmpisect checkindex: building entry list constructing entry list arena arenas00: 2554 entries [arenas01] sorting 2554 entries checkindex: checking 2554 entries at 16777216 # diff actual correct isect block 0x184000 > 04665caf88387b2a9f925ca5d958d2cfd5748d3c 10067426 0 724 1 isect block 0x1ae000 > 0558ba6343c0256c2daa851bb81dbd7fb2a2b9e7 10069700 0 2063 2 isect block 0x4b6000 > 16f19e6591bfe468f489c88fe0c6cf607c107c5c 10068499 8 1840 3 isect block 0x612000 > 1ecbb5af8ee870174e099e5c9bc84c944beec01f 10064704 0 744 1 isect block 0x65c000 > 207f10e6f8a66dab242b1f0d8226b0a18436ffcd 10067090 8 440 1 isect block 0xa7e000 > 386a02c7fe558550107853d9788ad72f2f9053f2 10068283 880 1 isect block 0xada000 > 3a7dc491bf6078e9d16c3fd6bad14d638a709c85 10070360 8 120 1 isect block 0xfae000 > 5682a0fb0a24fbf36bfb4308865ab45aa6bf3b15 10067991 0 835 1 isect block 0x127a000 > 66b430198ea34f4e734bde565804bd0be3f23dfd 10064925 8 240 1 isect block 0x147c000 > 7254aa4af20a94ea73ee46b9b7a419129131c0ad 10070255 880 1 isect block 0x1584000 > 784875610550ac6a10111c6d3266056f8e1c9171 10066161 0 740 1 isect block 0x160e000 > 7b6d56b5bf715fe3972bb0f614621f0cc90225c3 10067646 8 440 1 isect block 0x1676000 > 7dc3a7c680e0e8c1c61ce446cd645f57a619b409 10065348 0 1587 1 isect block 0x1774000 > 8384ca87c033a4c64e14894202d3570491f00f8d 10066882 0 678 1 isect block 0x186e000 > 892c639a60cdad7409482362d340afd5b7c7cd5e 10066385 0 813 1 isect block 0x1b36000 > 994fba051c5c1895417d15e993e1f4e4905df20d 10065818 0 477 1 isect block 0x1c36000 > 9f1b4cc34e917fc7a81b7bc35960e2e7467a8c19 10065959 0 673 1 isect block 0x1d0e000 > a3fde373beeb7d74007788fa2654436a7f260e0b 10068387 0 403 1 isect block 0x1fd2000 > b402d8db94260e233c6c0b7e4282dd0e77df9c87 10066647 0 811 1 isect block 0x2308000 > c6a3e8b8b8b181dfc25ce22df91cadb2a3b87f4b 10065133 0 706 1 isect block 0x2a82000 > f1ee1f851ab24bb5a2e7bb5ae7aa3a78c904e221 10070491 16 300 1 checkindex: 0 spurious entries, 21 missing, 0 wrong bloom filter: correct /usr/local/plan9/bin/venti/checkindex: errors found Is there any way I can recover any data at all? Would rebuilding unvac from an older pull of plan9port help ? Cheers, Mathieu
Re: [9fans] p9p vac issue
2009/6/22 Mathieu L. > Indeed, this works for me as well. > I've just migrated the arenas, bloom and isect to another machine with > a p9p tree from mid February and I had no problem unvacing my data > there. And for what it's worth, checkindex on that machine didn't report > any problem while it did on the machine with the recent p9p install > (which gives me the same vac/unvac issues as the ones already reported > by a few people). OK, so all I need now is to get my hands on an old copy of the p9p binaries... the only old ones I've got are carefully backed up inside the venti that I can't get at :) > So the data seems to be ok, which is already quite a relief. > > Cheers, > Mathieu -- Adrian
Re: [9fans] p9p vac issue
OK, so all I need now is to get my hands on an old copy of the p9p binaries... the only old ones I've got are carefully backed up inside the venti that I can't get at :) I'm not sure why you may need binaries as you say, but older source revs can be pulled from hg or cvs, also giving a chance to bisect where a bug may have been introduced. -Josh
Re: [9fans] p9p vac issue
if you can't get an old one from swtch.com, I can tar this mid-february tree I have - or rather only the necessary parts - and serve it to you if you want. Mathieu --- Begin Message --- 2009/6/22 Mathieu L. > Indeed, this works for me as well. > I've just migrated the arenas, bloom and isect to another machine with > a p9p tree from mid February and I had no problem unvacing my data > there. And for what it's worth, checkindex on that machine didn't report > any problem while it did on the machine with the recent p9p install > (which gives me the same vac/unvac issues as the ones already reported > by a few people). OK, so all I need now is to get my hands on an old copy of the p9p binaries... the only old ones I've got are carefully backed up inside the venti that I can't get at :) > So the data seems to be ok, which is already quite a relief. > > Cheers, > Mathieu -- Adrian --- End Message ---
[9fans] Snarf and Paste problem in acme
Hi all, I've got a problem doing a simple Snarf followed by a Paste in acme. I select the text using mouse button1, execute "Snarf" in the tag line with button 2, left-click again in one of the acme windows and click on "Paste" again with button 2. But no text is pasted. Also, a Paste following a "Cut" does not work. I can execute commands by using button 2, "Cut" always works and I can execute arbitrary non built-in commands such as "ls" with button 2. I run Plan 9 under VMWare Fusion on Mac OS X and do not have any other major problems so far. Any help is much appreciated. Cheers, -- /Manuel
Re: [9fans] p9p vac issue
On Mon, Jun 22, 2009 at 8:08 PM, Mathieu L. wrote: > if you can't get an old one from swtch.com, I can tar this mid-february > tree I have - or rather only the necessary parts - and serve it to you > if you want. > > Mathieu > > > -- Forwarded message -- > From: Adrian Tritschler > To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> > Date: Mon, 22 Jun 2009 21:33:22 +1000 > Subject: Re: [9fans] p9p vac issue > 2009/6/22 Mathieu L. >> >> Indeed, this works for me as well. > > >> >> I've just migrated the arenas, bloom and isect to another machine with >> a p9p tree from mid February and I had no problem unvacing my data >> there. And for what it's worth, checkindex on that machine didn't report >> any problem while it did on the machine with the recent p9p install >> (which gives me the same vac/unvac issues as the ones already reported >> by a few people). > > OK, so all I need now is to get my hands on an old copy of the p9p > binaries... the only old ones I've got are carefully backed up inside the > venti that I can't get at :) > >> >> So the data seems to be ok, which is already quite a relief. >> Did you guys get this message when building the june 22 p9p? vac.c:509: warning: sizeof(pointer) possibly incorrect in argument 3 regards fernan -- http://www.fernski.com
Re: [9fans] Snarf and Paste problem in acme
snarf in vmware doesn't work so well comment this # if(! test -f /dev/snarf) # aux/stub /dev/snarf # bind /mnt/vmware/snarf /dev/snarf in /rc/bin/aux/vmware On Mon, Jun 22, 2009 at 11:12 AM, Manuel Franceschini wrote: > Hi all, > > I've got a problem doing a simple Snarf followed by a Paste in acme. I > select the text using mouse button1, execute "Snarf" in the tag line > with button 2, left-click again in one of the acme windows and click > on "Paste" again with button 2. But no text is pasted. Also, a Paste > following a "Cut" does not work. I can execute commands by using > button 2, "Cut" always works and I can execute arbitrary non built-in > commands such as "ls" with button 2. > > I run Plan 9 under VMWare Fusion on Mac OS X and do not have any other > major problems so far. Any help is much appreciated. > > Cheers, > -- > /Manuel > > -- Federico G. Benavento
Re: [9fans] Snarf and Paste problem in acme
Great. I commented it in /bin/aux/vmware and that fixed the problem. Thanks a bunch! /Manuel On Mon, Jun 22, 2009 at 5:23 PM, Federico G. Benavento wrote: > snarf in vmware doesn't work so well > > comment this > > # if(! test -f /dev/snarf) > # aux/stub /dev/snarf > # bind /mnt/vmware/snarf /dev/snarf > > in /rc/bin/aux/vmware > > On Mon, Jun 22, 2009 at 11:12 AM, Manuel > Franceschini wrote: >> Hi all, >> >> I've got a problem doing a simple Snarf followed by a Paste in acme. I >> select the text using mouse button1, execute "Snarf" in the tag line >> with button 2, left-click again in one of the acme windows and click >> on "Paste" again with button 2. But no text is pasted. Also, a Paste >> following a "Cut" does not work. I can execute commands by using >> button 2, "Cut" always works and I can execute arbitrary non built-in >> commands such as "ls" with button 2. >> >> I run Plan 9 under VMWare Fusion on Mac OS X and do not have any other >> major problems so far. Any help is much appreciated. >> >> Cheers, >> -- >> /Manuel >> >> > > > > -- > Federico G. Benavento
Re: [9fans] p9p vac issue
On Mon, Jun 22, 2009 at 10:40 PM, Fernan Bolando wrote: > On Mon, Jun 22, 2009 at 8:08 PM, Mathieu L. wrote: >> if you can't get an old one from swtch.com, I can tar this mid-february >> tree I have - or rather only the necessary parts - and serve it to you >> if you want. >> >> Mathieu >> >> >> -- Forwarded message -- >> From: Adrian Tritschler >> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> >> Date: Mon, 22 Jun 2009 21:33:22 +1000 >> Subject: Re: [9fans] p9p vac issue >> 2009/6/22 Mathieu L. >>> >>> Indeed, this works for me as well. >> >> >>> >>> I've just migrated the arenas, bloom and isect to another machine with >>> a p9p tree from mid February and I had no problem unvacing my data >>> there. And for what it's worth, checkindex on that machine didn't report >>> any problem while it did on the machine with the recent p9p install >>> (which gives me the same vac/unvac issues as the ones already reported >>> by a few people). >> >> OK, so all I need now is to get my hands on an old copy of the p9p >> binaries... the only old ones I've got are carefully backed up inside the >> venti that I can't get at :) >> >>> >>> So the data seems to be ok, which is already quite a relief. >>> > > Did you guys get this message when building the june 22 p9p? > vac.c:509: warning: sizeof(pointer) possibly incorrect in argument 3 > looks like it's related to the error above. you might want to downgrade to http://swtch.com/plan9port/plan9port-20090609.tgz fernan -- http://www.fernski.com
Re: [9fans] p9p vac issue
> looks like it's related to the error above. you might want to downgrade to > http://swtch.com/plan9port/plan9port-20090609.tgz fortune tells me The most effective debugging tool is still careful thought, coupled with judiciously placed print statements. -Kernighan, 1978 i don't think this bug is going to be fixed without a bit of actual debugging. since your theories are rather easy to test, i would think it would be much easier to arrive at a solution via a frontal assault bwk style, rather than sniping at it from the safety of the mailing list. i promise, vac won't shoot back. even if you pull out gdb. i'm interested in what the actual bug is. - erik
