Hi Matt, Pallissard, Matthew <[email protected]> wrote:
> I'm running into a few issues when transferring more data than RAM on the > box. Without really digging into it I've noticed that dd or cp seem to > crash once operating system cache eats up /roughly/ all the RAM on the box. Crash how? Do you have a backtrace or did it just hang? > This leads me to a few questions; > > 1. Anyone else run into this yet? I've just done a 5GiB AFS->NFS copy of a kernel build tree on a machine with ~3.5GiB availabile RAM with no problems. Are you copying a single file that's larger than memsize? > 2. Is there an issue tracker? I found the todo page, but haven't found > where to report bugs and related information. There's a kafs mailing list here: [email protected] I don't currently have an issue tracker - that's something I'll need to look into. Possibly you could use bugs.kernel.org if it's likely a kernel bug. > 3. Is there a "get involved page"? I'm not a great developer by any means > but I'm not completely incompetent either. Anything on the TODO lists is fair game. > - Do I just submit patches? Yes - though you might want to drop me an email first, just in case I have some conflicting stuff in the works. > Where to? Me and the linux-afs mailing list. > Is there a style guide, etc? More or less the kernel's coding style document. Note that there are three places to contribute to: kafs/AF_RXRPC in the kernel, kafs-client and kafs-utils. If you're good at python, kafs-utils needs some TLC; but in the client, aklog-kafs needs some work and there may need to be a PAM module. David _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
