Hi; What is the ETA on Lustre 1.8.4? I read on a previous thread (http://groups.google.com/group/lustre-discuss-list/browse_thread/thread /6030a620fcbc62d4/db747ffc635a2432?lnk=gst&q=1.8.4#db747ffc635a2432) the software would be released on July 31st. We are currently working with a customer who has hit bug 22897 (https://bugzilla.lustre.org/show_bug.cgi?id=22897) and requires the upgrade. Thanks, Osvaldo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100802/cfbfeec8/attachment.html
On Mon, Aug 02, 2010 at 12:04:24PM -0400, Osvaldo Rentas wrote:> What is the ETA on Lustre 1.8.4?The code is frozen (v1_8_4). The rpms are built and should be available soon on the download site. Johann
Wonderful news. On a related topic. Can the build scripts be made available (or a cleansed variant). It''s not that cumbersome to write one''s own but if they already exist it''d be handy to re-use them rather than recreating them, or at least use them as a reference. James Robnett NRAO/AOC Johann Lombardi wrote:> On Mon, Aug 02, 2010 at 12:04:24PM -0400, Osvaldo Rentas wrote: >> What is the ETA on Lustre 1.8.4? > > The code is frozen (v1_8_4). The rpms are built and should be available soon > on the download site. > > Johann > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss
Hi James, On Tue, Aug 03, 2010 at 10:42:00AM -0600, James Robnett wrote:> Wonderful news. On a related topic. Can the build scripts be > made available (or a cleansed variant). It''s not that cumbersome > to write one''s own but if they already exist it''d be handy to re-use > them rather than recreating them, or at least use them as a reference.Our build scripts are - and have alway been - available under the "build" directory (build/{lbuild,lbuild-rhel5,...}). Cheers, Johann
Any idea when 1.8.4 will be released? Is there a source code available somewhere so I can try to build it myself? Many thanks Wojciech On 3 August 2010 17:55, Johann Lombardi <johann.lombardi at oracle.com> wrote:> Hi James, > > On Tue, Aug 03, 2010 at 10:42:00AM -0600, James Robnett wrote: > > Wonderful news. On a related topic. Can the build scripts be > > made available (or a cleansed variant). It''s not that cumbersome > > to write one''s own but if they already exist it''d be handy to re-use > > them rather than recreating them, or at least use them as a reference. > > Our build scripts are - and have alway been - available under the "build" > directory (build/{lbuild,lbuild-rhel5,...}). > > Cheers, > Johann > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >-- Wojciech Turek Senior System Architect High Performance Computing Service University of Cambridge Email: wjt27 at cam.ac.uk Tel: (+)44 1223 763517 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100817/da0394e9/attachment.html
just git-pull from lustre repository and checkout the 1.8.4 On Tue, Aug 17, 2010 at 9:50 PM, Wojciech Turek <wjt27 at cam.ac.uk> wrote:> Any idea when 1.8.4 will be released? Is there a source code available > somewhere so I can try to build it myself? > > Many thanks > > Wojciech > > On 3 August 2010 17:55, Johann Lombardi <johann.lombardi at oracle.com> wrote: >> >> Hi James, >> >> On Tue, Aug 03, 2010 at 10:42:00AM -0600, James Robnett wrote: >> > Wonderful news. ?On a related topic. ?Can the build scripts be >> > made available (or a cleansed variant). ?It''s not that cumbersome >> > to write one''s own but if they already exist it''d be handy to re-use >> > them rather than recreating them, ?or at least use them as a reference. >> >> Our build scripts are - and have alway been - available under the "build" >> directory (build/{lbuild,lbuild-rhel5,...}). >> >> Cheers, >> Johann >> _______________________________________________ >> Lustre-discuss mailing list >> Lustre-discuss at lists.lustre.org >> http://lists.lustre.org/mailman/listinfo/lustre-discuss > > > > -- > Wojciech Turek > > Senior System Architect > > High Performance Computing Service > University of Cambridge > Email: wjt27 at cam.ac.uk > Tel: (+)44 1223 763517 > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss > >
James Robnett
2010-Dec-08 18:42 UTC
[Lustre-discuss] Determining /proc/fs/lustre/llite subdirectoy
Our clients have 2 or 3 different lustre filesystems mounted. We''re using Lustre 1.8.4 on RHEL 5.5. On clients I''d like to be able to toggle via a script the extents monitoring in /proc/fs/lustre/llite/lustre-XXXXXX/extents_stats Given a Lustre directory X how do I determine which lustre-XXXXX /proc directory that equates to. I know I''ve seen the question before but after searching the docs and googling old mailing lists I''m still stumped. I can cheat a bit since I know which MDS goes to which filesystem, do ''lctl list_nids'', see which MDS is the right one, then see which OSSes are grouped with that MDS and pull the trailing -osc-ffff-XXXXXXX suffix off and use that as the suffix for /proc/fs/lustre/llite but I have a vague recollection of a simpler more direct way. [lustre]# df . Filesystem 1K-blocks Used Available Use% Mounted on 10.64.1.11 at tcp:/lustre ................ [lustre]# /usr/sbin/lctl device_list 0 UP mgc MGC10.64.1.11 at tcp f7f9beb4-2f44-9219-f491-01dde044e308 5 1 UP lov lustre-clilov-ffff81021c910400 3de485df-1dfa-31a1-64d3-c54e948e6f22 4 2 UP mdc lustre-MDT0000-mdc-ffff81021c910400 3de485df-1dfa-31a1-64d3-c54e948e6f22 5 3 UP osc lustre-OST0000-osc-ffff81021c910400 3de485df-1dfa-31a1-64d3-c54e948e6f22 5 ... <remaining OSTS removed> 11 UP mgc MGC10.64.2.11 at tcp d9cd36e8-0748-60bd-3b0f-327efce98418 5 12 UP lov lustre-clilov-ffff810220907c00 c2e6c647-c01f-f841-f06d-1a97571a6aea 4 13 UP mdc lustre-MDT0000-mdc-ffff810220907c00 c2e6c647-c01f-f841-f06d-1a97571a6aea 5 14 UP osc lustre-OST0000-osc-ffff810220907c00 c2e6c647-c01f-f841-f06d-1a97571a6aea 5 ... <remaining OSTS removed> Since I want the filesystem on the first MDS (10.64.1.11) that equates to /proc/fs/lustre/llite/lustre-ffff81021c910400, this works but its a bit cumbersome to script. Is there a simpler way like ''lfs list-llite dir'' James Robnett NRAO/NM
Cliff White
2010-Dec-08 19:31 UTC
[Lustre-discuss] Determining /proc/fs/lustre/llite subdirectoy
On 12/08/2010 10:42 AM, James Robnett wrote:> > Our clients have 2 or 3 different lustre filesystems mounted. > We''re using Lustre 1.8.4 on RHEL 5.5. > > On clients I''d like to be able to toggle via a script the extents > monitoring in /proc/fs/lustre/llite/lustre-XXXXXX/extents_statsWhen you have multiple file systems, you really should use the --fsname parameter and give them different names. You apparently kept the default name of ''lustre''. The first field is actually the fsname, so for example on a test system I have two filesystems named ''test1'' and ''test2'' so on a typical client I have /proc/fs/lustre/llite/test1-XXXXXXX, and /proc/fs/lustre/llite/test2-XXXXXX. Using the fsname makes identifying the fs bits on the clients trival, since all the ID''s start with the fsname. (Which is why we added it) I think it may be possible to change the name with tunefs.lustre after creation. Using fsname is the ''simple more direct way'' you seek. cliffw> > Given a Lustre directory X how do I determine which lustre-XXXXX /proc > directory that equates to. I know I''ve seen the question before > but after searching the docs and googling old mailing lists I''m > still stumped. > > I can cheat a bit since I know which MDS goes to which filesystem, > do ''lctl list_nids'', see which MDS is the right one, then see which > OSSes are grouped with that MDS and pull the trailing -osc-ffff-XXXXXXX > suffix off and use that as the suffix for /proc/fs/lustre/llite > but I have a vague recollection of a simpler more direct way. > > [lustre]# df . > Filesystem 1K-blocks Used Available Use% Mounted on > 10.64.1.11 at tcp:/lustre ................ > > > [lustre]# /usr/sbin/lctl device_list > 0 UP mgc MGC10.64.1.11 at tcp f7f9beb4-2f44-9219-f491-01dde044e308 5 > 1 UP lov lustre-clilov-ffff81021c910400 > 3de485df-1dfa-31a1-64d3-c54e948e6f22 4 > 2 UP mdc lustre-MDT0000-mdc-ffff81021c910400 > 3de485df-1dfa-31a1-64d3-c54e948e6f22 5 > 3 UP osc lustre-OST0000-osc-ffff81021c910400 > 3de485df-1dfa-31a1-64d3-c54e948e6f22 5 > ...<remaining OSTS removed> > 11 UP mgc MGC10.64.2.11 at tcp d9cd36e8-0748-60bd-3b0f-327efce98418 5 > 12 UP lov lustre-clilov-ffff810220907c00 > c2e6c647-c01f-f841-f06d-1a97571a6aea 4 > 13 UP mdc lustre-MDT0000-mdc-ffff810220907c00 > c2e6c647-c01f-f841-f06d-1a97571a6aea 5 > 14 UP osc lustre-OST0000-osc-ffff810220907c00 > c2e6c647-c01f-f841-f06d-1a97571a6aea 5 > ...<remaining OSTS removed> > > Since I want the filesystem on the first MDS (10.64.1.11) that equates to > /proc/fs/lustre/llite/lustre-ffff81021c910400, this works but its a bit > cumbersome to script. Is there a simpler way like ''lfs list-llite dir'' > > James Robnett > NRAO/NM > > > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss