[9fans] err 2: arena creation time after last write time

[9fans] err 2: arena creation time after last write time

[Rodolfo (kix)]

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

Hi,

I have a new installation of Plan9 (fossil+venti) in a Qemu, in the first
reboot the venti starts and then the console start to show:

"err 2: arena creation time after last write time"


why?

thanks.


-- 
Rodolfo García "kix"

[-- Attachment #2: Type: text/html, Size: 311 bytes --]

Re: [9fans] err 2: arena creation time after last write time

[David Leimbach]

On 8/18/06, Rodolfo (kix) <rodolfogarciap@gmail.com> wrote:
> Hi,
>
> I have a new installation of Plan9 (fossil+venti) in a Qemu, in the first
> reboot the venti starts and then the console start to show:
>
> "err 2: arena creation time after last write time"
>
> why?

I had this until I set my timezone properly and used NTP to make sure
that the times were correct.

>
> thanks.
>
>
> --
> Rodolfo García "kix"

Re: [9fans] err 2: arena creation time after last write time

[Rodolfo (kix)]

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

Thanks,

I am spending to much time configuring the network, because I am using qemu.
Anyone can give me some tips to connect my p9 to something?

I am running qemu as:

qemu -net nic -net user -k es p9cpuserver

and the termrc is with ip/ipconfig (dhcp)

In the other hand, I try with macaddr and static ipaddr (configuring termrc
and /lib/ndb/local)

But I can ping the router of my network (192.168.1.1). why?

Thanks.

2006/8/18, David Leimbach <leimy2k@gmail.com>:
>
> On 8/18/06, Rodolfo (kix) <rodolfogarciap@gmail.com> wrote:
> > Hi,
> >
> > I have a new installation of Plan9 (fossil+venti) in a Qemu, in the
> first
> > reboot the venti starts and then the console start to show:
> >
> > "err 2: arena creation time after last write time"
> >
> > why?
>
> I had this until I set my timezone properly and used NTP to make sure
> that the times were correct.
>
> >
> > thanks.
> >
> >
> > --
> > Rodolfo García "kix"
>



-- 
Rodolfo García "kix"

[-- Attachment #2: Type: text/html, Size: 1440 bytes --]

Re: [9fans] err 2: arena creation time after last write time

[erik quanstrom]

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

what are your routes?
	; cat /net/iproute
there will be some /128 routes that are actually broadcast addresses.

you can run the attached command to get your ethernet devices, mac, address/mask
and network.  there's a similar program in /sys/src/libip called testreadipifc.c

- erik

[-- Attachment #2: ipifc.c --]
[-- Type: text/plain, Size: 1191 bytes --]

#include <u.h>
#include <libc.h>
#include <ip.h>

char *efmt = "%.2ux:%.2ux:%.2ux:%.2ux:%.2ux:%.2ux";
#pragma	varargck type	"e"	uchar*

int
ethfmt(Fmt *f)
{
	char buf[6*2+6];
	uchar *p;

	p = va_arg(f->args, uchar*);
	snprint(buf, sizeof buf, efmt, p[0], p[1], p[2], p[3], p[4], p[5], p[6]);
	va_end(p);
	return fmtstrcpy(f, buf);
}

void 
ipifcprint(int idx)
{
	Ipifc 	*ifc;
	Iplifc	*l;
	uchar 	eth[6];

	for(ifc = readipifc(0, 0, idx); ifc; ifc = ifc->next){
		print("%d:%s ", ifc->index, ifc->dev);
		if(myetheraddr(eth, ifc->dev) == 0)
			print("\t"	"%#e", eth);
		print("\n");
		for(l = ifc->lifc; l; l = l->next)
			print("\t" "%I%M" "\t" "%I\n", l->ip, l->mask, l->net);
	}

//	freeipifc(ifc);
}

void
usage(void)
{
	fprint(2, "usage: ipfic [interface number] ...\n");
	exits("usage");
}

void
main(int argc, char **argv){
	char* r;
	int i;

	ARGBEGIN{
	}ARGEND;

	fmtinstall('I', eipfmt);
	fmtinstall('M', eipfmt);
	fmtinstall('E', eipfmt);
	fmtinstall('e', ethfmt);
	if(*argv)
		for(; *argv; argv++){
			i = strtoul(*argv, &r, 0);
			if (*r)
				usage();
			ipifcprint(i);
		}
	else
		ipifcprint(-1);

	exits(0);
}

Re: [9fans] err 2: arena creation time after last write time

[Gorka guardiola]

qemu´s nat doesnt forward the ping responses.
try with something else like hget.

On 8/19/06, Rodolfo (kix) <rodolfogarciap@gmail.com> wrote:
> Thanks,
>
> I am spending to much time configuring the network, because I am using qemu.
> Anyone can give me some tips to connect my p9 to something?
>
> I am running qemu as:
>
> qemu -net nic -net user -k es p9cpuserver
>
> and the termrc is with ip/ipconfig (dhcp)
>
> In the other hand, I try with macaddr and static ipaddr (configuring termrc
> and /lib/ndb/local)
>
> But I can ping the router of my network ( 192.168.1.1). why?
>

-- 
- curiosity sKilled the cat

[9fans] Searching for text outside Acme

[yard-ape]

I'm curious: how did Plan9 users search through text output in a window (before they all used Acme)?  Plumb output to Sam?  Whither that old search feature from the old standalone unix 9term?

-Derek

Re: [9fans] Searching for text outside Acme

[Benn Newman]

[-- Attachment #1: Type: text/plain, Size: 510 bytes --]

yard-ape@telus.net wrote:
> I'm curious: how did Plan9 users search through text output in a window (before they all used Acme)?  Plumb output to Sam?  Whither that old search feature from the old standalone unix 9term?
> 
> -Derek
Beats me. I don't like having to use acme (it's a bother when I need to 
start it just to search through some text, so I'd like to know what I 
can *still* do. The real solution, of course, is to port less to Plan 9.
--
Benn Newman | http://www.tip9ug.jp/who/newmanbe/

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3639 bytes --]

Re: [9fans] Searching for text outside Acme

[Micah Stetson]

> can *still* do. The real solution, of course, is to port less to Plan 9.

There's a comment designed to get a response.

Have you tried 'grep foo /dev/text', or is that not what you wanted?
people talk about adding look to the button-2 menu every once in a
while:

http://www.google.com/search?q=site%3A9fans.net+%22searching+in+rio+terminal+windows%22

I thought somebody made a patch once, but I can't find it.

Micah

Re: [9fans] Searching for text outside Acme

[Benn Newman]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

Micah Stetson wrote:
>> can *still* do. The real solution, of course, is to port less to Plan 9.
I hope you know that that was a joke.
> There's a comment designed to get a response.
But, of course.
> Have you tried 'grep foo /dev/text', or is that not what you wanted?
A typical use (for me) for wanting to search is man pages (some of them 
are rather long). I don't care where the word is, just what comes 
after/around it.
> people talk about adding look to the button-2 menu every once in a
> while:
(not using Plan 9 right now, shame on me) I think it is. From reading 
the documentation, I don't understand what it does.
--
Benn Newman - http://www.tip9ug.jp/who/newmanbe

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3639 bytes --]

Re: [9fans] Searching for text outside Acme

[Micah Stetson]

> >> can *still* do. The real solution, of course, is to port less to Plan 9.
> I hope you know that that was a joke.

I figured it was, but I neglected to add smileys to my response.

Micah

Re: [9fans] Searching for text outside Acme

[yard-ape]

"Micah Stetson" <micah@stetsonnet.org> wrote:

> Have you tried 'grep foo /dev/text', or is that not what you wanted?
> people talk about adding look to the button-2 menu every once in a
> while...

Well, if Mr. Pike says "Look" would crowd button 2, then I drop it.  But how does one jump to a string in a man page without visually scanning it from top to bottom (for example)?  Plumbing the text 'man(1)' to sam works alright; but I thought there might be a way to leverage the text window's noscroll behaviour a little more.

-Derek

Re: [9fans] Searching for text outside Acme

[Francisco J Ballesteros]

Using acme for doing everything (to honor its name) works just fine.
After you read a man page, all the refs in there are ready for button-3.

I found acme incovenient time ago when I was using it like I used other
editors in unix. As soon as I started to use acme for everything, my feeling
changed. But in any case, feelings about editors are a religion,
aren´t they? :-)

On 8/19/06, yard-ape@telus.net <yard-ape@telus.net> wrote:
> "Micah Stetson" <micah@stetsonnet.org> wrote:
>
> > Have you tried 'grep foo /dev/text', or is that not what you wanted?
> > people talk about adding look to the button-2 menu every once in a
> > while...
>
> Well, if Mr. Pike says "Look" would crowd button 2, then I drop it.  But how does one jump to a string in a man page without visually scanning it from top to bottom (for example)?  Plumbing the text 'man(1)' to sam works alright; but I thought there might be a way to leverage the text window's noscroll behaviour a little more.
>
> -Derek
>
>

Re: [9fans] Searching for text outside Acme

[Charles Forsyth]

> it's a bother when I need to 
> start [acme] just to search through some text

usually, i start a big acme with frames populated from last time, when i log in,
so it's always there, ready for work.  agrep is useful there.

Re: [9fans] Searching for text outside Acme

[erik quanstrom]

in the spirit of smacme...

if you're using p9p, i put a copy of 9term with b3 menu items for forward and reverse
searching.  i but a posixthreads binary there too.  /n/sources/contrib/quanstro/9term.look(.tar)?.bz2
the reason for the binary is that this was built for a very old version of p9p (before
russ added the per-window devdraw.)  so i'm not sure if it will compile anymore.

i used to use this quite a bit, but it, like linux, has fallen into disuse here.  i just didn't have 
the heart to put that into rio.

- erik

On Sat Aug 19 13:34:10 CDT 2006, newmanbe@sdf.lonestar.org wrote:

> yard-ape@telus.net wrote:
> > I'm curious: how did Plan9 users search through text output in a window (before they all used Acme)?  Plumb output to Sam?  Whither that old search feature from the old standalone unix 9term?
> > 
> > -Derek
> Beats me. I don't like having to use acme (it's a bother when I need to 
> start it just to search through some text, so I'd like to know what I 
> can *still* do. The real solution, of course, is to port less to Plan 9.
> --
> Benn Newman | http://www.tip9ug.jp/who/newmanbe/

Re: [9fans] Searching for text outside Acme

[yard-ape]

erik quanstrom <quanstro@quanstro.net> wrote:

> in the spirit of smacme...
>
> if you're using p9p, i put a copy of 9term with b3 menu items for forward and reverse
> searching.  i but a posixthreads binary there too.  /n/sources/contrib/quanstro/9term.look(.tar)?.bz2

Thanks, Erik; that'll do very nicely.

Re: [9fans] err 2: arena creation time after last write time

[Ronald G Minnich]

here's how I run qemu so as to get things going. This allows me to 
drawterm into it.

qemu qemu.vesaroot &

Gets me a cpu kernel going

sleep 5 && dhcpd -d

gets me the dhcpd

a run looks like this:

[root@q plan9]# qemu qemu.vesaroot & sleep 5&& dhcpd -d
[1] 4674
Connected to host network interface: tun1
Could not open '/dev/kqemu' - QEMU acceleration layer not activated
Internet Systems Consortium DHCP Server V3.0.2-RedHat
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 17 leases to leases file.
Listening on LPF/tun1/46:9c:6d:94:f5:1f/172.20.0/24
Sending on   LPF/tun1/46:9c:6d:94:f5:1f/172.20.0/24

No subnet declaration for ath0 (192.168.0.104).
** Ignoring requests on ath0.  If this is not what
    you want, please write a subnet declaration
    in your dhcpd.conf file for the network segment
    to which interface ath0 is attached. **

Sending on   Socket/fallback/fallback-net
DHCPDISCOVER from 52:54:00:12:34:56 via tun1
DHCPOFFER on 172.20.0.2 to 52:54:00:12:34:56 via tun1
Dynamic and static leases present for 172.20.0.2.
Remove host declaration qemu or remove 172.20.0.2
from the dynamic address pool for 172.20.0/24
DHCPREQUEST for 172.20.0.2 (172.20.0.1) from 52:54:00:12:34:56 via tun1
DHCPACK on 172.20.0.2 to 52:54:00:12:34:56 via tun1


(note the DHCPREQUEST -- that's my plan 9)
(the error message is unimportant)

OK, what's the config look like? dhcpd.conf:
subnet 172.20.0.0 netmask 255.255.255.0 {
               range 172.20.0.2 172.20.0.2 ;
               default-lease-time 600;
                  max-lease-time 7200;
               option subnet-mask 255.255.255.0;
                 option routers 172.20.0.1;
             }
host qemu {
         hardware ethernet 52:54:00:12:34:56;
         fixed-address xtest;
}

xtest is (from /etc/hosts):
172.20.0.2 xtest


ok but how did tun1 get configured? You need to set up /etc/qemu-ifup

[root@q etc]# cat /etc/qemu-ifup
#!/bin/sh
tun=$1
sudo /sbin/ifconfig $1 172.20.0.1
sudo /sbin/iptables -N nat
sudo /sbin/iptables -t nat -F
sudo /sbin/iptables -t nat -A POSTROUTING -s 172.20.0.1 -j MASQUERADE
sudo /sbin/iptables -t nat -A POSTROUTING -d 172.20.0.1 -o $tun
sudo echo 1 > /proc/sys/net/ipv4/ip_forward
[root@q etc]#


this allows me to drawterm into the plan 9 cpu server running on my laptop.

If this all works, then put it in the wiki :-) This is on FC4.

ron

Re: [9fans] err 2: arena creation time after last write time

[Rodolfo (kix)]

[-- Attachment #1: Type: text/plain, Size: 4737 bytes --]

Thanks Ronald,

This is my new method ;-) and I can use ping :-)
If any thinks is ok, I can write it in the wiki.

slds.

- - - - - - - -

Installing Plan9 network for QEMU (Linux)

Do you need:

* Support for tunneling in kernel, with 802.1q:

tun: "Network device support" -> "Universal TUN/TAP device driver support"
bridging: "Networking options" -> "802.1d Ethernet Bridging"

* The bridge-utils package

First, load the Tunneling kernel support as modules

add "tun" to /etc/modules

Load it now (do not reboot ;-)): modprobe tun

* Create this script:

darky:~# cat kixconf
IFACE=eth0
BRIF=br0
IPORIG=`/sbin/ifconfig $IFACE | grep "inet addr" | cut -d: -f2 | cut -d" "
-f1`
IPGW=`netstat -nr | grep ^"0.0.0.0" | awk -F" " '{print $2} '`
IPBCAST=`/sbin/ifconfig $IFACE | grep "Bcast" | cut -d: -f3 | cut -d" " -f1`

echo "Interface = " $IFACE
echo "Bridge if = " $BRIF
echo "IP = " $IPORIG
echo "Gateway = " $IPGW
echo "Broadcast = " $IPBCAST

ifconfig $IFACE down
brctl addbr $BRIF
ifconfig $IFACE 0.0.0.0 promisc up
ifconfig $BRIF $IPORIG netmask 255.255.255.0 broadcast $IPBCAST up
brctl stp $BRIF off
brctl setfd $BRIF 1
brctl sethello $BRIF 1
brctl addif $BRIF $IFACE
route add default gw $IPGW
darky:~#

Now, configure /etc/qemu-ifup, and set the +x bit (chmod 755 /etc/qemu-ifup)
like this:

darky:~# ls -l /etc/qemu-ifup
-rwxr-xr-x 1 root root 60 2006-08-19 12:57 /etc/qemu-ifup
darky:~# cat /etc/qemu-ifup
#!/bin/sh
ifconfig $1 0.0.0.0 promisc up
brctl addif br0 $1
darky:~#

Now, you can use your Plan9 as a physical node in your network, then
configure the Plan9 scripts as
http://plan9.bell-labs.com/wiki/plan9/Network_configuration/index.html

For boot the Plan 9 you shoud use this command:

/usr/bin/qemu -m 128 -hda '' -net nic,vlan=0,macaddr=00:11:22:33:44:55 -net
tap,vlan=0,ifname= -localtime &

slds.

2006/8/19, Ronald G Minnich <rminnich@lanl.gov>:
>
> here's how I run qemu so as to get things going. This allows me to
> drawterm into it.
>
> qemu qemu.vesaroot &
>
> Gets me a cpu kernel going
>
> sleep 5 && dhcpd -d
>
> gets me the dhcpd
>
> a run looks like this:
>
> [root@q plan9]# qemu qemu.vesaroot & sleep 5&& dhcpd -d
> [1] 4674
> Connected to host network interface: tun1
> Could not open '/dev/kqemu' - QEMU acceleration layer not activated
> Internet Systems Consortium DHCP Server V3.0.2-RedHat
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
> Wrote 0 deleted host decls to leases file.
> Wrote 0 new dynamic host decls to leases file.
> Wrote 17 leases to leases file.
> Listening on LPF/tun1/46:9c:6d:94:f5:1f/172.20.0/24
> Sending on   LPF/tun1/46:9c:6d:94:f5:1f/172.20.0/24
>
> No subnet declaration for ath0 (192.168.0.104).
> ** Ignoring requests on ath0.  If this is not what
>     you want, please write a subnet declaration
>     in your dhcpd.conf file for the network segment
>     to which interface ath0 is attached. **
>
> Sending on   Socket/fallback/fallback-net
> DHCPDISCOVER from 52:54:00:12:34:56 via tun1
> DHCPOFFER on 172.20.0.2 to 52:54:00:12:34:56 via tun1
> Dynamic and static leases present for 172.20.0.2.
> Remove host declaration qemu or remove 172.20.0.2
> from the dynamic address pool for 172.20.0/24
> DHCPREQUEST for 172.20.0.2 (172.20.0.1) from 52:54:00:12:34:56 via tun1
> DHCPACK on 172.20.0.2 to 52:54:00:12:34:56 via tun1
>
>
> (note the DHCPREQUEST -- that's my plan 9)
> (the error message is unimportant)
>
> OK, what's the config look like? dhcpd.conf:
> subnet 172.20.0.0 netmask 255.255.255.0 {
>                range 172.20.0.2 172.20.0.2 ;
>                default-lease-time 600;
>                   max-lease-time 7200;
>                option subnet-mask 255.255.255.0;
>                  option routers 172.20.0.1;
>              }
> host qemu {
>          hardware ethernet 52:54:00:12:34:56;
>          fixed-address xtest;
> }
>
> xtest is (from /etc/hosts):
> 172.20.0.2 xtest
>
>
> ok but how did tun1 get configured? You need to set up /etc/qemu-ifup
>
> [root@q etc]# cat /etc/qemu-ifup
> #!/bin/sh
> tun=$1
> sudo /sbin/ifconfig $1 172.20.0.1
> sudo /sbin/iptables -N nat
> sudo /sbin/iptables -t nat -F
> sudo /sbin/iptables -t nat -A POSTROUTING -s 172.20.0.1 -j MASQUERADE
> sudo /sbin/iptables -t nat -A POSTROUTING -d 172.20.0.1 -o $tun
> sudo echo 1 > /proc/sys/net/ipv4/ip_forward
> [root@q etc]#
>
>
> this allows me to drawterm into the plan 9 cpu server running on my
> laptop.
>
> If this all works, then put it in the wiki :-) This is on FC4.
>
> ron
>



-- 
Rodolfo García "kix"

[-- Attachment #2: Type: text/html, Size: 7842 bytes --]

Re: [9fans] err 2: arena creation time after last write time

[Gorka guardiola]

On 8/18/06, Ronald G Minnich <rminnich@lanl.gov> wrote:

> Connected to host network interface: tun1
> Could not open '/dev/kqemu' - QEMU acceleration layer not activated

You are not using kqemu!!. It used to be really unstable, but it is
is stable enough now (at least for me). without it I cant use qemu because
it is too slow...
-- 
- curiosity sKilled the cat

[9fans] test command is broken

[Richard Miller]

The patch applied to the test(1) command on 12 August was
incorrect, as shown by this example:

term% test 1 -gt 2 -o 3 -lt 4 && echo yes
yes
term% test 1 -lt 2 -o 3 -lt 4 && echo yes
test: unexpected operator/operand: 3
term% 

Because the -a and -o operators don't necessarily
evaluate their right-hand argument, it's wrong to assume
that  there should be no arguments remaining when the
top-level expresssion evaluation returns.

The result is not just a spurious error message but possibly
an incorrect truth status, so I would suggest that anyone who
has pulled from sources since 12 August should revert to the
previous version of /386/bin/test.

-- Richard

Re: [9fans] err 2: arena creation time after last write time

[csant]

Hola,

> I have a new installation of Plan9 (fossil+venti) in a Qemu, in the first
> reboot the venti starts and then the console start to show:
>
> "err 2: arena creation time after last write time"
>
> why?

I recently had that problem after a clean install of Plan 9 fossil+venti  
because there was a network error and the time could not be correctly  
sync'ed. That network problem showed up only in the fossil+venti  
installation and not the fossil one.

/c

Re: [9fans] err 2: arena creation time after last write time

[John Floren]

On 8/18/06, csant <csant@csant.info> wrote:
> Hola,
>
> > I have a new installation of Plan9 (fossil+venti) in a Qemu, in the first
> > reboot the venti starts and then the console start to show:
> >
> > "err 2: arena creation time after last write time"
> >
> > why?
>
> I recently had that problem after a clean install of Plan 9 fossil+venti
> because there was a network error and the time could not be correctly
> sync'ed. That network problem showed up only in the fossil+venti
> installation and not the fossil one.
>
> /c
>
So, does this lead to big problems with Venti? I've wondered this
before--what if your clock gets mis-set, Venti makes an archive, and
then you reset your clock, but there's suddenly an archive /from the
future/! (cue Twilight Zone theme)
Maybe I'm just making it into a Y2K type thing.

John
-- 
"The first thing we do, let's kill all the lawyers" -- Shakespeare, Henry VI

Re: [9fans] err 2: arena creation time after last write time

[csant]

>> > I have a new installation of Plan9 (fossil+venti) in a Qemu, in the  
>> first
>> > reboot the venti starts and then the console start to show:
>> >
>> > "err 2: arena creation time after last write time"
>> >
>> > why?
>>
>> I recently had that problem after a clean install of Plan 9 fossil+venti
>> because there was a network error and the time could not be correctly
>> sync'ed. That network problem showed up only in the fossil+venti
>> installation and not the fossil one.
>>
>> /c
>>
> So, does this lead to big problems with Venti? I've wondered this
> before--what if your clock gets mis-set, Venti makes an archive, and
> then you reset your clock, but there's suddenly an archive /from the
> future/! (cue Twilight Zone theme)

I had just been understanding that venti does a dump at a given time, and  
stores it in something like
	/n/dump/<year>/<monthday>/
The only problem I could see here is if you dump twice on the same day,  
i.e. once in a future date, and then, after resetting your clock, on the  
right date once you reach it. How does venti handle that?

/c

Re: Re: [9fans] err 2: arena creation time after last write time

[andrey mirtchovski]

> The only problem I could see here is if you dump twice on the same day,
> i.e. once in a future date, and then, after resetting your clock, on the
> right date once you reach it. How does venti handle that?

plan9% 9fs dump
plan9% ls -l /n/dump/*
d-r-xr-xr-x M 36820 adm adm 0 Jun 15 14:46 /n/dump/2006/0615
d-r-xr-xr-x M 36820 adm adm 0 Jun 19 10:11 /n/dump/2006/0619
d-r-xr-xr-x M 36820 adm adm 0 Jun 19 11:47 /n/dump/2006/0619.1
d-r-xr-xr-x M 36820 adm adm 0 Jun 20 04:00 /n/dump/2006/0620

Re: Re: [9fans] err 2: arena creation time after last write time

[John Floren]

On 8/18/06, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> > The only problem I could see here is if you dump twice on the same day,
> > i.e. once in a future date, and then, after resetting your clock, on the
> > right date once you reach it. How does venti handle that?
>
> plan9% 9fs dump
> plan9% ls -l /n/dump/*
> d-r-xr-xr-x M 36820 adm adm 0 Jun 15 14:46 /n/dump/2006/0615
> d-r-xr-xr-x M 36820 adm adm 0 Jun 19 10:11 /n/dump/2006/0619
> d-r-xr-xr-x M 36820 adm adm 0 Jun 19 11:47 /n/dump/2006/0619.1
> d-r-xr-xr-x M 36820 adm adm 0 Jun 20 04:00 /n/dump/2006/0620
>
Heck, I think I've had that happen for me. I believe I ran "vac /" or
something like that, some time after the daily snapshot. Not sure if
that's how vac works, or if it was due to a mis-set clock...


John
-- 
"The first thing we do, let's kill all the lawyers" -- Shakespeare, Henry VI

Re: Re: [9fans] err 2: arena creation time after last write time

[csant]

>> The only problem I could see here is if you dump twice on the same day,
> d-r-xr-xr-x M 36820 adm adm 0 Jun 19 10:11 /n/dump/2006/0619
> d-r-xr-xr-x M 36820 adm adm 0 Jun 19 11:47 /n/dump/2006/0619.1
Neat, thank you :)
/c