similar to: lustre performance question

Hi, On a few of the hpc cluster nodes, i am seeing a new lustre error that is pasted below. The volumes are working fine and there is nothing on the oss and mds to report. LustreError: 5080:0:(import.c:607:ptlrpc_connect_interpret()) data3-OST0000_UUID at 192.168.2.98@tcp changed handle from 0xfe51139158c64fae to 0xfe511392a35878b3; copying, but this may foreshadow disaster

Hi, I am running samba and lprng for 4 hp laserjets. Sometimes a samba print job goes to the wrong printer. Normally everything works just fine. Shown below is the lprng acct log file enries for the concerned print job. Please notice that the print job was supposed to go to hp4050-mail, but ended up in hp8100. Any suggestions are much appreciated. Thanks Balagopal jobstart

As any of you using version 1.6 of Lustre knows, Lustre servers can now be started simply my mounting the devices it is using. Even an /etc/fstab entry can be used if you can have the mount delayed until the network is started. Given this change, you have also notices that we have eliminated the initscript for Lustre that used to exist for releases prior to 1.6. I''d like to take a

OK, so our old MDS had hardware issues so I configured a new MGS / MDS on a VM (this is a backup lustre filesystem and I wanted to separate the MGS / MDS from OSS of the previous), and then did this: For example: mount -t ldiskfs /dev/old /mnt/ost_old mount -t ldiskfs /dev/new /mnt/ost_new rsync -aSv /mnt/ost_old/ /mnt/ost_new # note trailing slash on ost_old/ If you are unable to connect both

Hi, Lustre manual 1.6 v18 says that that in production lustre debug level should be set to fairly low. Manual also says that I can verify that level by running following commands: # sysctl portals.debug This gives ne following error error: ''portals.debug'' is an unknown key cat /proc/sys/lnet/debug gives output: ioctl neterror warning error emerg ha config console cat

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

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

All, I''ve added a new 2.2 TB OST to my cluster easily enough, but this new disk array is meant to replace several smaller OSTs that I used to have of which were only 120 GB, 500 GB, and 700 GB. Adding an OST is easy, but how do I REMOVE the small OSTs that I no longer want to be part of my cluster? Is there a command to tell luster to move all the file stripes off one of the nodes?

Hi, I tried to compile lustre-client 2.0.0.1 on RHEL4 with kernel 2.6.9-89.0.28.EL-x86_64 and I got 3 errors and 1 warning during the compile. The compile is executed with -Werror option, and it fails in all 4 cases * Error: lustre_compat25.h CC [M] /usr/src/redhat/BUILD/lustre-2.0.0.1/lustre/fid/fid_handler.o In file included from

Some clients have been removed several weeks ago but are still listed in: ls -l /proc/fs/lustre/obdfilter/*/exports/ This was found after tracing back mystery tcp packets to the OSS. Although this is causing no damage, it raises the question of when former clients will be cleared from the OSS. Is there a way to manually remove these exports from the OSS? -- Regards, David

Hello, We had a problem with our disk controller that required a reboot. 2 of our OSTs remounted and went through the recovery window but clients hang trying to access them. Also /proc/fs/lustre/obdfilter/$UUID/ is empty for that OST UUID. LDISKFS FS on dm-5, internal journal on dm-5:8 LDISKFS-fs: delayed allocation enabled LDISKFS-fs: file extents enabled LDISKFS-fs: mballoc enabled

Hi Folks, We can see these massages on our MDS Feb 12 12:46:08 mds01 kernel: LDISKFS-fs warning (device dm-0): empty_dir: bad directory (dir #31452569) - no `.'' or `..'' Feb 12 12:46:08 mds01 kernel: LDISKFS-fs warning (device dm-0): ldiskfs_rmdir: empty directory has too many links (3) It seem to indicate that we have bad(corrupted) directory. Do you have any idea how to

Hi, I have 2 questions regarding building and installing Lustre server on Ubuntu. We have a running Lustre setup on RHEL and now trying to build and install on Ubuntu. 1. Whether latest Lustre (2.6+) server can be built on Ubuntu with the same steps as for RHEL? Or are there different steps for Ubuntu. 2. Has anyone tried this before and/or Whether Lustre2.6.x

Hi all, We are pleased to announce that Lustre 2.0 Beta1 is available for download. This is our next step in a series of milestone based pre-releases as we move towards Lustre 2.0 GA. This Beta includes 136 fixes since the Alpha7 milestone. Beta Milestone Criteria: * Tested for RHEL5/OEL5 x86_64 * Basic functional and recovery testing is passing consistently * mpi applications tests

Hi all, We are pleased to announce that Lustre 2.0 Beta1 is available for download. This is our next step in a series of milestone based pre-releases as we move towards Lustre 2.0 GA. This Beta includes 136 fixes since the Alpha7 milestone. Beta Milestone Criteria: * Tested for RHEL5/OEL5 x86_64 * Basic functional and recovery testing is passing consistently * mpi applications tests

Hi I used lustre-1.8.3 for Centos5.4. I patched the kernel according to Lustre 1.8 operations manual.pdf. I have a problem when I want to implement quota. My cluster configuration is: 1. one MGS/MDS host (with two devices: sda and sdb,respectively) with the following commands: 1) mkfs.lustre --mgs /dev/sda 2) mount -t lustre /dev/sda /mnt/mgt 3) mkfs.lustre --fsname=lustre

I''m a Lustre newbie who just joined this list. I''d appreciate any help on the following Lustre 2.4 issue I''m running into: Every time I mount the MDT, the mount appears to succeed but /var/log/messages contains the message: "LustreError: 11-0: lustre-MDT0000-lwp-MDT0000: Communicating with 0@lo, operation mds_connect failed with -11". The MDT uses 4 local

I compiled Lustre with a vanilla 2.6.12.6 kernel, and it seems to work quite well, so far. However, I can''t seem to successfully export a Lustre filesystem via NFS using it, so I''m guessing that NFS export support hasn''t made it into the 1.6beta, yet. Is that correct? Are there plans for another beta with that support included in the near future, or does someone

I compiled Lustre with a vanilla 2.6.12.6 kernel, and it seems to work quite well, so far. However, I can''t seem to successfully export a Lustre filesystem via NFS using it, so I''m guessing that NFS export support hasn''t made it into the 1.6beta, yet. Is that correct? Are there plans for another beta with that support included in the near future, or does someone

Dear All, we are facing problem while connecting o2ib module. Lustre 2.2 with centos 6.3 gives problem while loading o2ib module for infiniband. Thanks in advance Regards, Faheem Patel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20130326/d0eb1e39/attachment.html