All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: tiziano.mueller@stepping-stone.ch, xfs@oss.sgi.com
Subject: Re: Setting project quotas on special files
Date: Sun, 10 Nov 2013 02:46:20 -0800 (PST)	[thread overview]
Message-ID: <527F63FC.1050005@oracle.com> (raw)
In-Reply-To: <1384069188.245087.68.camel@storm>


On 11/10 2013 15:39 PM, Tiziano Müller wrote:
> Hi everyone
>
> It started with the following error:
>
>    dev # cp -al dvd dvd2
>    cp: cannot create hard link ‘dvd2’ to ‘dvd’: Invalid cross-device link
>
> "dvd" is in this case a symlink (but I also did the test with special
> devices).
This definitely would fail if you trying to create hard links across
volumes.
>
> What I did was: copy that symlink from somewhere else, trying to turn on
> project quotas on a parent directoy of that "dev" directory which gives
> me:
>
>   xfs_quota: skipping special file /var/foo/dev/dvd
symlink files will be skipped and xfs_quota consider it as special file
just like fifo, sock, etc...

If xfs_quota do check with follow symlinks, then the project id is potentially
applied to files on another filesystem. 

>
> When I examine the inode using xfs_db I get for my "dvd" symlink:
>
>   core.projid_lo = 0
>   core.projid_hi = 0
>
> When I create a new symlink "foo" (with the same uid+gid as "dvd") and
> examine it's inode using xfs_db:
>
>   core.projid_lo = 2398
>   core.projid_hi = 61
>
> What I therefore seem to encounter is the problem mentioned in xfs_quota
> for the project subcommand:
>
>   An attempt to create a hard link to a file in the tree will only succeed if the project identi‐
>        fier matches the project identifier for the tree.
>
> I could now use xfs_io to fix all special files once (since newly
> created ones will carry the project id directly), but why does
> "xfs_quota -x -c 'project -s test1' /var" skip special files if it is
> clearly possible and required to set the project id on them to have
> hardlinks working again within the project dir?
Sorry if I misunderstood your question, but the existing hard link files
would
notbe skipped IMO.  For the project subcommand, it means we could not create
hardlinks cross different project trees.

Thanks,
-Jeff

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-11-10 11:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  7:39 Setting project quotas on special files Tiziano Müller
2013-11-10 10:46 ` Jeff Liu [this message]
2013-11-10 15:06   ` Tiziano Müller
2013-11-11  6:43     ` Jeff Liu
2013-11-11  7:38       ` Tiziano Müller
2013-11-11  8:26         ` Jeff Liu

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=527F63FC.1050005@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=tiziano.mueller@stepping-stone.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.