From: Dave Chinner <david@fromorbit.com>
To: Varun Shastry <vrn.shastry@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Project quota behaviour on hardlinks
Date: Tue, 27 Nov 2012 08:50:32 +1100 [thread overview]
Message-ID: <20121126215032.GQ32450@dastard> (raw)
In-Reply-To: <CAB+GMR8yU4LaU7EwXboKQLDsGGD0N6EuDT4CgxYLpVFPsROKXg@mail.gmail.com>
On Mon, Nov 26, 2012 at 12:47:08PM +0530, Varun Shastry wrote:
> Hello everyone,
>
> I wanted to know how project quota behaves on hardlinks when created in
> different tree structures based on below 2 situations.
Test it and see.
> * Does it account twice if the file is hard linked in the same parent?
Hard links are only accounted once to the owner of the inode.
> * Does it account twice if the file is hard linked in a different tree
> which is also set quota in other project?
You can't hard link across directory tree quota boundaries - you'll
get EXDEV. Similarly for rename across directory tree boundaries.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-11-26 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 7:17 Project quota behaviour on hardlinks Varun Shastry
2012-11-26 21:50 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121126215032.GQ32450@dastard \
--to=david@fromorbit.com \
--cc=vrn.shastry@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox