From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: xfs@oss.sgi.com
Cc: brian wince <bswince@gmail.com>
Subject: Re: xfs_quota unable to create project id's over 65535
Date: Tue, 16 Aug 2011 20:15:51 +0200 [thread overview]
Message-ID: <201108162015.51313.arekm@maven.pl> (raw)
In-Reply-To: <CAE-kmAw1m8HNn_sHpVx6DtTGCr4XdsiG5KM3FNnMe_fibjyaVw@mail.gmail.com>
On Tuesday 16 of August 2011, brian wince wrote:
> Hello,
> We use unix uids for project ids andnow have uids well over 65535.
> Is there a way to force xfs_quota to use project id's above the 64k
> boundary?
man xfs_admin (from recent xfsprogs) and read about projid32bit. Note that
after turning this on you won't be able to mount fs on kernels that don't
support projid32bit (<= 2.6.36) without hacks.
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-08-16 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 17:29 xfs_quota unable to create project id's over 65535 brian wince
2011-08-16 18:15 ` Arkadiusz Miskiewicz [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=201108162015.51313.arekm@maven.pl \
--to=arekm@maven.pl \
--cc=bswince@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