-----BEGIN PGP SIGNED MESSAGE-----
On 5/2/14, 2:07 PM, Martin Papik wrote:
>> You're right that this doesn't seem to be well described in
>> documentation, that's probably something we should address.
> Yup, any idea when? .... Also, I think it would be good to have a
> section on what to do when things go south and what to expect. E.g. I
> found out the hard way that xfs_check on a 2TB disk allocates 16G of
> memory, so now I'm running it with cgroup based limitations, otherwise
> I couldn't even open my emails now. I'm still not sure when to run
> xfs_check and when xfs_repair, etc. At least I haven't seen such docs.
> Maybe I missed them.
We have a lot of docs at http://xfs.org/index.php/XFS_Papers_and_Documentation
in publican/xml format, but Dave has been making noises about converting
that to asciidoc. In any case, the goal is documentation which is readily
available, version-controlled, for which patches may be submitted...
Like everything else, there are more things to do than there are hours
to do them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----