# Help with testing filesystem quota module **URL:** \ **Category:** Ansible Developer\ **Created:** [November 21, 2018, 10:39am UTC](https://forum.ansible.com/t/help-with-testing-filesystem-quota-module/29088 "2018-11-21T10:39:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Peter\_Hudec](https://avatars.discourse-cdn.com/v4/letter/p/8e8cbc/32.png) [@Peter\_Hudec](https://forum.ansible.com/u/Peter_Hudec)\ **Post date:** [November 21, 2018, 10:39am UTC](https://forum.ansible.com/t/help-with-testing-filesystem-quota-module/29088/1 "2018-11-21T10:39:46Z")
Hi, I was searching for filesystem quota module, but I did not found any ;( So I wrote one. The goal is to add this module in the ansible repository for everyone. code: [https://github.com/hudecof/ansible\_module\_quota](https://github.com/hudecof/ansible_module_quota) I would like you to ask to help a little bit. What do I need. Feel free to open issues or submit PR. 1) testing Right now it’s tested on Debian 9 and CentOS 7. The `quota` tools is used to parse actual quota. `quotatool` in current stable debian has bag, that makes the parsing impossible. See [https://github.com/ekenberg/quotatool/issues/7](https://github.com/ekenberg/quotatool/issues/7). It’s fixed in next release. Debian testing should be OK with this tool. Not sure about the `quota` output on older distributions releases or any other one. 2) documentation do the right documentation. At this moment this is big TODO.   regards     Peter ---
**Author:** ![Peter\_Hudec](https://avatars.discourse-cdn.com/v4/letter/p/8e8cbc/32.png) [@Peter\_Hudec](https://forum.ansible.com/u/Peter_Hudec)\ **Post date:** [November 28, 2018, 6:36am UTC](https://forum.ansible.com/t/help-with-testing-filesystem-quota-module/29088/2 "2018-11-28T06:36:23Z")
Thanks Alica, this helps a lot. Just another question. Is there a way how to debug. with ansible-doc? Seems I have there some kind of typo ;( (env) Peters-MBP:hudecof.module\_quota hudecof$ ansible-doc -M library quota ERROR! module quota missing documentation (or could not parse documentation): expected string or bytes-like object regards Peter