<font size=2 face="sans-serif">When I see "independent fileset"
(in Spectrum/GPFS/Scale) I always think and try to read that as "inode
space".</font><br><br><font size=2 face="sans-serif">An "independent fileset" has
all the attributes of an (older-fashioned) dependent fileset PLUS all of
its files are represented by inodes that are in a separable range of inode
numbers - this allows GPFS to efficiently do snapshots of just that inode-space
(uh... independent fileset)...</font><br><br><font size=2 face="sans-serif">And... of course the files of dependent
filesets must also be represented by inodes -- those inode numbers are
within the inode-space of whatever the containing independent fileset is...
as was chosen when you created the fileset.... If you didn't say
otherwise, inodes come from the default "root" fileset....</font><br><br><font size=2 face="sans-serif">Clear as your bath-water, no?<br></font><br><font size=2 face="sans-serif">So why does mmbackup care one way or
another ??? Stay tuned....</font><br><br><font size=2 face="sans-serif">BTW - if you look at the bits of the
inode numbers carefully --- you may not immediately discern what I mean
by a "separable range of inode numbers" -- (very technical hint)
you may need to permute the bit order before you discern a simple pattern...</font><br><font size=2 face="sans-serif"> </font><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Luis Bolinches"
<luis.bolinches@fi.ibm.com></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug-discuss@spectrumscale.org</font><br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">gpfsug-discuss@spectrumscale.org</font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/18/2017 02:10 AM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [gpfsug-discuss]
mmbackup with fileset : scope errors</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><font size=2 face="Arial">Hi</font><br><font size=2 face="Arial"> </font><br><font size=2 face="Arial">There is no direct way to convert the one
fileset that is dependent to independent or viceversa.</font><br><font size=2 face="Arial"> </font><br><font size=2 face="Arial">I would suggest to take a look to chapter
5 of the 2014 redbook, lots of definitions about GPFS ILM including filesets
</font><a href=http://www.redbooks.ibm.com/abstracts/sg248254.html?Open><font size=2 color=blue face="Arial"><u>http://www.redbooks.ibm.com/abstracts/sg248254.html?Open</u></font></a><font size=2 face="Arial">Is not the only place that is explained but I honestly believe is a good
single start point. It also needs an update as does nto have anything on
CES nor ESS, so anyone in this list feel free to give feedback on that
page people with funding decisions listen there.</font><br><font size=2 face="Arial"> </font><br><font size=2 face="Arial">So you are limited to either migrate the
data from that fileset to a new independent fileset (multiple ways to do
that) or use the TSM client config.</font><br><font size=2 face="Arial"> </font><br><font size=2 face="Arial">----- Original message -----<br>From: "Jaime Pinto" <pinto@scinet.utoronto.ca><br>Sent by: gpfsug-discuss-bounces@spectrumscale.org<br>To: "gpfsug main discussion list" <gpfsug-discuss@spectrumscale.org>,
"Jaime Pinto" <pinto@scinet.utoronto.ca><br>Cc:<br>Subject: Re: [gpfsug-discuss] mmbackup with fileset : scope errors<br>Date: Thu, May 18, 2017 4:43 AM<br> </font><br><tt><font size=2>There is hope. See reference link below:</font></tt><tt><font size=2 color=blue><u><br></u></font></tt><a href=https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/com.ibm.spectrum.scale.v4r11.ins.doc/bl1ins_tsm_fsvsfset.htm target=_blank><tt><font size=2 color=blue><u>https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.1.1/com.ibm.spectrum.scale.v4r11.ins.doc/bl1ins_tsm_fsvsfset.htm</u></font></tt></a><tt><font size=2><br><br>The issue has to do with dependent vs. independent filesets, something
<br>I didn't even realize existed until now. Our filesets are dependent <br>(for no particular reason), so I have to find a way to turn them into <br>independent.<br><br>The proper option syntax is "--scope inodespace", and the error
<br>message actually flagged that out, however I didn't know how to <br>interpret what I saw:<br><br><br># mmbackup /gpfs/sgfs1/sysadmin3 -N tsm-helper1-ib0 -s /dev/shm <br>--scope inodespace --tsm-errorlog $logfile -L 2<br>--------------------------------------------------------<br>mmbackup: Backup of /gpfs/sgfs1/sysadmin3 begins at Wed May 17 <br>21:27:43 EDT 2017.<br>--------------------------------------------------------<br>Wed May 17 21:27:45 2017 mmbackup:mmbackup: Backing up *dependent* <br>fileset sysadmin3 is not supported<br>Wed May 17 21:27:45 2017 mmbackup:This fileset is not suitable for <br>fileset level backup. exit 1<br>--------------------------------------------------------<br><br>Will post the outcome.<br>Jaime<br><br><br><br>Quoting "Jaime Pinto" <pinto@scinet.utoronto.ca>:<br><br>> Quoting "Luis Bolinches" <luis.bolinches@fi.ibm.com>:<br>><br>>> Hi<br>>><br>>> have you tried to add exceptions on the TSM client config file?<br>><br>> Hey Luis,<br>><br>> That would work as well (mechanically), however it's not elegant or<br>> efficient. When you have over 1PB and 200M files on scratch it will<br>> take many hours and several helper nodes to traverse that fileset
just<br>> to be negated by TSM. In fact exclusion on TSM are just as inefficient.<br>> Considering that I want to keep project and sysadmin on different<br>> domains then it's much worst, since we have to traverse and exclude<br>> scratch & (project|sysadmin) twice, once to capture sysadmin and
again<br>> to capture project.<br>><br>> If I have to use exclusion rules it has to rely sole on gpfs rules,
and<br>> somehow not traverse scratch at all.<br>><br>> I suspect there is a way to do this properly, however the examples
on<br>> the gpfs guide and other references are not exhaustive. They only
show<br>> a couple of trivial cases.<br>><br>> However my situation is not unique. I suspect there are may facilities<br>> having to deal with backup of HUGE filesets.<br>><br>> So the search is on.<br>><br>> Thanks<br>> Jaime<br>><br>><br>><br>><br>>><br>>> Assuming your GPFS dir is /IBM/GPFS and your fileset to exclude
is linked<br>>> on /IBM/GPFS/FSET1<br>>><br>>> dsm.sys<br>>> ...<br>>><br>>> DOMAIN /IBM/GPFS<br>>> EXCLUDE.DIR /IBM/GPFS/FSET1<br>>><br>>><br>>> From: "Jaime Pinto" <pinto@scinet.utoronto.ca><br>>> To: "gpfsug main discussion list" <gpfsug-discuss@spectrumscale.org><br>>> Date: 17-05-17 23:44<br>>> Subject: [gpfsug-discuss] mmbackup
with fileset : scope errors<br>>> Sent by: gpfsug-discuss-bounces@spectrumscale.org<br>>><br>>><br>>><br>>> I have a g200 /gpfs/sgfs1 filesystem with 3 filesets:<br>>> * project3<br>>> * scratch3<br>>> * sysadmin3<br>>><br>>> I have no problems mmbacking up /gpfs/sgfs1 (or sgfs1), however
we<br>>> have no need or space to include *scratch3* on TSM.<br>>><br>>> Question: how to craft the mmbackup command to backup<br>>> /gpfs/sgfs1/project3 and/or /gpfs/sgfs1/sysadmin3 only?<br>>><br>>> Below are 3 types of errors:<br>>><br>>> 1) mmbackup /gpfs/sgfs1/sysadmin3 -N tsm-helper1-ib0 -s /dev/shm<br>>> --tsm-errorlog $logfile -L 2<br>>><br>>> ERROR: mmbackup: Options /gpfs/sgfs1/sysadmin3 and --scope filesystem<br>>> cannot be specified at the same time.<br>>><br>>> 2) mmbackup /gpfs/sgfs1/sysadmin3 -N tsm-helper1-ib0 -s /dev/shm<br>>> --scope inodespace --tsm-errorlog $logfile -L 2<br>>><br>>> ERROR: Wed May 17 16:27:11 2017 mmbackup:mmbackup: Backing up<br>>> dependent fileset sysadmin3 is not supported<br>>> Wed May 17 16:27:11 2017 mmbackup:This fileset is not suitable
for<br>>> fileset level backup. exit 1<br>>><br>>> 3) mmbackup /gpfs/sgfs1/sysadmin3 -N tsm-helper1-ib0 -s /dev/shm<br>>> --scope filesystem --tsm-errorlog $logfile -L 2<br>>><br>>> ERROR: mmbackup: Options /gpfs/sgfs1/sysadmin3 and --scope filesystem<br>>> cannot be specified at the same time.<br>>><br>>> These examples don't really cover my case:<br>>> </font></tt><a href=https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_mmbackup.htm#mmbackup__mmbackup_examples target=_blank><tt><font size=2 color=blue><u>https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.3/com.ibm.spectrum.scale.v4r23.doc/bl1adm_mmbackup.htm#mmbackup__mmbackup_examples</u></font></tt></a><tt><font size=2><br>>><br>>><br>>> Thanks<br>>> Jaime<br>>><br>>><br>>> ************************************<br>>> TELL US ABOUT YOUR SUCCESS
STORIES<br>>> </font></tt><a href=http://www.scinethpc.ca/testimonials target=_blank><tt><font size=2 color=blue><u>http://www.scinethpc.ca/testimonials</u></font></tt></a><tt><font size=2><br>>> ************************************<br>>> ---<br>>> Jaime Pinto<br>>> SciNet HPC Consortium - Compute/Calcul Canada<br>>> </font></tt><a href=www.scinet.utoronto.ca><tt><font size=2>www.scinet.utoronto.ca</font></tt></a><tt><font size=2>- </font></tt><a href=www.computecanada.ca><tt><font size=2>www.computecanada.ca</font></tt></a><tt><font size=2><br>>> University of Toronto<br>>> 661 University Ave. (MaRS), Suite 1140<br>>> Toronto, ON, M5G1M1<br>>> P: 416-978-2755<br>>> C: 416-505-1477<br>>><br>>> ----------------------------------------------------------------<br>>> This message was sent using IMP at SciNet Consortium, University
of<br>>> Toronto.<br>>><br>>> _______________________________________________<br>>> gpfsug-discuss mailing list<br>>> gpfsug-discuss at spectrumscale.org<br>>> </font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target=_blank><tt><font size=2 color=blue><u>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</u></font></tt></a><tt><font size=2><br>>><br>>><br>>><br>>><br>>><br>>> Ellei edellä ole toisin mainittu: / Unless stated otherwise above:<br>>> Oy IBM Finland Ab<br>>> PL 265, 00101 Helsinki, Finland<br>>> Business ID, Y-tunnus: 0195876-3<br>>> Registered in Finland<br>>><br>><br>><br>><br>><br>><br>><br>> ************************************<br>> TELL US ABOUT YOUR SUCCESS STORIES<br>> </font></tt><a href=http://www.scinethpc.ca/testimonials target=_blank><tt><font size=2 color=blue><u>http://www.scinethpc.ca/testimonials</u></font></tt></a><tt><font size=2><br>> ************************************<br>> ---<br>> Jaime Pinto<br>> SciNet HPC Consortium - Compute/Calcul Canada<br>> </font></tt><a href=www.scinet.utoronto.ca><tt><font size=2>www.scinet.utoronto.ca</font></tt></a><tt><font size=2>- </font></tt><a href=www.computecanada.ca><tt><font size=2>www.computecanada.ca</font></tt></a><tt><font size=2><br>> University of Toronto<br>> 661 University Ave. (MaRS), Suite 1140<br>> Toronto, ON, M5G1M1<br>> P: 416-978-2755<br>> C: 416-505-1477<br>><br>> ----------------------------------------------------------------<br>> This message was sent using IMP at SciNet Consortium, University of
Toronto.<br>><br>> _______________________________________________<br>> gpfsug-discuss mailing list<br>> gpfsug-discuss at spectrumscale.org<br>> </font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target=_blank><tt><font size=2 color=blue><u>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</u></font></tt></a><tt><font size=2><br>><br><br><br><br><br><br><br> ************************************<br> TELL US ABOUT YOUR SUCCESS STORIES<br> </font></tt><a href=http://www.scinethpc.ca/testimonials target=_blank><tt><font size=2 color=blue><u>http://www.scinethpc.ca/testimonials</u></font></tt></a><tt><font size=2><br> ************************************<br>---<br>Jaime Pinto<br>SciNet HPC Consortium - Compute/Calcul Canada<br></font></tt><a href=www.scinet.utoronto.ca><tt><font size=2>www.scinet.utoronto.ca</font></tt></a><tt><font size=2>- </font></tt><a href=www.computecanada.ca><tt><font size=2>www.computecanada.ca</font></tt></a><tt><font size=2><br>University of Toronto<br>661 University Ave. (MaRS), Suite 1140<br>Toronto, ON, M5G1M1<br>P: 416-978-2755<br>C: 416-505-1477<br><br>----------------------------------------------------------------<br>This message was sent using IMP at SciNet Consortium, University of Toronto.<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org</font></tt><tt><font size=2 color=blue><u><br></u></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target=_blank><tt><font size=2 color=blue><u>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</u></font></tt></a><font size=2 face="Arial"><br> </font><br><font size=2 face="Arial"> </font><br><font size=3><br>Ellei edellä ole toisin mainittu: / Unless stated otherwise above:<br>Oy IBM Finland Ab<br>PL 265, 00101 Helsinki, Finland<br>Business ID, Y-tunnus: 0195876-3 <br>Registered in Finland<br></font><tt><font size=2>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br></font></tt><br><br><BR>