I see only 4 pdfs now with slightly different titles to the previous 5 pdfs
available with 4.2.0. Just checking there are only supposed to be 4 now?
Greg
___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listi
The GID selection rules for account creation are Linux distribution specific.
It sounds like you are familiar with Red Hat, where I think this idea of
GID=UID started.
sles12sp1-brc:/dev/disk/by-uuid # useradd testout
sles12sp1-brc:/dev/disk/by-uuid # grep testout /etc/passwd
testout:x:1001:100:
i can't contribute much to the usefulness of tracking primary or secondary
group. depending on who you ask you get a 50/50 answer why its great or
broken either way.
Jonathan explanation was correct, we only track/enforce primary groups , we
don't do anything with secondary groups in regards to quo
JAB,
Our scratch filesystem uses user and group quotas. It started out as a
traditional scratch filesystem but then we decided (for better or worse) to
allow groups to purchase quota on it (and we don’t purge it, as many sites do).
We have many users in multiple groups, so if this is not worki
On 03/08/16 19:34, Buterbaugh, Kevin L wrote:
Hi Jaime / Sven,
If Jaime’s interpretation is correct about user1 continuing to be able
to write to “group2” files even though that group is at their hard
limit, then that’s a bug that needs fixing. I haven’t tested that
myself, and we’re in a downt
JAB,
The set group id bit is tangential to my point. I expect GPFS to count any
files a user owns against their user quota. If they are a member of multiple
groups then I also expect it to count it against the group quota of whatever
group is associated with that file. I.e., if they do a chg
On 03/08/16 19:06, Buterbaugh, Kevin L wrote:
Hi Sven,
Wait - am I misunderstanding something here? Let’s say that I have
“user1” who has primary group “group1” and secondary group “group2”.
And let’s say that they write to a directory where the bit on the
directory forces all files created in
Hi Jaime / Sven,
If Jaime’s interpretation is correct about user1 continuing to be able to write
to “group2” files even though that group is at their hard limit, then that’s a
bug that needs fixing. I haven’t tested that myself, and we’re in a downtime
right now so I’m a tad bit busy, but if I
Quoting "Buterbaugh, Kevin L" :
Hi Sven,
Wait - am I misunderstanding something here? Let?s say that I have
?user1? who has primary group ?group1? and secondary group ?group2?.
And let?s say that they write to a directory where the bit on the
directory forces all files created in tha
Hi Sven,
Wait - am I misunderstanding something here? Let’s say that I have “user1” who
has primary group “group1” and secondary group “group2”. And let’s say that
they write to a directory where the bit on the directory forces all files
created in that directory to have group2 associated wit
I guess I have a bit of a puzzle to solve, combining quotas on
filesets, paths and USR/GRP attributes
So much for the "standard" built-in linux account creation script, in
which by default every new user is created with primary GID=UID,
doesn't really help any of us.
Jaime
Quoting "Jona
On 03/08/16 17:22, Jaime Pinto wrote:
Suppose I want to set both USR and GRP quotas for a user, however GRP is
not the primary group. Will gpfs enforce the secondary group quota for
that user?
Nope that's not how POSIX schematics work for group quotas. As far as I
can tell only your primary gr
Quoting "Sven Oehme" :
Hi,
quotas are only counted against primary group
sven
Thanks Sven
I kind of suspected, but needed an independent confirmation.
Jaime
On Wed, Aug 3, 2016 at 9:22 AM, Jaime Pinto
wrote:
Suppose I want to set both USR and GRP quotas for a user, however GRP is
not
Hi,
quotas are only counted against primary group
sven
On Wed, Aug 3, 2016 at 9:22 AM, Jaime Pinto
wrote:
> Suppose I want to set both USR and GRP quotas for a user, however GRP is
> not the primary group. Will gpfs enforce the secondary group quota for that
> user?
>
> What I mean is, if the
Suppose I want to set both USR and GRP quotas for a user, however GRP
is not the primary group. Will gpfs enforce the secondary group quota
for that user?
What I mean is, if the user keeps writing files with secondary group
as the attribute, and that overall group quota is reached, will tha
Your first process is correct. Install the 4.2.0-0 rpms first, then install
the 4.2.1 rpms after.
-Bryan
-Original Message-
From: gpfsug-discuss-boun...@spectrumscale.org
[mailto:gpfsug-discuss-boun...@spectrumscale.org] On Behalf Of Kenneth Waegeman
Sent: Wednesday, August 03, 2016 3:5
Hi,
In the upgrade procedure (prerequisites) of 4.2.1, I read:
"If you are coming from 4.1.1-X, you must first upgrade to 4.2.0-0. You
may use this 4.2.1-0 package to perform a First Time Install or to
upgrade from an existing 4.2.0-X level."
What does this mean exactly. Should we just instal
And I am seeing the same behaviour on a SLES 12 SP1 update from 4.2.04 to
4.2.1.0.
From: gpfsug-discuss-boun...@spectrumscale.org
[mailto:gpfsug-discuss-boun...@spectrumscale.org] On Behalf Of
greg.lehm...@csiro.au
Sent: Wednesday, 3 August 2016 3:07 PM
To: gpfsug-discuss@spectrumscale.org
Subj
18 matches
Mail list logo
