getting the trace while running with -lf flag

[Zubrania]

Hello Team

I am getting the following trace while trying to do pcp to lustre FS

without -lf flag pcp works as expected

env python 2.7
pcp from git

Thank you

Tue Mar 20 17:09:19 2018:WARNING: appears to have problems with openmpi on
Tue Mar 20 17:09:19 2018:large job sizes; if pcp hangs, consider using mpich
Tue Mar 20 17:09:19 2018:instead.
Tue Mar 20 17:09:19 2018:R0: All workers have reported in.
Tue Mar 20 17:09:19 2018:Starting 32 processes.
Tue Mar 20 17:09:19 2018:Files larger than 500 Mbytes will be copied in parallel chunks.
Tue Mar 20 17:09:19 2018:Will force stripe all files.
Tue Mar 20 17:09:19 2018:Will md5 verify copies.
Tue Mar 20 17:09:19 2018:
Tue Mar 20 17:09:19 2018:Starting phase I: Scanning and copying directory structure...
Tue Mar 20 17:09:19 2018:Exception on rank 0 host node25:
Tue Mar 20 17:09:19 2018:Traceback (most recent call last):
Tue Mar 20 17:09:19 2018: File "/usr/bin/pcp", line 1533, in
Tue Mar 20 17:09:19 2018: scantree(sourcedir, destdir, statedb)
Tue Mar 20 17:09:19 2018: File "/usr/bin/pcp", line 354, in scantree
Tue Mar 20 17:09:19 2018: listofpaths = walker.Execute(sourcedir)
Tue Mar 20 17:09:19 2018: File "/usr/local/lib/python2.7/site-packages/pcplib/parallelwalk. py", line 260, in Execute
Tue Mar 20 17:09:19 2018: self._ProcessNode()
Tue Mar 20 17:09:19 2018: File "/usr/local/lib/python2.7/site-packages/pcplib/parallelwalk. py", line 175, in _ProcessNode
Tue Mar 20 17:09:19 2018: self.ProcessDir(filename)
Tue Mar 20 17:09:19 2018: File "/usr/bin/pcp", line 1345, in ProcessDir
Tue Mar 20 17:09:19 2018: copyDir(directoryname, newdir)
Tue Mar 20 17:09:19 2018: File "/usr/bin/pcp", line 1042, in copyDir
Tue Mar 20 17:09:19 2018: layout = lustreapi.getstripe(sourcedir)
Tue Mar 20 17:09:19 2018: File "/usr/local/lib/python2.7/site-packages/pcplib/lustreapi.py" , line 121, in getstripe
Tue Mar 20 17:09:19 2018: raise IOError(err, os.strerror(err))
Tue Mar 20 17:09:19 2018:IOError: [Errno 25] Inappropriate ioctl for device

[guycoates]

Hi,
That means that the source directory is not a lustre filesystem, and so there is no stripe information to copy.

[Zubrania]

Hi, according to documentation I have found here “-lf can be used when only the destination filesystem is lustre.” That kind of error expected using “-l requires that the source and destination filesystems are both lustre." In my case only destination file system is Lustre while source file system is not

…

On Mar 26, 2018, at 18:56, Guy Coates ***@***.***> wrote: Hi, That means that the source directory is not a lustre filesystem, and so there is no stripe information to copy. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#30 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJOsZVSRDXgRRDfX6oN7ny56iEnZSFt7ks5tiQ-mgaJpZM4Sx_D5>.

[guycoates]

I can fix the code so that it will run where the source is not lustre; in the meantime, you can work around the issue by creating the destination directory, setting the striping on the directory with lfs setstripe, and running without -lf; that will stripe everything at the destination...

[Zubrania]

Thank you already done that using that workaround

…

On Mar 29, 2018, at 15:23, Guy Coates ***@***.***> wrote: I can fix the code so that it will run where the source is not lustre; in the meantime, you can work around the issue by creating the destination directory, setting the striping on the directory with lfs setstripe, and running without -lf; that will stripe everything at the destination... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#30 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJOsZWxFF1kQn2bquPsA4Lqia62t2mmRks5tjNJPgaJpZM4Sx_D5>.