subject:"Re\: \[gpfsug\-discuss\] GPFS Independent Fileset Limit vs Quotas\?"

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-17 Thread Marc A Kaplan

My idea, not completely thought out, is that before you hit the 1000 
limit, you start putting new customers or projects into dependent filesets 
and define those new dependent filesets within either a lesser number of 
independent filesets expressly created to receive the new customers OR 
perhaps even lump them with already existing independent filesets that 
have matching backup requirements.

I would NOT try to create backups for each dependent fileset.  But stick 
with the supported facilities to manage backup per independent...

Having said that, if you'd still like to do backup per dependent fileset 
-- then have at it -- but test, test and retest And measure 
performance...
My GUESS is that IF you can hack mmbackup or similar to use  mmapplypolicy 
/path-to-dependent-fileset  --scope fileset  
instead of mmapplypolicy /path-to-independent-fileset --scope inodespace 


You'll be okay because the inodescan where you end up reading some extra 
inodes is probably a tiny fraction of all the other IO you'll be doing! 

BUT I don't think IBM is in a position to encourage you to hack mmbackup 
-- it's already very complicated!





From:   "Peinkofer, Stephan" 
To: gpfsug main discussion list 
Date:   08/17/2018 07:40 AM
Subject:    Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs 
Quotas?
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Dear Marc,

well as I think I cannot simply "move" dependent filesets between 
independent ones and our customers must have the opportunity to change 
data protection policy for their Containers at any given time, I cannot 
map them to a "backed up" or "not backed up" independent fileset.

So how much performance impact is lets say 1-10 exclude.dir directives per 
independent fileset?

Many thanks in advance.
Best Regards,
Stephan Peinkofer



From: gpfsug-discuss-boun...@spectrumscale.org 
 on behalf of Marc A Kaplan 

Sent: Tuesday, August 14, 2018 5:31 PM
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas? 
 
True, mmbackup is designed to work best backing up either a single 
independent fileset or the entire file system.  So if you know some 
filesets do not need to be backed up, map them to one or more indepedent 
filesets that will not be backed up.

mmapplypolicy is happy to scan a single dependent fileset, use option 
--scope fileset and make the primary argument the path to the root of the 
fileset you wish to scan.   The overhead is not simply described.   The 
directory scan phase will explore or walk the (sub)tree in parallel with 
multiple threads on multiple nodes, reading just the directory blocks that 
need to be read.

The inodescan phase will read blocks of inodes from the given inodespace 
...  since the inodes of dependent filesets may be "mixed" into the same 
blocks as other dependend filesets that are in the same independent 
fileset, mmapplypolicy will incur what you might consider "extra" 
overhead.




From:"Peinkofer, Stephan" 
To:gpfsug main discussion list 
Date:08/14/2018 12:50 AM
Subject:Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs 
Quotas?
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Dear Marc,


If you "must" exceed 1000 filesets because you are assigning each project 
to its own fileset, my suggestion is this:

Yes, there are scaling/performance/manageability benefits to using 
mmbackup over independent filesets.

But maybe you don't need 10,000 independent filesets -- 
maybe you can hash or otherwise randomly assign projects that each have 
their own (dependent) fileset name to a lesser number of independent 
filesets that will serve as management groups for (mm)backup...

OK, if that might be doable, whats then the performance impact of having 
to specify Include/Exclude lists for each independent fileset in order to 
specify which dependent fileset should be backed up and which one not?
I don’t remember exactly, but I think I’ve heard at some time, that 
Include/Exclude and mmbackup have to be used with caution. And the same 
question holds true for running mmapplypolicy for a “job” on a single 
dependent fileset? Is the scan runtime linear to the size of the 
underlying independent fileset or are there some optimisations when I just 
want to scan a subfolder/dependent fileset of an independent one?

Like many things in life, sometimes compromises are necessary!

Hmm, can I reference this next time, when we negotiate Scale License 
pricing with the ISS sales people? ;)

Best Regards,
Stephan Peinkofer
___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss


___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gp

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-14 Thread Marc A Kaplan

True, mmbackup is designed to work best backing up either a single 
independent fileset or the entire file system.  So if you know some 
filesets do not need to be backed up, map them to one or more indepedent 
filesets that will not be backed up. 

mmapplypolicy is happy to scan a single dependent fileset, use option 
--scope fileset and make the primary argument the path to the root of the 
fileset you wish to scan.   The overhead is not simply described.   The 
directory scan phase will explore or walk the (sub)tree in parallel with 
multiple threads on multiple nodes, reading just the directory blocks that 
need to be read.

The inodescan phase will read blocks of inodes from the given inodespace 
...  since the inodes of dependent filesets may be "mixed" into the same 
blocks as other dependend filesets that are in the same independent 
fileset, mmapplypolicy will incur what you might consider "extra" 
overhead.




From:   "Peinkofer, Stephan" 
To: gpfsug main discussion list 
Date:   08/14/2018 12:50 AM
Subject:    Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs 
Quotas?
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Dear Marc,


If you "must" exceed 1000 filesets because you are assigning each project 
to its own fileset, my suggestion is this:

Yes, there are scaling/performance/manageability benefits to using 
mmbackup over independent filesets.

But maybe you don't need 10,000 independent filesets -- 
maybe you can hash or otherwise randomly assign projects that each have 
their own (dependent) fileset name to a lesser number of independent 
filesets that will serve as management groups for (mm)backup...

OK, if that might be doable, whats then the performance impact of having 
to specify Include/Exclude lists for each independent fileset in order to 
specify which dependent fileset should be backed up and which one not?
I don’t remember exactly, but I think I’ve heard at some time, that 
Include/Exclude and mmbackup have to be used with caution. And the same 
question holds true for running mmapplypolicy for a “job” on a single 
dependent fileset? Is the scan runtime linear to the size of the 
underlying independent fileset or are there some optimisations when I just 
want to scan a subfolder/dependent fileset of an independent one?

Like many things in life, sometimes compromises are necessary!

Hmm, can I reference this next time, when we negotiate Scale License 
pricing with the ISS sales people? ;)

Best Regards,
Stephan Peinkofer
___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss





___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-14 Thread Grunenberg, Renar

+1  great answer Stephan. We also dont understand why funktions are existend, 
but every time we want to use it, the first step is make a requirement.

Von meinem iPhone gesendet


Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:09561 96-44110
Telefax:09561 96-44104
E-Mail: renar.grunenb...@huk-coburg.de
Internet:   www.huk.de

HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.

Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in 
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this 
information is strictly forbidden.


Am 14.08.2018 um 06:50 schrieb Peinkofer, Stephan 
mailto:stephan.peinko...@lrz.de>>:

Dear Marc,


If you "must" exceed 1000 filesets because you are assigning each project to 
its own fileset, my suggestion is this:

Yes, there are scaling/performance/manageability benefits to using mmbackup 
over independent filesets.

But maybe you don't need 10,000 independent filesets --
maybe you can hash or otherwise randomly assign projects that each have their 
own (dependent) fileset name to a lesser number of independent filesets that 
will serve as management groups for (mm)backup...

OK, if that might be doable, whats then the performance impact of having to 
specify Include/Exclude lists for each independent fileset in order to specify 
which dependent fileset should be backed up and which one not?
I don’t remember exactly, but I think I’ve heard at some time, that 
Include/Exclude and mmbackup have to be used with caution. And the same 
question holds true for running mmapplypolicy for a “job” on a single dependent 
fileset? Is the scan runtime linear to the size of the underlying independent 
fileset or are there some optimisations when I just want to scan a 
subfolder/dependent fileset of an independent one?

Like many things in life, sometimes compromises are necessary!

Hmm, can I reference this next time, when we negotiate Scale License pricing 
with the ISS sales people? ;)

Best Regards,
Stephan Peinkofer

___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-13 Thread Peinkofer, Stephan

Dear Marc,


If you "must" exceed 1000 filesets because you are assigning each project to 
its own fileset, my suggestion is this:

Yes, there are scaling/performance/manageability benefits to using mmbackup 
over independent filesets.

But maybe you don't need 10,000 independent filesets --
maybe you can hash or otherwise randomly assign projects that each have their 
own (dependent) fileset name to a lesser number of independent filesets that 
will serve as management groups for (mm)backup...

OK, if that might be doable, whats then the performance impact of having to 
specify Include/Exclude lists for each independent fileset in order to specify 
which dependent fileset should be backed up and which one not?
I don’t remember exactly, but I think I’ve heard at some time, that 
Include/Exclude and mmbackup have to be used with caution. And the same 
question holds true for running mmapplypolicy for a “job” on a single dependent 
fileset? Is the scan runtime linear to the size of the underlying independent 
fileset or are there some optimisations when I just want to scan a 
subfolder/dependent fileset of an independent one?

Like many things in life, sometimes compromises are necessary!

Hmm, can I reference this next time, when we negotiate Scale License pricing 
with the ISS sales people? ;)

Best Regards,
Stephan Peinkofer

___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-13 Thread Marc A Kaplan

If you "must" exceed 1000 filesets because you are assigning each project 
to its own fileset, my suggestion is this:

Yes, there are scaling/performance/manageability benefits to using 
mmbackup over independent filesets.

But maybe you don't need 10,000 independent filesets -- 
maybe you can hash or otherwise randomly assign projects that each have 
their own (dependent) fileset name to a lesser number of independent 
filesets that will serve as management groups for (mm)backup...

Like many things in life, sometimes compromises are necessary!



From:   "Peinkofer, Stephan" 
To: gpfsug main discussion list 
Date:   08/13/2018 03:26 AM
Subject:    Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs 
Quotas?
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Dear Marc,

OK, so let’s give it a try:

[root@datdsst100 pr74qo]# mmlsfileset dsstestfs01
Filesets in file system 'dsstestfs01':
Name StatusPath 
root Linked/dss/dsstestfs01 
...
quota_test_independent   Linked/dss/dsstestfs01/quota_test_independent 

quota_test_dependent Linked 
/dss/dsstestfs01/quota_test_independent/quota_test_dependent

[root@datdsst100 pr74qo]# mmsetquota dsstestfs01:quota_test_independent 
--user a2822bp --block 1G:1G --files 10:10
[root@datdsst100 pr74qo]# mmsetquota dsstestfs01:quota_test_dependent 
--user a2822bp --block 10G:10G --files 100:100

[root@datdsst100 pr74qo]#  mmrepquota -u -v 
dsstestfs01:quota_test_independent 
*** Report for USR quotas on dsstestfs01
 Block Limits| 
File Limits
Name   filesettype KB  quota  limit   in_doubt 
   grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_independent USR   01048576 1048576   
0 none |0  10   100 none e 
root   quota_test_independent USR   0  0 0  0 none 
|1   000 none i 

[root@datdsst100 pr74qo]#  mmrepquota -u -v 
dsstestfs01:quota_test_dependent
*** Report for USR quotas on dsstestfs01
 Block Limits| 
File Limits
Name   filesettype KB  quota  limit   in_doubt 
   grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_dependent USR   0   10485760   10485760  
   0 none |0 100  1000 none e 
root   quota_test_dependent USR   0  0  0  
   0 none |1   000 none i 

Looks good …

[root@datdsst100 pr74qo]# cd 
/dss/dsstestfs01/quota_test_independent/quota_test_dependent/
[root@datdsst100 quota_test_dependent]# for foo in `seq 1 99`; do touch 
file${foo}; chown a2822bp:pr28fa file${foo}; done

[root@datdsst100 quota_test_dependent]#  mmrepquota -u -v 
dsstestfs01:quota_test_dependent
*** Report for USR quotas on dsstestfs01
 Block Limits| 
File Limits
Name   filesettype KB  quota  limit   in_doubt 
   grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_dependent USR   0   10485760   10485760  
   0 none |   99 100  1000 none e 
root   quota_test_dependent USR   0  0  0  
   0 none |1   000 none i 
 
[root@datdsst100 quota_test_dependent]#  mmrepquota -u -v 
dsstestfs01:quota_test_independent 
*** Report for USR quotas on dsstestfs01
 Block Limits| 
File Limits
Name   filesettype KB  quota  limit   in_doubt 
   grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_independent USR   01048576 1048576   
0 none |0  10   100 none e 
root   quota_test_independent USR   0  0 0  0 none 
|1   000 none i 

So it seems that per fileset per user quota is really not depending on 
independence. But what is the documentation then meaning with:
>>> User group and user quotas can be tracked at the file system level or 
per independent fileset.
???

However, there still remains the problem with mmbackup and mmapplypolicy …
And if you look at some of the RFEs, like the one from DESY, they want 
even more than 10k independent filesets …


Best Regards,
Stephan Peinkofer
-- 
Stephan Peinkofer
Dipl. Inf. (FH), M. Sc. (TUM)
 
Leibniz Supercomputing Centre
Data and Storage Division
Boltzmannstraße 1, 85748 Garching b. München
Tel: +49(0)89 35831-8715 Fax: +49(0)89 35831-9700
URL: http://www.lrz.de

On

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-13 Thread Olaf Weiser

as Dominic said.. .. your are absolutely
right .. for mmbackup you need dedicated inode spaces .. so "independent"
filesets .. (in case I  you wanna  be able to mmbackup on a fileset
level or multiple mmbackup's in parallel .. )From:      
 "Peinkofer, Stephan"
To:      
 gpfsug main discussion
list Date:      
 08/13/2018 09:26 AMSubject:    
   Re: [gpfsug-discuss]
GPFS Independent Fileset Limit vs Quotas?Sent by:    
   gpfsug-discuss-boun...@spectrumscale.orgDear Marc,OK, so let’s give it a try:[root@datdsst100 pr74qo]# mmlsfileset dsstestfs01Filesets in file system 'dsstestfs01':Name              
      Status    Path        
                     
     root              
      Linked    /dss/dsstestfs01    
                   ...quota_test_independent   Linked    /dss/dsstestfs01/quota_test_independent
quota_test_dependent     Linked    /dss/dsstestfs01/quota_test_independent/quota_test_dependent[root@datdsst100 pr74qo]# mmsetquota dsstestfs01:quota_test_independent
--user a2822bp --block 1G:1G --files 10:10[root@datdsst100 pr74qo]# mmsetquota dsstestfs01:quota_test_dependent
--user a2822bp --block 10G:10G --files 100:100[root@datdsst100 pr74qo]#  mmrepquota -u -v dsstestfs01:quota_test_independent
*** Report for USR quotas on dsstestfs01               
         Block Limits        
                     
     |              
      File LimitsName       fileset    type  
          KB      quota  
   limit   in_doubt    grace |    files
  quota    limit in_doubt    grace entryTypea2822bp    quota_test_independent USR  
            0    1048576  
 1048576          0     none |
       0      10      
10        0     none e      
  root       quota_test_independent USR  
            0        
 0          0        
 0     none |        1    
  0        0        0  
  none i         [root@datdsst100 pr74qo]#  mmrepquota -u -v dsstestfs01:quota_test_dependent*** Report for USR quotas on dsstestfs01               
         Block Limits        
                     
     |              
      File LimitsName       fileset    type  
          KB      quota  
   limit   in_doubt    grace |    files
  quota    limit in_doubt    grace entryTypea2822bp    quota_test_dependent USR    
          0   10485760   10485760  
       0     none |      
 0     100      100      
 0     none e         root       quota_test_dependent USR  
            0        
 0          0        
 0     none |        1    
  0        0        0  
  none i         Looks good …[root@datdsst100 pr74qo]# cd /dss/dsstestfs01/quota_test_independent/quota_test_dependent/[root@datdsst100 quota_test_dependent]# for foo in `seq
1 99`; do touch file${foo}; chown a2822bp:pr28fa file${foo}; done[root@datdsst100 quota_test_dependent]#  mmrepquota
-u -v dsstestfs01:quota_test_dependent*** Report for USR quotas on dsstestfs01               
         Block Limits        
                     
     |              
      File LimitsName       fileset    type  
          KB      quota  
   limit   in_doubt    grace |    files
  quota    limit in_doubt    grace entryTypea2822bp    quota_test_dependent USR    
          0   10485760   10485760  
       0     none |      
99     100      100        0
    none e         root       quota_test_dependent USR  
            0        
 0          0        
 0     none |        1    
  0        0        0  
  none i         [root@datdsst100 quota_test_dependent]#  mmrepquota
-u -v dsstestfs01:quota_test_independent *** Report for USR quotas on dsstestfs01               
         Block Limits        
                     
     |              
      File LimitsName       fileset    type  
          KB      quota  
   limit   in_doubt    grace |    files
  quota    limit in_doubt    grace entryTypea2822bp    quota_test_independent USR  
            0    1048576  
 1048576          0     none |
       0      10      
10        0     none e      
  root       quota_test_independent USR  
            0        
 0          0        
 0     none |        1    
  0        0        0  
  none i         So it seems that per fileset per user quota is really
not depending on independence. But what is the documentation then meaning
with:>>> User group and user quotas can be tracked
at the file system level or per independent fileset.???However, there still remains the problem with mmbackup
and mmapplypolicy …And if you look at some of the RFEs, like the one from
DESY, they want even more than 10k independent filesets …Best Regards,Stephan Peinkofer-- Stephan PeinkoferDipl. Inf. (FH), M. Sc. (TUM) Leibniz Supercomputing CentreData and Storage DivisionBoltzmannstraße 1, 85748 Garching b. MünchenTel: +49(0)89 35831-8715     Fax: +49(0)89 35831-9700URL: http://www.lrz.deOn 12. Aug 2018, at 15:05, Marc A Kaplan <makap...@us.ibm.com>
wrote:That's interesting, I confess I never read that piece
of documentation.What's also interesting, is that if you look at this doc for quotas:https://www.ibm.com/supp

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-13 Thread Peinkofer, Stephan

Dear Marc,

OK, so let’s give it a try:

[root@datdsst100 pr74qo]# mmlsfileset dsstestfs01
Filesets in file system 'dsstestfs01':
Name StatusPath
root Linked/dss/dsstestfs01
...
quota_test_independent   Linked/dss/dsstestfs01/quota_test_independent
quota_test_dependent Linked
/dss/dsstestfs01/quota_test_independent/quota_test_dependent

[root@datdsst100 pr74qo]# mmsetquota dsstestfs01:quota_test_independent --user 
a2822bp --block 1G:1G --files 10:10
[root@datdsst100 pr74qo]# mmsetquota dsstestfs01:quota_test_dependent --user 
a2822bp --block 10G:10G --files 100:100

[root@datdsst100 pr74qo]#  mmrepquota -u -v dsstestfs01:quota_test_independent
*** Report for USR quotas on dsstestfs01
 Block Limits|  
   File Limits
Name   filesettype KB  quota  limit   in_doubt
grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_independent USR   010485761048576 
 0 none |0  10   100 none e
root   quota_test_independent USR   0  0  0 
 0 none |1   000 none i

[root@datdsst100 pr74qo]#  mmrepquota -u -v dsstestfs01:quota_test_dependent
*** Report for USR quotas on dsstestfs01
 Block Limits|  
   File Limits
Name   filesettype KB  quota  limit   in_doubt
grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_dependent USR   0   10485760   10485760   
   0 none |0 100  1000 none e
root   quota_test_dependent USR   0  0  0   
   0 none |1   000 none i

Looks good …

[root@datdsst100 pr74qo]# cd 
/dss/dsstestfs01/quota_test_independent/quota_test_dependent/
[root@datdsst100 quota_test_dependent]# for foo in `seq 1 99`; do touch 
file${foo}; chown a2822bp:pr28fa file${foo}; done

[root@datdsst100 quota_test_dependent]#  mmrepquota -u -v 
dsstestfs01:quota_test_dependent
*** Report for USR quotas on dsstestfs01
 Block Limits|  
   File Limits
Name   filesettype KB  quota  limit   in_doubt
grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_dependent USR   0   10485760   10485760   
   0 none |   99 100  1000 none e
root   quota_test_dependent USR   0  0  0   
   0 none |1   000 none i

[root@datdsst100 quota_test_dependent]#  mmrepquota -u -v 
dsstestfs01:quota_test_independent
*** Report for USR quotas on dsstestfs01
 Block Limits|  
   File Limits
Name   filesettype KB  quota  limit   in_doubt
grace |files   quotalimit in_doubtgrace entryType
a2822bpquota_test_independent USR   010485761048576 
 0 none |0  10   100 none e
root   quota_test_independent USR   0  0  0 
 0 none |1   000 none i

So it seems that per fileset per user quota is really not depending on 
independence. But what is the documentation then meaning with:
>>> User group and user quotas can be tracked at the file system level or per 
>>> independent fileset.
???

However, there still remains the problem with mmbackup and mmapplypolicy …
And if you look at some of the RFEs, like the one from DESY, they want even 
more than 10k independent filesets …


Best Regards,
Stephan Peinkofer
--
Stephan Peinkofer
Dipl. Inf. (FH), M. Sc. (TUM)

Leibniz Supercomputing Centre
Data and Storage Division
Boltzmannstraße 1, 85748 Garching b. München
Tel: +49(0)89 35831-8715 Fax: +49(0)89 35831-9700
URL: http://www.lrz.de

On 12. Aug 2018, at 15:05, Marc A Kaplan 
mailto:makap...@us.ibm.com>> wrote:

That's interesting, I confess I never read that piece of documentation.
What's also interesting, is that if you look at this doc for quotas:

https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_change_quota_anynum_users_onproject_basis_acrs_protocols.htm

The word independent appears only once in a "Note": It is recommended to create 
an independent fileset for the project.

AND if you look at the mmchfs or mmchcr command you see:
--perfileset-quota

 Sets the scope of user and group quota limit checks to the individual fileset 
level, rather than to the entire file system.

With no mention of "dependent" nor "independent"...




From:

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

2018-08-12 Thread Marc A Kaplan

That's interesting, I confess I never read that piece of documentation.
What's also interesting, is that if you look at this doc for quotas:

https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_change_quota_anynum_users_onproject_basis_acrs_protocols.htm

The word independent appears only once in a "Note": It is recommended to 
create an independent fileset for the project. 

AND if you look at the mmchfs or mmchcr command you see:

--perfileset-quota 
 Sets the scope of user and group quota limit checks to the individual 
fileset level, rather than to the entire file system. 

With no mention of "dependent" nor "independent"...




From:   "Peinkofer, Stephan" 
To: gpfsug main discussion list 
Date:   08/11/2018 03:03 AM
Subject:Re: [gpfsug-discuss] GPFS Independent Fileset Limit
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Dear Marc,

so at least your documentation says:
https://www.ibm.com/support/knowledgecenter/en/STXKQY_5.0.1/com.ibm.spectrum.scale.v5r01.doc/bl1hlp_filesfilesets.htm
>>> User group and user quotas can be tracked at the file system level or 
per independent fileset.
But obviously as a customer I don't know if that "Really" depends on 
independence.

Currently about 70% of our filesets in the Data Science Storage systems 
get backed up to ISP. But that number may change over time as it depends 
on the requirements of our projects. For them it is just selecting 
"Protect this DSS Container by ISP" in a Web form an our portal then 
automatically does all the provisioning of the ISP Node to one of our ISP 
servers, rolling out the new dsm config files to the backup workers and so 
on.

Best Regards, 
Stephan Peinkofer

From: gpfsug-discuss-boun...@spectrumscale.org 
 on behalf of Marc A Kaplan 

Sent: Friday, August 10, 2018 7:15 PM
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] GPFS Independent Fileset Limit 
 
I know quota stuff was cooked into GPFS before we even had "independent 
filesets"...
So which particular quota features or commands or options now depend on 
"independence"?! Really?

Yes, independent fileset performance for mmapplypolicy and mmbackup scales 
with the inodespace sizes. But I'm curious to know how many of those indy 
filesets are mmback-ed-up.

Appreciate your elaborations, 'cause even though I've worked on some of 
this code, I don't know how/when/if customers push which limits.

- 
Dear Marc,
well the primary reasons for us are:
- Per fileset quota (this seems to work also for dependent filesets as far 
as I know) 
- Per user per fileset quota (this seems only to work for independent 
filesets)
- The dedicated inode space to speedup mmpolicy runs which only have to be 
applied to a specific subpart of the file system
- Scaling mmbackup by backing up different filesets to different TSM 
Servers economically
We have currently more than 1000 projects on our HPC machines and several 
different existing and planned file systems (use cases):

___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss





___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

Re: [gpfsug-discuss] GPFS Independent Fileset Limit vs Quotas?

8 matches

Site Navigation

Mail list logo

Footer information