4 thoughts on “90235”

  1. Re: So how bad is openafs ??

    The server side code is actually not too bad. There’s some ugliness, but it’s not any worse than any other ancient code. And there’s actually work on modernizing it (*gasp* prototypes 🙂

    The client side, though, sucks ass IMNSHO. I haven’t looked at the Solaris client code, much, but there’s enough “common” code that’s ifdef’d to high hell that it’s just extremely painful to actually track down the root source of problems. Preprocessors are definitely your friends, but it’s still pretty convoluted.

    And then, the Linux client code appears to have been written by monkeys and shows a lack of understanding of how the VFS works. I’m no expert on the matter, but I can definitely tell when some things are majorly out of whack.

    But for distributed networked filesystems, AFS is the best thing out there :/

  2. Re: So how bad is openafs ??

    hmm, so the best bet might be to use openafs as the server, arla as the client ??

    thanks 🙂

  3. Re: So how bad is openafs ??

    arla is its own can of worms… it tends to occasionally rx storm the servers and also only caches whole files, which is a bit of a problem if you want to have large-ish files in AFS.

Comments are closed.