Closing Today - Lustre Usage Survey
by OpenSFS Administration
Hello Lustre Community,
There are still a few hours remaining to submit your response to the Lustre
Usage Survey! Since the survey closes today, February 28th, we hope you'll
take a few minutes to provide your feedback in order to help us identify
Lustre usage trends and assist with future planning on releases.
The survey only takes a few minutes to complete and can be accessed at
https://www.surveymonkey.com/r/ZVZ2663. Note that all questions are
optional, so it is ok to submit a partially completed survey if you prefer
not to disclose some information. The results of the survey will be shared
at LUG 2018.
Thanks for your participation,
OpenSFS Administration
__________________________
OpenSFS Administration
3855 SW 153rd Drive Beaverton, OR 97003 USA
Phone: +1 503-619-0561 | Fax: +1 503-644-6708
Twitter:
<https://urlf.duocircle.io/?url=https%3A%2F%2Ftwitter.com%2Fopensfs&id=31d5&
rcpt=jfranklin(a)vtmgroup.com&tss=1517589596&msgid=b376eaa5-0837-11e8-b762-7df
9de8d46fe&html=1&h=be6fe83c> @OpenSFS
Email: <mailto:admin@opensfs.org> admin(a)opensfs.org | Website:
<https://urlf.duocircle.io/?url=http%3A%2F%2Fwww.opensfs.org%2F&id=31d5&rcpt
=jfranklin(a)vtmgroup.com&tss=1517589596&msgid=b376eaa5-0837-11e8-b762-7df9de8
d46fe&html=1&h=4eaae127> www.opensfs.org
3 years
Re: [HPDD-discuss] Lustre filelocking issue
by Colin Faber
Did you mount lustre client with the flock option?
On Feb 15, 2018 9:56 AM, "Prentice Bisbal" <pbisbal(a)pppl.gov> wrote:
Hi.
I'm an experience HPC system admin, but I know almost nothing about Lustre
administration. The system admin who administered our small Lustre
filesystem recently retired, and no one has filled that gap yet. I user
recently reported they are now getting file-locking errors from a program
they've run repeatedly on Lustre in the past. When the run the same program
on an NFS filesystem, the error goes away. I've cut-and-pasted the error
messages below.
Since I have real experience as a Lustre admin, I turned to google, and it
looks like it might be that the file-locking daemon died (if Lustre has a
separate file-lock daemon), or somehow file-locking was recently disabled.
If that is possible, how do I check this, and restart or re-enable if
necessary? I skimmed the user manual, and could not find anything on
either of these issues.
Any and all help will be greatly appreciated.
Some of the error messages:
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) MPI-process 9:
#000: H5F.c line 579 in H5Fopen(): unable to open file
major: File accessibilty
minor: Unable to open file
#001: H5Fint.c line 1168 in H5F_open(): unable to lock the file or
initialize file structure
major: File accessibilty
minor: Unable to open file
#002: H5FD.c line 1821 in H5FD_lock(): driver lock request failed
major: Virtual File Layer
minor: Can't update object
#003: H5FDsec2.c line 939 in H5FD_sec2_lock(): unable to flock file,
errno = 38, error message = 'Function not implemented'
major: File accessibilty
minor: Bad file ID accessed
Error: couldn't open file HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1)
MPI-process 13:
#000: H5F.c line 579 in H5Fopen(): unable to open file
major: File accessibilty
minor: Unable to open file
#001: H5Fint.c line 1168 in H5F_open(): unable to lock the file or
initialize file structure
major: File accessibilty
minor: Unable to open file
#002: H5FD.c line 1821 in H5FD_lock(): driver lock request failed
major: Virtual File Layer
minor: Can't update object
#003: H5FDsec2.c line 939 in H5FD_sec2_lock(): unable to flock file,
errno = 38, error message = 'Function not implemented'
major: File accessibilty
minor: Bad file ID accessed
--
Prentice
_______________________________________________
HPDD-discuss mailing list
HPDD-discuss(a)lists.01.org
https://lists.01.org/mailman/listinfo/hpdd-discuss
3 years
Lustre filelocking issue
by Prentice Bisbal
Hi.
I'm an experience HPC system admin, but I know almost nothing about
Lustre administration. The system admin who administered our small
Lustre filesystem recently retired, and no one has filled that gap yet.
I user recently reported they are now getting file-locking errors from a
program they've run repeatedly on Lustre in the past. When the run the
same program on an NFS filesystem, the error goes away. I've
cut-and-pasted the error messages below.
Since I have real experience as a Lustre admin, I turned to google, and
it looks like it might be that the file-locking daemon died (if Lustre
has a separate file-lock daemon), or somehow file-locking was recently
disabled. If that is possible, how do I check this, and restart or
re-enable if necessary? I skimmed the user manual, and could not find
anything on either of these issues.
Any and all help will be greatly appreciated.
Some of the error messages:
HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) MPI-process 9:
#000: H5F.c line 579 in H5Fopen(): unable to open file
major: File accessibilty
minor: Unable to open file
#001: H5Fint.c line 1168 in H5F_open(): unable to lock the file or
initialize file structure
major: File accessibilty
minor: Unable to open file
#002: H5FD.c line 1821 in H5FD_lock(): driver lock request failed
major: Virtual File Layer
minor: Can't update object
#003: H5FDsec2.c line 939 in H5FD_sec2_lock(): unable to flock file,
errno = 38, error message = 'Function not implemented'
major: File accessibilty
minor: Bad file ID accessed
Error: couldn't open file HDF5-DIAG: Error detected in HDF5
(1.10.0-patch1) MPI-process 13:
#000: H5F.c line 579 in H5Fopen(): unable to open file
major: File accessibilty
minor: Unable to open file
#001: H5Fint.c line 1168 in H5F_open(): unable to lock the file or
initialize file structure
major: File accessibilty
minor: Unable to open file
#002: H5FD.c line 1821 in H5FD_lock(): driver lock request failed
major: Virtual File Layer
minor: Can't update object
#003: H5FDsec2.c line 939 in H5FD_sec2_lock(): unable to flock file,
errno = 38, error message = 'Function not implemented'
major: File accessibilty
minor: Bad file ID accessed
--
Prentice
3 years
Correct order of kernel modules load during lustre server boot
by Dzmitryj Jakavuk
Hello
I am looking for a correct procedure of booting multiprotocol OSS (ib0,bond0) with the requirement to start lustre modules automatically after system boot
Currently I don’t have the idea how to do that? can you please advice ? OS RHEL7
Thank you
3 years
LUG18 Abstracts due 2/16
by OpenSFS Administration
Want to present at the Lustre User Group
<http://opensfs.org/events/lug-2018/> this year? Be sure to submit your
abstract by the February 16th deadline: https://easychair.org/cfp/LUG2018 .
Accepted abstracts will be notified in time to take advantage of early bird
registration.
We would like to encourage end-user sites to submit presentations on best
practices and boundary-pushing deployments. Come join us for a great week of
material.
Additional LUG details, including early bird registration, are available at
http://opensfs.org/events/lug-2018/
We look forward to seeing you at Argonne!
Best regards,
The LUG 2018 Organizing & Program Committees
3 years
Load Lustre modules during bootup
by Dzmitryj Jakavuk
Hello
I am looking for a proper way of booting RHEL 7 and ability to load lustre modules
My config is the following
options lnet networks=“o2ib0(ib0),tcp0(bond0)”
Lustre on ZFS
I have tried to load lustre modules using systemd-modules-load.service. It inserts zfs modules,ksocklnd and ko2iblnd but does not load lustre module with the “Network Down” error and the following error description
"Cant query IPoIB interface ib0: it’s down”
later on I have changed the boot order of systemd-modules-load.service to start after network service but still unavailable to load lustre module during startup
After logging to the shell I can ping other IPoIB interfaces
Can you please help with the proper config to have lustre module load during boot?
thank you
3 years
Lustre Usage Survey: Input Requested
by OpenSFS Administration
Dear Lustre Community,
The OpenSFS Lustre Working Group has launched the seventh annual survey for
organizations using Lustre. We are looking for trends in Lustre usage to
assist with future planning on releases and will present the results at LUG.
Please complete this short survey (https://www.surveymonkey.com/r/ZVZ2663)
to make sure your organization's voice is heard!
Response to the survey is due by February 28th. Note that all questions are
optional, so it is ok to submit a partially completed survey if you prefer
not to disclose some information.
Best regards,
OpenSFS Administration
__________________________
OpenSFS Administration
3855 SW 153rd Drive Beaverton, OR 97003 USA
Phone: +1 503-619-0561 | Fax: +1 503-644-6708
Twitter: <https://twitter.com/opensfs> @OpenSFS
Email: <mailto:admin@opensfs.org> admin(a)opensfs.org | Website:
<http://www.opensfs.org/> www.opensfs.org
3 years, 1 month
