>>For the record, I have completed today my AFM migration of a filesystem with 
>>100 million files. Users are now accessing the new filesystem.


Loric-> Hi.  I was wondering, what version of GPFS where you running on the 
home and cache clusters?  I take it you broke up the prefetch list into smaller 
(for example <2 million) file lists? If not, how? How much capacity did you 
migfrate over and how long did this process take? Thanks.


Bill Pappas

901-619-0585

[email protected]


[1466780990050_DSTlogo.png]


[http://www.prweb.com/releases/2016/06/prweb13504050.htm]

http://www.prweb.com/releases/2016/06/prweb13504050.htm


________________________________
From: [email protected] 
<[email protected]> on behalf of 
[email protected] 
<[email protected]>
Sent: Monday, October 24, 2016 12:05 PM
To: [email protected]
Subject: gpfsug-discuss Digest, Vol 57, Issue 60

Send gpfsug-discuss mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://gpfsug.org/mailman/listinfo/gpfsug-discuss
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gpfsug-discuss digest..."


Today's Topics:

   1. Using AFM to migrate within the same cluster (Eric Horst)
   2. Re: Using AFM to migrate files. (Peter Childs) (Peter Childs)
      - URL encoding for pathnames (Loic Tortay)
   3. Re: Using AFM to migrate within the same cluster (Scott Fadden)
   4. Re: Using AFM to migrate files. (Peter Childs) (Peter Childs)
      - URL encoding for pathnames (Yaron Daniel)


----------------------------------------------------------------------

Message: 1
Date: Mon, 24 Oct 2016 09:16:56 -0700
From: Eric Horst <[email protected]>
To: gpfsug main discussion list <[email protected]>
Subject: [gpfsug-discuss] Using AFM to migrate within the same cluster
Message-ID:
        <CAF-To-2_BQSXKY1Qv2gs6BnxOC2RU=ywfil9mcw5crehzvd...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

The recent conversation about AFM has been interesting. I've read the
documentation several times and this is my question. Can AFM be used
to migrate between two filesystems in the same cluster? There are
examples of moving between clusters with NFS or native protocol but
I've got a simple situation of needing to transparently move 100M
files between two existing filesystems.

Thanks,

-Eric

--
Eric Horst
University of Washington


------------------------------

Message: 2
Date: Mon, 24 Oct 2016 18:50:51 +0200
From: Loic Tortay <[email protected]>
To: gpfsug main discussion list <[email protected]>
Subject: Re: [gpfsug-discuss] Using AFM to migrate files. (Peter
        Childs) (Peter Childs) - URL encoding for pathnames
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

On 10/24/2016 11:44 AM, Venkateswara R Puvvada wrote:
>
> mmafmctl prefecth expects encoded list file, and it is not documented
> correctly.  Issues like memory leak, file descriptor leak, and fileset
> going into Unmounted state were fixed in later releases (4.2.1/4.2.2). All
> your points are correct with respect to AFM migration. There is manual
> intervention required. Also prefetch does not give list of files which
> were failed during data read. Users need to run policy to find all
> uncached files today.
>
Hello,
For the record, I have completed today my AFM migration of a filesystem
with 100 million files. Users are now accessing the new filesystem.

After disabling user access and a last "prefetch", the AFM filesets were
converted to independent filesets.
Less than 600 files were then found to be different between the "home"
and the "cache" filesystems with a metadata comparison (I just copied
the files from the old filesystem to the new one).
I have compared the MD5 of a few thousand randomly selected files and
found no differences between the "home" and the "cache" filesystems.
I expect the users to let us know if they find something different (they
have been instructed to do so). We'll keep the "home" filesystem around
for some time, just in case there is a problem.

Maybe something else that should be mentionned in the documentation is
what to do with the ".ptrash" directories after the AFM filesets have
been converted. I removed them since they contained files that had
clearly been deleted by the users.


Lo?c.
--
|       Lo?c Tortay <[email protected]> - IN2P3 Computing Centre      |


------------------------------

Message: 3
Date: Mon, 24 Oct 2016 09:57:33 -0700
From: "Scott Fadden" <[email protected]>
To: gpfsug main discussion list <[email protected]>
Subject: Re: [gpfsug-discuss] Using AFM to migrate within the same
        cluster
Message-ID:
        
<of42d09886.a30a7c7b-on88258056.005d0734-88258056.005d2...@notes.na.collabserv.com>

Content-Type: text/plain; charset="us-ascii"

Yes you can use AFM to move data within a cluster. If you are using the
NSD protocol the target needs to be a separate file system, if you are
using NFS it needs to be an NFS export.


Scott Fadden
Spectrum Scale - Technical Marketing
Phone: (503) 880-5833
[email protected]
http://www.ibm.com/systems/storage/spectrum/scale



From:   Eric Horst <[email protected]>
To:     gpfsug main discussion list <[email protected]>
Date:   10/24/2016 09:17 AM
Subject:        [gpfsug-discuss] Using AFM to migrate within the same
cluster
Sent by:        [email protected]



The recent conversation about AFM has been interesting. I've read the
documentation several times and this is my question. Can AFM be used
to migrate between two filesystems in the same cluster? There are
examples of moving between clusters with NFS or native protocol but
I've got a simple situation of needing to transparently move 100M
files between two existing filesystems.

Thanks,

-Eric

--
Eric Horst
University of Washington
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss





-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20161024/866c55cf/attachment-0001.html>

------------------------------

Message: 4
Date: Mon, 24 Oct 2016 20:05:00 +0300
From: "Yaron Daniel" <[email protected]>
To: gpfsug main discussion list <[email protected]>
Subject: Re: [gpfsug-discuss] Using AFM to migrate files. (Peter
        Childs) (Peter Childs) - URL encoding for pathnames
Message-ID:
        
<ofbc94a30e.47d6d231-onc2258056.005dccb6-c2258056.005dd...@notes.na.collabserv.com>

Content-Type: text/plain; charset="iso-8859-1"

Hi

Maybe worth also to check if there are any orphan files in the NEW fs ?


Regards





Yaron Daniel
 94 Em Ha'Moshavot Rd

Server, Storage and Data Services - Team Leader
 Petach Tiqva, 49527
Global Technology Services
 Israel
Phone:
+972-3-916-5672


Fax:
+972-3-916-5672


Mobile:
+972-52-8395593


e-mail:
[email protected]


IBM Israel









From:   Loic Tortay <[email protected]>
To:     gpfsug main discussion list <[email protected]>
Date:   10/24/2016 07:50 PM
Subject:        Re: [gpfsug-discuss] Using AFM to migrate files. (Peter
Childs) (Peter Childs) - URL encoding for pathnames
Sent by:        [email protected]



On 10/24/2016 11:44 AM, Venkateswara R Puvvada wrote:
>
> mmafmctl prefecth expects encoded list file, and it is not documented
> correctly.  Issues like memory leak, file descriptor leak, and fileset
> going into Unmounted state were fixed in later releases (4.2.1/4.2.2).
All
> your points are correct with respect to AFM migration. There is manual
> intervention required. Also prefetch does not give list of files which
> were failed during data read. Users need to run policy to find all
> uncached files today.
>
Hello,
For the record, I have completed today my AFM migration of a filesystem
with 100 million files. Users are now accessing the new filesystem.

After disabling user access and a last "prefetch", the AFM filesets were
converted to independent filesets.
Less than 600 files were then found to be different between the "home"
and the "cache" filesystems with a metadata comparison (I just copied
the files from the old filesystem to the new one).
I have compared the MD5 of a few thousand randomly selected files and
found no differences between the "home" and the "cache" filesystems.
I expect the users to let us know if they find something different (they
have been instructed to do so). We'll keep the "home" filesystem around
for some time, just in case there is a problem.

Maybe something else that should be mentionned in the documentation is
what to do with the ".ptrash" directories after the AFM filesets have
been converted. I removed them since they contained files that had
clearly been deleted by the users.


Lo?c.
--
|       Lo?c Tortay <[email protected]> - IN2P3 Computing Centre      |
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss




-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20161024/449a0cf1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: 
<http://gpfsug.org/pipermail/gpfsug-discuss/attachments/20161024/449a0cf1/attachment.gif>

------------------------------

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


End of gpfsug-discuss Digest, Vol 57, Issue 60
**********************************************
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to