Hello, Kevin.
I see from LU-13285 that Nathan D. pointed you at LU-13296. I left a comment
in the ticket as well. I think that you can try the patch from LU-13296 with
your reproducer.
-Cory
On 2/21/20, 10:08 AM, "lustre-discuss on behalf of Konzem, Kevin P"
On Feb 27, 2020, at 11:59, Peeples, Heath
mailto:hea...@hpc.msstate.edu>> wrote:
We have enabled project quotas, but the totals are way off from du as can be
seen below:
$ du -sh /work/project
1.5T /work/project
$ lfs quota -h -p 17115 /work/project
Disk quotas for prj 17115 (pid 17115):
Do you have hostname associated with the IP address so when you do a
reverse lookup it resolves the hostname?
Jeremy
On Thu, Feb 27, 2020, 11:41 AM Steve Brasier wrote:
> Thanks Jeremy. I will file a bug - I've confirmed that if I'm actually
> ssh'd in as root then `keyctl read` can read the
Dear Lustre Community,
Tomorrow, February 28th is the final day to submit your responses to the Lustre
Usage survey. We are looking for trends in Lustre usage to assist with future
planning on releases and will present the results at LUG. Note that all
questions are optional, so it is ok to
We have enabled project quotas, but the totals are way off from du as can be
seen below:
$ du -sh /work/project
1.5T /work/project
$ lfs quota -h -p 17115 /work/project
Disk quotas for prj 17115 (pid 17115):
Filesystem used quota limit grace files quota limit grace
/work/project 1.848G 47.31T
Thanks Jeremy. I will file a bug - I've confirmed that if I'm actually
ssh'd in as root then `keyctl read` can read the keys created by `mount -t
lustre ... -o skpath=`. So that's definitely an issue.
However, using this workaround of actually logging in as root I now get the
following when
