Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

15
  • How long does a du -sm /home/* take? Commented Dec 15, 2024 at 16:38
  • For every share mounted over the network, try calculating the sub-totals for it at the system that is providing the share if at all possible. Tallying up disk usage per-user is likely to be much faster locally than over the network. Commented Dec 15, 2024 at 17:04
  • 2
    Which file system does /home use? You might find it more effective to use quotas for this, even if you don’t enforce limits. Commented Dec 15, 2024 at 17:17
  • 2
    @einpoklum enabling quotas doesn’t mean setting them — at its most basic, it enables tracking of disk usage per user (and optionally, per group and per “project”), without enforcing any limits. Commented Dec 15, 2024 at 17:26
  • 1
    that has nothing to do with the problem you have! no_root_squash means that users can write their own suid binaries (something that otherwise only root can do), and I'm not sure which kind of access control you have, but allowing an NFS client to tell the NFS server that they are, in fact, requesting files on behalf of root, would basically allow any machine that users control to access all files, no matter who they belong to. Commented Dec 15, 2024 at 19:22