From: Nathan Scott <nscott@aconex.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: Sten Spans <sten@blinkenlights.nl>, xfs@oss.sgi.com
Subject: Re: xfs_quota project + symlinks
Date: Tue, 31 Oct 2006 09:24:03 +1100 [thread overview]
Message-ID: <1162247043.17754.160.camel@edge> (raw)
In-Reply-To: <2F2FC01C6C9DD207E49DFC0B@timothy-shimmins-power-mac-g5.local>
On Mon, 2006-10-30 at 15:39 +1000, Timothy Shimmin wrote:
> Hi,
>
> > If path is a symlink, then the project id is applied to a file
> > potentially on another filesystem. Wouldn't it be better to
> > add O_NOFOLLOW here ?
>
> You want it to error out if it is a symlink.
>
Thats not ideal. But some way to stay on the symlink's filesystem
is probably needed here, from the sound of it.
> I'm not that familiar with quotas (Nathan?, Donald?), but I would presume
> that since symlinks take up space depending on the symlink path, that they should
> have quota control on the space they take up.
If they require space to be allocated (i.e the symlink target is not
stored in the inode literal area), then that space allocation will be
subject to quota IIRC.
> In which case, one would actually not want to follow the symlink but rather
> apply a limit to that actual symlink inode.
*nod*
>
> But I agree, I doubt one wants to follow the symlinks - it would get rather
> confusing.
*nod*
cheers.
--
Nathan
next prev parent reply other threads:[~2006-10-30 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 13:31 xfs_quota project + symlinks Sten Spans
2006-10-26 13:45 ` Sten Spans
2006-10-30 5:39 ` Timothy Shimmin
2006-10-30 7:54 ` Sten Spans
2006-10-30 22:24 ` Nathan Scott [this message]
2006-10-31 1:08 ` Timothy Shimmin
2006-10-31 2:01 ` Nathan Scott
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=1162247043.17754.160.camel@edge \
--to=nscott@aconex.com \
--cc=sten@blinkenlights.nl \
--cc=tes@sgi.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