search for: writeconf

Hi, We run four-node Lustre 2.3, and I needed to both change hardware under MGS/MDS and reassign an OSS ip. Just the same, I added a brand new 10GE network to the system, which was the reason for MDS hardware change. I ran tunefs.lustre --writeconf as per chapter 14.4 in Lustre Manual, and everything mounts fine. Log regeneration apparently works, since it seems to do something, but exceedingly slowly. Disks show all but no activity, CPU utilization is zero across the board, and memory should be no issue. I believe it works, but curre...

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

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,

...is available under lustre/utils/loadgen for testing purposes. * See http://www.clusterfs.com/changelog.1.6.0.html for more. The new beta is known as 1.6beta7, (or internal version 1.5.97) Due to a change in the configuration log format, logs from earlier 1.6 betas should not be used. A "writeconf" should be executed (see the wiki) if upgrading an older 1.6 beta. Due to a wire protocol change, this beta will not interoperate with earlier 1.6 betas (but will interoperate with 1.4.x). (errata - the interoperability note in the ChangeLog incorrectly says beta8 instead of beta7.) RPMS and...

...is available under lustre/utils/loadgen for testing purposes. * See http://www.clusterfs.com/changelog.1.6.0.html for more. The new beta is known as 1.6beta7, (or internal version 1.5.97) Due to a change in the configuration log format, logs from earlier 1.6 betas should not be used. A "writeconf" should be executed (see the wiki) if upgrading an older 1.6 beta. Due to a wire protocol change, this beta will not interoperate with earlier 1.6 betas (but will interoperate with 1.4.x). (errata - the interoperability note in the ChangeLog incorrectly says beta8 instead of beta7.) RPMS and...

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

...fattr \--restore=/tmp/mdsea Run on all nodes (clients and OSS''s & MDS / MGS) to change MGS (where mgs is the name of the server and /dev/sdb1 is the name of the unmounted oat) tunefs.lustre --mgsnode=mgs at tcp0 /dev/sdb1 tunefs.lustre --erase-param --mgsnode=192.168.16.3 at tcp --writeconf /dev/sdc1 After copying with rsync, I had to cd /srv/mdt; rm CATALOGS OBJECTS/* on the new MDT partition. I also upgraded from 1.8.8 to 2. I managed to mount the Lustre filesystem and if I do lfs df -h, I get: NB> I deactivated those two OSTs below. [root at mgs data]# lfs df -h UUID...

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