Jeff has been busy today I see...
What is the current status about OpenAFS and Linux threads? I know the
thread situation on Linux sucks in general, just tell me your best
practice, ok? :-)
Ok. My best practice is to run fileservers on SPARC Solaris, thereby
avoiding the Linux threads mess, the h
On Thursday, March 17, 2005 12:33:12 PM +0100 Harald Barth
<[EMAIL PROTECTED]> wrote:
I suppose it's possible you could construct something that does this
using the convert-RO-to-RW functionality that is in very recent
servers. But I'd have to think about it for a lot longer to convince
myse
> I suppose it's possible you could construct something that does this using
> the convert-RO-to-RW functionality that is in very recent servers. But I'd
> have to think about it for a lot longer to convince myself that this would
> actually be stable.
Yes. Something like that would be nice.
On Tuesday, March 15, 2005 12:20:14 PM +0100 Harald Barth <[EMAIL PROTECTED]>
wrote:
cysteine# tail -1 BosLog
Mon Mar 14 18:15:08 2005: fs:vol exited on signal 6
Actually, signal 6 is SIGIOT, which generally means an abort.
It's possible an abort message was written, but went out to the beginnin
On Tuesday, March 15, 2005 12:20:14 PM +0100 Harald Barth <[EMAIL PROTECTED]>
wrote:
command-that-fails | vos restore example a foo -overwrite full
Now volume foo is gone on server but still exists in vldb. Why does
a vos restore first delete and then create the volume? Would it
not be better to
Hi everybody,
I think this behaviour needs improvement
Start with existing volume foo:
create volume example a foo 4711
Do a restore
command-that-fails | vos restore example a foo -overwrite full
Now volume foo is gone on server but still exists in vldb. Why does
a vos restore first dele
