X-force Lustre 2019 Free Download
Sandrine Willert
Now, I will do a few tests on the p1-client. Perhaps after a write
conf that is basically clean... and I can replace it... but currently
it contains lots of info about each of the OST's.All the OST's are happy mounting to the mdt and all think that they
are part of our p1 file system.Thanks.
On Sun, Mar 18, 2012 at 3:04 PM, Kit Westneat wrote:
> Oh right, that makes sense. I guess if I were you I would try one of two
> things. First, back up the MDT, and then try:
> 1) format a small loopback device with the parameters you want the MDT to
> have, then replace the CONFIGS directory on your MDT with the CONFIGS
> directory on the loopback device
> - OR -
> 2) use a hex editor to modify the UUID
>
> Then use tunefs.lustre --print to make sure it all looks good before
> mounting it.
>
> Though one thing I wonder about is, are the OSTs on the same page with the
> fsname? Like are they expecting to be part of the p1 filesystem?
Those instructions are identical for 1.6 and 1.8.For current lustre, only two commands are used for configuration.
mkfs.lustre and mount.
Usually when lustre_rmmod returns that error, you run it a second time,
and it will clear things. Unless you have live mounts or network
connections.cliffw
I concur with Cliff White. The "lustre_rmmod" returns those sort of
errors if there is still a Lustre disk mounted. I have found (with
Lustre version 1.6.7.1) that I have to unmount all Lustre disks first
(hopefully nicely) and then I can run the lustre_rmmod command
typically without errors.My problems have come from a hung process which cannot be killed
accessing a Lustre disk. I have to cycle power to the Lustre client
on which the process is hung and the linux shutdown command hangs on
trying to remove the Lustre modules. I can't remove the modules
while the disk is still mounted (perceived active) and kill -9 PID
isn't working. My personal behavior for this is to run the linux
shutdown as far it goes (the lustre_rmmod part) and then I physically
cycle power on the stuck client box. If there is a better way, I
would like to learn it.Cheers!
megan
Syslog /var/log/messages is the normal place.You can use 'lctl ping' to verify that the client can reach the server.
Usually in these cases, it's a network/name misconfiguration.Run 'tunefs.lustre --print' on your servers, and verify that mgsnode=
is correct.cliffw
Those are server modules. You would need to add lustre-kernel-smp for
that to workFor a client, you install the matching vendor kernel, then:
lustre-client-modules
lustre-clientFor a server, you need
lustre-kernel-smp
lustre-modules
lustre-
ldiskfs-And as others have mentioned in this thread, kernel version must match
exactly. Check /lib/modules - if you have a mis-match, there will be an
extra directory there.cliffw
RPM installation order really doesn't matter. If you install in the
'wrong' order you will get a lot of warnings from RPM due to the
relationship of the various RPMs. But these are harmless - whatever
order you install in, it should work fine.
cliffw
Now that the obvious clue has been sleuthed out and identified the villainous depreciated kernel installation media can be destroyed. That should come in whatever form you feel appropriate from the good old Frisbee and forget or the always popular coaster contemplation collection.The order doesn't matter that much - aside from correct kernel first. What matters is the thoughtful message "Are the Modules Loaded?" If your getting it you have missed installing one of the packages. When all else fails remove and reinstall or even force as the case may be sometimes with the e2fsprogs. This becomes quite a chore when your installing on more then two computers.What is needed is a bare bones Lustre installation dvd iso. I'm sure Brian plugged the one Sun offers in another post and for a fact one University runs and develops in house their own distribution that would be very interesting to obtain but it's not public. Good luck Carlos and be sure to have plenty of inodes! Arden--- On Wed, 6/17/09, Jerome, Ron wrote:
I have some questions about the client packages. I am not sure why the roadmap or lustre users require separate client packages but stating the obvious some people must need separate client packages is that correct? Otherwise the server packages contain the client anyhow correct? If the later are the client packages for linux somewhat redundant? When will the real client .exe for windows become available?Arden--- On Wed, 6/17/09, Sheila Barthel wrote:
The key here is 'patchless client' Yes, any machine with Lustre server
bits installed can be a client. Not Long Ago, there was only one
installation for Lustre. Everybody got the same bits.And the Lustre design re-uses things. Note that any Lustre node
connecting to a service has a 'client' - for example the OSS is a
'client' of the MDS, and the MDS a 'client' of the OSS.The 'patchless client' was created to allow users to run Lustre with a
stock vendor/distro kernel. This removes a lot of support/installation
issues - servers can be considered 'Lustre-only' devices, but clients
typically have other goop installed. Allowing users to use a stock
distro kernel simplifies their support relationship with their other
vendors.
I think you are missing a basic point here. It's been mentioned a few times.
You don't have a lustre-patched kernel installed.Here's what a proper system looks like - it's 1.6.7.2, but that doesn't
matter, 1.8.0 is the same.
Notwithstanding Intel's ownership of the copyright in the modifications to the original version of this Operations Manual, as between Intel and Oracle, Oracle and/or its affiliates retain sole ownership of the copyright in the unmodified portions of this Operations Manual.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.
NOTHING IN THIS MODIFIED OPERATIONS MANUAL IS INTENDED TO AFFECT THE NOTICE PROVIDED BY ORACLE BELOW IN RESPECT OF THE ORIGINAL OPERATIONS MANUAL AND SUCH ORACLE NOTICE CONTINUES TO APPLY TO THIS MODIFIED OPERATIONS MANUAL EXCEPT FOR THE MODIFICATIONS; THIS INTEL NOTICE SHALL APPLY ONLY TO MODIFICATIONS MADE BY INTEL. AS BETWEEN YOU AND ORACLE: (I) NOTHING IN THIS INTEL NOTICE IS INTENDED TO AFFECT THE TERMS OF THE ORACLE NOTICE BELOW; AND (II) IN THE EVENT OF ANY CONFLICT BETWEEN THE TERMS OF THIS INTEL NOTICE AND THE TERMS OF THE ORACLE NOTICE, THE ORACLE NOTICE SHALL PREVAIL.
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license and obtain more information about Creative Commons licensing, visit Creative Commons Attribution-Share Alike 3.0 United States or send a letter to Creative Commons, 171 2nd Street, Suite 300, San Francisco, California 94105, USA.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
7fc3f7cf58