[gpfsug-discuss] GPFS+TSM+HSM: staging vs. migration priority

[Jaime Pinto]

Hey Dominic

Just submitted a  new request:

Headline: GPFS+TSM+HSM: staging vs. migration priority

ID: 85292

Thank you
Jaime



Quoting Dominic Mueller-Wicke01 <dominic.mueller at de.ibm.com>:

>
> Hi Jaime,
>
> I received the same request from other customers as well.
> could you please open a RFE for the theme and send me the RFE ID? I will
> discuss it with the product management then. RFE Link:
> https://www.ibm.com/developerworks/rfe/execute?use_case=changeRequestLanding&BRAND_ID=0&PROD_ID=360&x=11&y=12
>
> Greetings, Dominic.
>
> ______________________________________________________________________________________________________________
>
> Dominic Mueller-Wicke | IBM Spectrum Protect Development | Technical Lead |
> +49 7034 64 32794 | dominic.mueller at de.ibm.com
>
> Vorsitzende des Aufsichtsrats: Martina Koederitz; Geschäftsführung: Dirk
> Wittkopp
> Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart,
> HRB 243294
>
>
>
> From:	Jaime Pinto <pinto at scinet.utoronto.ca>
> To:	gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>,
>             Marc A Kaplan <makaplan at us.ibm.com>
> Cc:	Dominic Mueller-Wicke01/Germany/IBM at IBMDE
> Date:	09.03.2016 16:22
> Subject:	Re: [gpfsug-discuss] GPFS+TSM+HSM: staging vs. migration
>             priority
>
>
>
> Interesting perspective Mark.
>
> I'm inclined to think EBUSY would be more appropriate.
>
> Jaime
>
> Quoting Marc A Kaplan <makaplan at us.ibm.com>:
>
>> For a write or create operation ENOSPC  would make some sense.
>> But if the file already exists and I'm just opening for read access I
>> would be very confused by ENOSPC.
>> How should the system respond:  "Sorry, I know about that file, I have it
>> safely stored away in HSM, but it is not available right now. Try again
>> later!"
>>
>> EAGAIN or EBUSY might be the closest in ordinary language...
>> But EAGAIN is used when a system call is interrupted and can be retried
>> right away...
>> So EBUSY?
>>
>> The standard return codes in Linux are:
>>
>> #define EPERM            1      /* Operation not permitted */
>> #define ENOENT           2      /* No such file or directory */
>> #define ESRCH            3      /* No such process */
>> #define EINTR            4      /* Interrupted system call */
>> #define EIO              5      /* I/O error */
>> #define ENXIO            6      /* No such device or address */
>> #define E2BIG            7      /* Argument list too long */
>> #define ENOEXEC          8      /* Exec format error */
>> #define EBADF            9      /* Bad file number */
>> #define ECHILD          10      /* No child processes */
>> #define EAGAIN          11      /* Try again */
>> #define ENOMEM          12      /* Out of memory */
>> #define EACCES          13      /* Permission denied */
>> #define EFAULT          14      /* Bad address */
>> #define ENOTBLK         15      /* Block device required */
>> #define EBUSY           16      /* Device or resource busy */
>> #define EEXIST          17      /* File exists */
>> #define EXDEV           18      /* Cross-device link */
>> #define ENODEV          19      /* No such device */
>> #define ENOTDIR         20      /* Not a directory */
>> #define EISDIR          21      /* Is a directory */
>> #define EINVAL          22      /* Invalid argument */
>> #define ENFILE          23      /* File table overflow */
>> #define EMFILE          24      /* Too many open files */
>> #define ENOTTY          25      /* Not a typewriter */
>> #define ETXTBSY         26      /* Text file busy */
>> #define EFBIG           27      /* File too large */
>> #define ENOSPC          28      /* No space left on device */
>> #define ESPIPE          29      /* Illegal seek */
>> #define EROFS           30      /* Read-only file system */
>> #define EMLINK          31      /* Too many links */
>> #define EPIPE           32      /* Broken pipe */
>> #define EDOM            33      /* Math argument out of domain of func */
>> #define ERANGE          34      /* Math result not representable */
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>           ************************************
>            TELL US ABOUT YOUR SUCCESS STORIES
>           http://www.scinethpc.ca/testimonials
>           ************************************
> ---
> Jaime Pinto
> SciNet HPC Consortium  - Compute/Calcul Canada
> www.scinet.utoronto.ca - www.computecanada.org
> University of Toronto
> 256 McCaul Street, Room 235
> Toronto, ON, M5T1W5
> P: 416-978-2755
> C: 416-505-1477
>
> ----------------------------------------------------------------
> This message was sent using IMP at SciNet Consortium, University of
> Toronto.
>
>
>
>
>






          ************************************
           TELL US ABOUT YOUR SUCCESS STORIES
          http://www.scinethpc.ca/testimonials
          ************************************
---
Jaime Pinto
SciNet HPC Consortium  - Compute/Calcul Canada
www.scinet.utoronto.ca - www.computecanada.org
University of Toronto
256 McCaul Street, Room 235
Toronto, ON, M5T1W5
P: 416-978-2755
C: 416-505-1477

----------------------------------------------------------------
This message was sent using IMP at SciNet Consortium, University of Toronto.