similar to: New lustre-community mailing list

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

Are you in Salt Lake City? We''ll be having an ''unofficial'' Birds of a Feather (BOF) session Wednesday evening the 14th, from 5:30pm to 7:30pm, at the Salt Lake Marriott Downtown City Creek 2nd floor Snowbird Rm. We''ve had a really busy year with some great progress around Lustre development in particular! Also some new important participants have joined. Lots

hello, does lustre support OSD T10 standard? Can it be used with IBM''s/Intel''s OSD initiator and target? Thanks, Ashish -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20071128/c2de31a6/attachment-0002.html

Hello, I am planning on deploying a few more clients in my lustre environment and was wondering which client version to install. I know it is okay to run a newer client version than your lustre server for upgrade purposes. However, would it be okay to be in this state for a longer period of time (for the life of this filesystem)? My lustre server is currently running 1.8.1.1 on RHEL 5.3 and I

I am in the process of doing an upgrade of our 1.8.6 Lustre servers to 2.1.3. We have quite a few clients that all run versions of the lustre client close to 1.8.6. Is there a compatibility matrix somewhere that will show what clients will work with what servers? We don''t want to do the upgrade all at once so would like to know what order to make the changes. Brett -- /) _ _

Just checking to be sure this isn''t a known bug or problem. I couldn''t find a bz for this, but it would appear that tunefs.lustre --print fails on a lustre mdt or ost device if mounted with mmp. Is this expected behavior? TIA mds1-gps:~ # tunefs.lustre --print /dev/mapper/mdt1 checking for existing Lustre data: not found tunefs.lustre FATAL: Device /dev/mapper/mdt1 has not

Will lustre-1.5.95 build with 2.6.18-vanilla kernel? Which_patch doesn''t contain this kernel but I could see them in the series files. Do somebody have experience in building the same? I tried to do it but lot of errors after applying the patches in 2.6.18-vanilla series. Thanks, Venkat

Hi, I get the following error when I try to mount lustre on the clients. Permanent disk data: Target: lustre-OSTffff Index: unassigned Lustre FS: lustre Mount type: ldiskfs Flags: 0x72 (OST needs_index first_time update ) Persistent mount opts: errors=remount-ro,extents,mballoc Parameters: mgsnode=164.107.119.231 at tcp sh: losetup: command not found mkfs.lustre: error 32512 on losetup:

Hello, we wounder whether is it possible to add OSTs to the Lustre with quota support without making it offline? We tried to do this but all quota information was lost. Despite the fact that OST was formatted with quota support we are receiving this error message: Lustre: 3743:0:(lproc_quota.c:447:lprocfs_quota_wr_type()) lustrefs-OST0016: quotaon failed because quota files

Hi there, When Lustre is configured in an environment where there are multiple paths to the same destination of the same length (i.e. two paths, each one hop away), which path(s) will be used for sending and receiving data? I have my cluster configured with two OSTs with two GigE NICs in each. I am seeing identical performance metrics when I use LACP to aggregate, and when I use two separate

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

Hi, I have a query regarding Lustre Throughput Numbers with mdtest benchmark.I am running mdtest benhmark with following options :- /home/meshram/mpich2-new/mpich2-1.4/mpich2-install/bin/mpirun -np 256 -hostfile ./hostfile ./mdtest -z 3 -b 10 -I 5 -v -d /tmp/l66 where , mdtest - is the standard benchmark to test metadata operations. [ https://computing.llnl.gov/?set=code&page=sio_downloads

Hi, I have a query regarding Lustre Throughput Numbers with mdtest benchmark.I am running mdtest benhmark with following options :- /home/meshram/mpich2-new/mpich2-1.4/mpich2-install/bin/mpirun -np 256 -hostfile ./hostfile ./mdtest -z 3 -b 10 -I 5 -v -d /tmp/l66 where , mdtest - is the standard benchmark to test metadata operations. [ https://computing.llnl.gov/?set=code&page=sio_downloads

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

For future filesystem compatibility, we are wondering if there are any Lustre MDT filesystems in existence that have 2B or more total inodes? This is fairly unlikely, because it would require an MDT filesystem that is > 8TB in size (which isn''t even supported yet) and/or has been formatted with specific options to increase the total number of inodes. This can be checked with

Hello, We have an IA64 cluster with 64K kernel page size and we use lustre 1.4.8.1 and e2fsprogs-1.39cfs8. We meet the following problem : 1. I Create a Lustre file system, then start this file system and mount it on a client node 2. On this client node, I copy 2 files in my /mnt/lustre 3. I umount Lustre file system on this client node then stop Lustre file system 4. I use then :

Hi, has anyone tried to compile the lustre patchless client on a debian linux for arm architecture? Could be possible to do? Thanks in advance.

Hello, I am trying to mount a lustre filesystem thru an ib2ip gateway. The MDS''s have infiniband connections. The client nodes are tcp/ip connections. I am able to route between the client nodes and the MDS''s. I have the following in /etc/fstab: abe-mds1 at o2ib0,abe-mds2 at o2ib0:/home/client /abehome lustre _netdev,flock 0 0 I get the following when trying

Since in Linux we are mostly a debian shop we''d like to stick with debian for our calculation nodes if possible. So I wanted to ask the lustre 2.2 instructions for Debian are they more or less relevant to lustre 2.4/2.5 or am I going headlong into a tall brick wall. Also are newer clients backwards compatible with older server software? I am currently just setting up a demo environment