On Wed, 16 Sep 1998, Peter J. Braam wrote:

> Troy,
> 
> Whoops: I think you have hosed your volume (I _did_ warn you to first make
> the cache bigger).   This is perhaps the buffer cache corruption which
> will be gone in 4.8.

Heh... I thought you meant make the cache big or performance will be bad
;)    I'm happy to hear that this is a known bug.. So basically, the moral
of the story is 'Don't do anything while cfs wd that will come anywhere
near filling the cache' ?

Btw, I don't have anything on this volume except the untarred linux stuff.
Also, what's the ETA on 4.8? Thanks again.

> 
> What I would do is 
> 
> 1. copy valuable stuff elsewhere - on client
> 2. purgevol_rep volname 
> 3. createvol_rep .........
> 
> - Peter -
> 
> On Wed, 16 Sep 1998, Troy Benjegerdes wrote:
> 
> > On Wed, 16 Sep 1998, Peter J. Braam wrote:
> > 
> > > Yes, this is a known factor of 50 slower.  But try it after 
> > > 
> > > cfs wd (make your cache large first).  I think you'll be pretty impressed.
> > > 
> > > - Peter -
> > > 
> > 
> > Well, it is faster, but I prefer correct over fast ;)
> > 
> > I first tried this trick with the original 30 MB cache and tried to rm -rf
> > the original linux tree I untarred. It was quite fast until I started
> > getting 'no space left on device' errors. So, thinking the cache was to
> > small I re-inited venus with a 100MB cache, and the rm worked ..
> > 
> > Now I get these errors:
> > I don't know where the original error was (it scrolled by too fast)
> > 
> > (and yes, I have clog'd in and have tokens..)
> > 
> > tar: linux/include/asm-arm/limits.h: Could not create file: Not a directory
> > linux/include/asm-arm/vga.h
> > tar: linux/include/asm-arm/vga.h: Could not create file: Not a directory
> > linux/include/asm-arm/mm-init.h
> > tar: linux/include/asm-arm/mm-init.h: Could not create file: Not a directory
> > linux/include/asm-arm/mman.h 
> > tar: linux/include/asm-arm/mman.h: Could not create file: Not a directory
> > linux/include/asm-arm/param.h       
> > 
> > I haven't so far been able to get cfs wd working reliably. It seems to
> > work for a small to medium amount of stuff, but not for large amounts of
> > activity.
> > 
> > Any hints on what to do?
> > 
> > --------------------------------------------------------------------------
> > | Troy Benjegerdes    |    troybenj_at_iastate.edu    |    hozer_at_drgw.net   |
> > |    Unix is user friendly... You just have to be friendly to it first.  |
> > | This message composed with 100% free software.    http://www.linux.org |
> > --------------------------------------------------------------------------
> > 
> 

--------------------------------------------------------------------------
| Troy Benjegerdes    |    troybenj_at_iastate.edu    |    hozer_at_drgw.net   |
|    Unix is user friendly... You just have to be friendly to it first.  |
| This message composed with 100% free software.    http://www.linux.org |
--------------------------------------------------------------------------