Jeff Blaine wrote:
> Just bringing this back from April 24th.
Nothing has changed since then.
smime.p7s
Description: S/MIME Cryptographic Signature
Just bringing this back from April 24th.
Derrick J Brashear wrote:
On Thu, 24 May 2007, Jeff Blaine wrote:
OpenAFS 1.4.4 client
# ./vos examine fs1-a
fs1-a 2023883361 RW 3 K On-line
fs1.mitre.org /vicepa
RWrite 2023883361 ROnly 0 Backup 202
Derrick J Brashear wrote:
On Thu, 24 May 2007, Jeff Blaine wrote:
OpenAFS 1.4.4 client
# ./vos examine fs1-a
fs1-a 2023883361 RW 3 K On-line
fs1.mitre.org /vicepa
RWrite 2023883361 ROnly 0 Backup 2023883363
MaxQuota 5000 K
Creati
On Thu, 24 May 2007, Jeff Blaine wrote:
OpenAFS 1.4.4 client
# ./vos examine fs1-a
fs1-a 2023883361 RW 3 K On-line
fs1.mitre.org /vicepa
RWrite 2023883361 ROnly 0 Backup 2023883363
MaxQuota 5000 K
CreationWed Dec 31 19:00:00 1
OpenAFS 1.4.4 client
# ./vos examine fs1-a
fs1-a 2023883361 RW 3 K On-line
fs1.mitre.org /vicepa
RWrite 2023883361 ROnly 0 Backup 2023883363
MaxQuota 5000 K
CreationWed Dec 31 19:00:00 1969
CopyWed May 23 16:38:4
It's going to be a volser bug or race at create time. There's no reason
anything else should fix it other than actually fixing the relevant code.
I looked at the code cursorily over the weekend but haven't gotten further
yet as work-work has taken precedence.
On Wed, 23 May 2007, Jeff Blaine
bash-3.2$ vos create fs1 a fs1-a
Volume 2023883358 created on partition /vicepa of fs1
bash-3.2$ vos examine fs1-a
fs1-a 2023883358 RW 2 K On-line
fs1.mitre.org /vicepa
RWrite 2023883358 ROnly 0 Backup 0
MaxQuota 5000 K
Jeff Blaine <[EMAIL PROTECTED]> writes:
> > No solution, but we see the same - apparently transarc
> > afs had a problem and all volumes created in that period
> > all have the epoch as their create time.
>
> Well, that's not what we're seeing.
>
> Any volume we create *today* on our OpenAFS s
> No solution, but we see the same - apparently transarc
> afs had a problem and all volumes created in that period
> all have the epoch as their create time.
Well, that's not what we're seeing.
Any volume we create *today* on our OpenAFS servers has
the UNIX epoch as the create date.
Our entir
On May 18, 2007, at 9:34 AM, Jeff Blaine wrote:
We just noticed that we have this same exact problem
for only the volumes we created since moving from IBM
AFS to OpenAFS on 12/7/2006 for our file/db servers.
CreationWed Dec 31 19:00:00 1969
I saw no solution posted to the original pos
We just noticed that we have this same exact problem
for only the volumes we created since moving from IBM
AFS to OpenAFS on 12/7/2006 for our file/db servers.
CreationWed Dec 31 19:00:00 1969
I saw no solution posted to the original poster's
thread. Anyone?
___
John Hascall wrote:
> So, excluding time travel, what might cause this:
>
> # vos create afs-5.iastate.edu /vicepc blah.de.blah
> # vos exam blah.de.blah
> blah.de.blah 538247009 RW 2 K On-line
> afs-5.iastate.edu /vicepc
> RWrite 538247009 ROnly 0
So, excluding time travel, what might cause this:
# vos create afs-5.iastate.edu /vicepc blah.de.blah
# vos exam blah.de.blah
blah.de.blah 538247009 RW 2 K On-line
afs-5.iastate.edu /vicepc
RWrite 538247009 ROnly 0 Backup 0
MaxQuota
13 matches
Mail list logo
