[OpenAFS] buildbot and packages
Matt W. Benjamin
Mon, 17 Sep 2012 14:51:24 -0400 (EDT)
Well, we used the fuse rather extensively for locking and dirformat testing. It's experimental, but science experiment might be a little strong.
----- "Russ Allbery" <email@example.com> wrote:
> Troy Benjegerdes <firstname.lastname@example.org> writes:
> > I'm looking to get all the low-hanging fruit with unskilled
> > Particularly with regressions like this:
> > hozer@six:~/src/openafs-fuse-git/tests/fuse$
> -dynroot -fakestat -d -confdir
> /home/hozer/src/openafs-fuse-git/tests/fuse/conf -cachedir
> /home/hozer/src/openafs-fuse-git/tests/fuse/vcache -mountdir
> > FUSE library version: 2.8.6
> > nullpath_ok: 0
> > unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
> > INIT: 7.17
> > flags=0x0000047b
> > max_readahead=0x00020000
> > Starting AFS cache scan...found 0 non-empty cache files (0%).
> > afsd: All AFS daemons started.
> > Segmentation fault
> The fuse code currently in the tree was primarily a science experiment
> one developer and is not something that's really ready for production
> That's not to say this isn't a regression, and of course it would be
> to fix, but I'm completely unsurprised that it has issues. So far as
> know, no one is currently actively using the fuse code.
> Russ Allbery (email@example.com)
> OpenAFS-info mailing list
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104