search for: rutman

In 1.6.0, when creating a MDT, you could specify multiple --mgsnode options and it would failover between them. 1.6.3 only seems to take the last one and --mgsnode=192.168.1.252 at o2ib:192.168.1.253 at o2ib doesn''t seem to failover to the other node. Any ideas how to get around this? Robert Robert LeBlanc College of Life Sciences Computer Support Brigham Young University leblanc at

This may be in the documentation. If so, I missed it. If a site has multiple Lustre file systems, the documentation implies that there only needs to be a single MGS for an entire site (regardless of the number of file systems). However, I also know it is fairly common to have a combined MGS/MDT. So here are the questions. 1. If we are going to have several Lustre file systems,

Hi I want my lustre do such things during OST failed: if some file has stripe data on th failed OST, any operation on the file will return IO error without blocking, and also at this moment I can create and read/write new file or read/write files which have no stripe data on the failed OST without blocking. What should I do ? How to configure? thanks! swin -------------- next part

In hopes of improving the quality, coverage, and currency of the Lustre User Manual, I''m putting out a call to the Lustre community for contributors to this important resource. The user manual is especially important for new users to Lustre, but has fallen into some disrepair now that there is no longer a dedicated documentation writer for it. As well, there are many sections of the

In hopes of improving the quality, coverage, and currency of the Lustre User Manual, I''m putting out a call to the Lustre community for contributors to this important resource. The user manual is especially important for new users to Lustre, but has fallen into some disrepair now that there is no longer a dedicated documentation writer for it. As well, there are many sections of the

Hi, Our lustre environment is: 2.6.9-55.0.9.EL_lustre.1.6.3smp I would like to change recovery timeout from default value 250s to something longer I tried example from manual: set_timeout <secs> Sets the timeout (obd_timeout) for a server to wait before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at

...not clear. It has been confirmed (see below) that tunefs.lustre is optional when no parameters are changed. So we decided to just carry on with the mounting of the partitions which eventually worked as expected. Thanks and Regards Heiko ... sweating out 3.64 gallons during upgrade .... Natan Rutman wrote: Sheila, can we fix this up? Let me know what you need from me. On Jul 27, 2010, at 10:47 PM, Heiko Schr?ter wrote: > Am Dienstag 27 Juli 2010, um 18:41:24 schrieben Sie: > >> >> You actually don''t need to run tunefs unless you are changing something. Additio...

RFC: This is draft proposal API for the user-level interface for feeds. (This does not describe changelogs in general). Feeds would generally be used for two things: creating audit logs, and driving a database watching for filesystem changes. -------------- next part -------------- A non-text attachment was scrubbed... Name: feed_api.pdf Type: application/pdf Size: 85313 bytes Desc: not

...hidclass.sys: Use IoRegisterDeviceInterface. ntoskrnl.exe: Create the device interface symlink in IoSetDeviceInterfaceState(). hidclass.sys: IoCreateSymbolicLink is now called by IoSetDeviceInterfaceState. hidclass.sys: Move IoSetDeviceInterfaceState to PNP_RemoveDevice. Baruch Rutman (1): winmm: Attempt only once to load the default joystick driver. Beren Minor (1): xinput1_3: Report SUCCESS from XInputSetState when FFB isn't available. Brendan McGrath (1): winebus.sys: Use JoystickNumButtons for button_count. Byeong-Sik Jeon (2): gdi32: Specify t...

Whamcloud and EMC are jointly investigating how to be able to contribute the Lustre client code into the upstream Linux kernel. As a prerequisite to this, EMC is working to clean up the Lustre client code to better match the kernel coding style, and one of the anticipated major obstacles to upstream kernel submission is the heavy use of code abstraction via libcfs for portability to other

Whamcloud and EMC are jointly investigating how to be able to contribute the Lustre client code into the upstream Linux kernel. As a prerequisite to this, EMC is working to clean up the Lustre client code to better match the kernel coding style, and one of the anticipated major obstacles to upstream kernel submission is the heavy use of code abstraction via libcfs for portability to other

NOTE: BETA SOFTWARE, NOT FOR PRODUCTION USE Cluster File Systems is pleased to announce the next beta version of Lustre 1.6, which includes the following new features: * Dynamic service threads - within a small range, extra service threads are started automatically when the request queue builds up. * Mixed-endian environment fixes * Easy permanent OST removal * MGS failover * MGS proc

NOTE: BETA SOFTWARE, NOT FOR PRODUCTION USE Cluster File Systems is pleased to announce the next beta version of Lustre 1.6, which includes the following new features: * Dynamic service threads - within a small range, extra service threads are started automatically when the request queue builds up. * Mixed-endian environment fixes * Easy permanent OST removal * MGS failover * MGS proc

A request on a call today prodded me to publish our general-purpose Lustre mdtest benchmark plan, the metadata counterpart to the IOR plan I had published before. Hope you may find it useful. Lustre MD Benchmark Methodology using mdtest http://goo.gl/UBs1p Lustre IO Benchmark Methodology using IOR http://goo.gl/7AWwQ

A request on a call today prodded me to publish our general-purpose Lustre mdtest benchmark plan, the metadata counterpart to the IOR plan I had published before. Hope you may find it useful. Lustre MD Benchmark Methodology using mdtest http://goo.gl/UBs1p Lustre IO Benchmark Methodology using IOR http://goo.gl/7AWwQ