[gpfsug-discuss] mmchfileset syntax

[Daniel Kidger]

-J is to define which fileset you are talking about.
The alternative is give the fileset name straight after the ‘device’ argument.

Once the fileset is unambiguous, you then use other command line option to change things
e.g. -j to change the *name* of this fileset.
-j doesn’t change the mount point, and indeed mmcrfileset doesn’t set the mount point either.


Daniel


 

 
 	
Dr Daniel Kidger 
IBM Technical Sales Specialist
Software Defined Solution Sales

+ 44-(0)7818 522 266 
daniel.kidger at uk.ibm.com

> On 3 Jan 2018, at 10:38, Sobey, Richard A <r.sobey at imperial.ac.uk> wrote:
> 
> Hi all,
>  
> Attempting to change the junction path of a fileset and I’m getting some strange output. It may just not be possible but the documentation on mmchfileset itself doesn’t make it clear.
>  
> mmchfileset gpfs filesetname -J /gpfs/new_path
> mmchfileset: Options -J and FilesetName cannot be specified at the same time.
>  
> Which leads to what’s the point of the following command as the error suggests it will work:
>  
> mmchfileset device -J /gpfs/new_path
>  
> …as not specifying a FilesetName to the input of mmchfileset seems odd.
>  
> I do of course know that I can just unlink and relink but hey.. trying to save a few precious seconds 😊
>  
> Cheers
> Richard
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=HlQDuUjgJx4p54QzcXd0_zTwf4Cr2t3NINalNhLTA2E&m=75vJhcWv1Hpd6tMuB3qZ2waqZZtyZy9OKQ0LEECaPUM&s=Qnv7oXB0V-pe1q5evqLFP6uZPxplkHonKfRwnT1Inpc&e=
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180103/ed9b9d8a/attachment-0002.htm>