text:
Heathcote Williams

John Henley Heathcote-Williams (15 November 1941 – 1 July 2017), known as Heathcote Williams, was an English poet, actor, political activist and dramatist. He wrote a number of book-length polemical poems including Autogeddon, Falling for a Dolphin and Whale Nation, which in 1988 was described by Philip Hoare as "the most powerful argument for the newly instigated worldwide ban on whaling." Williams invented his idiosyncratic "documentary/investigative poetry" style which he put to good purpose bringing a diverse range of environmental and political matters to public attention. His last published work, American Porn was a critique of the American political establishment and the election of President Donald Trump; its publication date was the day of Trump's inauguration (20 January 2017). In June 2015 he published a book-length investigative poem about the "Muslim Gandhi", Khan Abdul Ghaffar Khan, Badshah Khan.

As well as being a playwright and screenwriter, Williams appeared in a number of independent and Hollywood films and was among the celebrity guests in the last episode of season 4 of Friends, '"The One With Ross's Wedding"'. He played Prospero in Derek Jarman's The Tempest (1979) and appeared in several "arthouse" films, including Orlando (1992), as well as the Hollywood film Basic Instinct 2 (2006). Al Pacino played the part of a Williams fan in a spoof arts documentary, Every Time I Cross the Tamar I Get into Trouble. Williams also wrote lyrics, collaborating with Marianne Faithfull among others.

Williams was a keen naturalist and discovered a new species of honey-producing wasp in the Argentine pampas, an event he recorded in a book of poems called Forbidden Fruit. Williams was a magician and a member of The Magic Circle. He wrote a TV play called What the Dickens! about Charles Dickens's penchant for performing magic shows. Bob Hoskins taught him fire eating. When he went to demonstrate his newfound talent to then girlfriend Jean Shrimpton, he accidentally set himself alight on her doorstep.

Williams was a leading activist in the London squatting scene in the 1970s and ran a squatters "estate agency" called the "Ruff Tuff Cream Puff". In 1977 he and a couple of hundred fellow squatters established the "state" of Frestonia in Notting Hill and declared independence from Britain. The then Shadow Chancellor, Geoffrey Howe, wrote to express his support and Williams was appointed UK Ambassador. Frestonia lasted almost a decade and had its own institutions and postage stamps. Williams spray-painted graffiti on the walls of Buckingham Palace as a protest against the Queen signing Michael X's death warrant while there was no capital punishment in the UK. In the early 1970s, his agitational graffiti were a feature on the walls of the then low-rent end of London's Notting Hill district. The final paragraph of Williams' New York Times obituary summed up his philosophy: "If poetry isn't revolutionary, it's nothing," he told Saira Viola from the web publication Gonzo Today in 2015. "Poetry is heightened language, and language exists to effect change, not to be a tranquilizer."

Early life and career
John Henley Heathcote-Williams was born in Helsby, Cheshire. After his schooldays at Eton, he changed his name to Heathcote Williams. His father, Harold Heathcote-Williams, was a barrister (appointed Queen's Counsel) and his mother, (Margaret) Julian (née Henley) a clergyman's daughter. His first book was The Speakers (1964), an account of life at Speakers' Corner in London's Hyde Park, written when he was just 22 years old. The Speakers attracted enthusiastic reviews, with Harold Pinter describing it as "brilliant... a remarkable achievement and very, very funny". In 1974, it was adapted for the stage by the Joint Stock Theatre Company.

His first full-length play, AC/DC (1970), first staged at the Royal Court Theatre, is a critique of the burgeoning mental health industry; it includes a thinly veiled attack on 1960s alternative society, and the proponent of the anti-psychiatry movement, R.D. Laing. Its production did not, however, appear to impede cordial relations between the two men in later years. AC/DC won the London Evening Standard's Most Promising Play Award. It also received the 1972 John Whiting Award for being "a new and distinctive development in dramatic writing with particular relevance to contemporary society." It was described in the Times Literary Supplement in a front-page review by Charles Marowitz as "the first play of the 21st century." AC/DC was produced in New York City in 1971 at the Chelsea Theater Center at the Brooklyn Academy of Music.

Other plays include the one-act monologue Hancock's Last Half Hour, The Local Stigmatic, The Immortalist and the impossible to categorise Remember The Truth Dentist – an early effort, again at the Royal Court, directed by Ken Campbell.

The inaugural issue of the London Review of Books included an effusive profile by fellow Etonian Francis Wyndham titled The Magic of Heathcote Williams.

Poetry
Williams had often been reluctant to co-operate in the promotion of his work commercially, refusing, for example, to go to the US to promote AC/DC, to the despair of his publishers. The only book signing tour he ever did – "enough," he complained, "to cripple a rock-star" – was the result of relentless pressure from Jonathan Cape's PR department.

Energetic publicity efforts on Williams' behalf, the responsibility of Cape's Polly Samson, enabled him to reach a wider audience for his trilogy of book-length poems on environmental themes. Each of them was the result of detailed research and featured many photographs. Written some years earlier as visionary propaganda, they had otherwise been gathering dust in a corner of his then agent's office. The North American rights for the poem Whale Nation (1988) were sold at the Frankfurt Book Fair for $100,000; Williams donated his share of the advance to environmental organizations. According to another writer on this subject, Philip Hoare in 2008, it is an "epic plea for the future of the whale, a hymn to the beauty, majesty and intelligence of the largest mammals on earth, as well as a prayer for their protection... Whale Nation became the most powerful argument for the newly instigated worldwide ban on whaling, and for a moment, back in 1988, it seemed as if a shameful chapter in human history might finally be drawing to a close.".

Whale Nation was followed by Sacred Elephant (1989), which deals with the devastation of the natural environment, and Autogeddon (1991), which characterises the motor car's global death toll as, "A humdrum holocaust, the third world war nobody bothered to declare." Each poem was made into a film by BBC Television, Autogeddon being performed by Jeremy Irons. Williams' public readings of Whale Nation reduced some members of the audience to tears. His recordings for Naxos Records, which include readings from the Buddhist scriptures, Dante and the Bible, have won awards.

In 2011, Williams began a new collaboration with Roy Hutchins, who had performed Whale Nation, Autogeddon and Falling for a Dolphin in the 1980s. The result was Zanzibar Cats, a performance of recent short poems. In What's on Stage, the reviewer Michael Coveney wrote: "These wonderful poems seize on political absurdity, planetary destruction and social injustice with relish and delight, as well as great erudition and verbal dexterity."

In December 2011, Huxley Scientific Press published a collection of poems by Williams on science and nature entitled Forbidden Fruit. The title poem is an elegy for mathematician, computer pioneer, and wartime codebreaker Alan Turing, the centenary of whose birth occurred in 2012. The Beat poet Michael McClure called the book "a collection of inspirations … as rich and dark as wasp honey". At the end of 2012, Huxley Scientific Press published Shelley at Oxford: Blasphemy, Book-Burning, and Bedlam, written by Williams during the bicentenary of Shelley's expulsion from Oxford for atheism, aged 19.

Williams regularly published new work on the digital, resurrected International Times. Royal Babylon: The Criminal Record of the British Monarchy was made into a video installation by the filmmaker collective Handsome Dog, to coincide with Queen Elizabeth II's diamond jubilee, and his poems Lord of the Drones: The President and the White House Fly, Hollywoodland, and Was Moby Dick Behind 9/11? (2012) are currently being edited into a trilogy—Autopsy: The American Empire Dissected.

In June 2015, 'Badshah Khan: Islamic Peace Warrior' was published by Thin Man Press. Williams's "poetic investigation" reviews the life and legacy of Khan Abdul Ghaffar Khan (1890–1988).

Williams's riposte to the election of President Donald Trump, American Porn, was published by Thin Man Press on 20 January, Trump's inauguration day.

Political pamphlets
In 2016, Williams responded to contemporary political events with a pamphlet in the Swiftean tradition, an excoriating commentary on Boris Johnson entitled 'The Blond Beast of Brexit: a Study in Depravity'. The pamphlet was described by a review as "a 20,000-word collage of the most maniacal, hypocritical, and cruel things the former mayor has ever said or done".

Later that year, an updated and expanded version, 'Brexit Boris: From Mayor to Nightmare', was published by Public Reading Rooms.

Painting and sculpture
Williams's second bout of fame caused him to cease writing in effect, and turn to painting and sculpture full-time. Leading the life of a would-be recluse, he received prolonged tuition from the 'New Ruralist' artist Graham Ovenden, at the latter's home on the edge of Bodmin Moor, Cornwall. The result was an out-pouring of hundreds of canvases, including satirical pastiches of the works of Van Gogh, Claude Monet, Stanley Spencer, Lucian Freud and others. He also produced a number of sculptures of great piles of books, tottering and damp-swollen, elaborately hand-carved in wood.

Song-writing
Williams's occasional but typically anarchistic forays into the realm of lyric-writing include the uncategorisable and unreleased "Wrinkly Bonk", and "Why D'Ya Do It?", a sexually explicit exploration of carnal jealousy, for Marianne Faithfull's 1979 classic album Broken English. Williams's words were enough to cause a walk-out by the female workers on EMI's production line.

Magazines
Williams was for a time associate editor of the literary journal Transatlantic Review, as well as being one of those responsible for the alternative sex paper Suck. He was a frequent contributor to the London underground paper International Times during the 1970s, to the radical vegetarian magazine Seed and to The Fanatic, issues of which would appear sporadically and provocatively in different formats and various countries of Western Europe. In 1974, he launched his own mimeographed underground newspaper, The Sunday Head. It was published from his home in Notting Hill Gate, London at the time when he was also the impresario for Albion Free State's Meat Roxy, a series of music, dance and poetry events held in a squatted, redundant bingo hall near the Portobello market.

An anthology of his tracts and manifestos from this period, Severe Joy, was announced by his then publisher but for some reason never actually appeared. A sampling did appear in a bi-lingual, limited edition titled Manifestoes from the Rotterdam-based Cold Turkey Press as well as in the Manchester literary magazine Wordworks in 1975.

Film
The theme of Williams' early one-act play The Local Stigmatic is fame and its adverse consequences, performed by Al Pacino at an Off-Off-Broadway venue, with financial assistance from Jon Voight. In later years the film version became known as 'Pacino's secret project,' his debut as a director. It was finally released as part of the Pacino: An Actor's Vision box-set in 2007.

Williams' own film performances include Prospero in Derek Jarman's version of The Tempest (1979), Wish You Were Here (1987), Stormy Monday (1988), Sally Potter's Orlando (1992), The Browning Version (1994), The Steal (1995), Blue Juice (1995) with Catherine Zeta Jones, Bring Me the Head of Mavis Davis (1997), The Odyssey (1997), Cousin Bette (1998), The Legend of 1900 (1998) and Alice in Wonderland (1999). Williams also appeared in Hotel (2001) with Salma Hayek, which he also co-wrote, and enjoyed a steady stream of bit-parts in big-budget Hollywood productions, such as the ill-fated Basic Instinct 2 (2006) and City of Ember (2008).

Television

Williams' contact with television overlapped with his activity in community politics. In a 1970s experiment by the BBC in public access television Williams, in the guise of a tree, spoke for fifteen minutes on the virtues of life unencumbered by the rule of Westminster. Albion Free State was his name for a utopian vision of an England free from government and bosses. Williams was one of 120 or so squatters who had commandeered a small chunk of West London, just about visible from BBC Television Centre itself. Frestonia, as the extensive squat was known, had declared itself independent of Great Britain. The actor David Rappaport was proclaimed Foreign Minister and Williams served as ambassador to the UK. Postage stamps were issued bearing the face of Guy the Gorilla instead of the Queen; they made no mention of currency, but simply carried the legend, God Will Provide. The project, which exasperated the authorities for years, provoked much litigation before the bulldozers were finally able to move in.

Williams later applied his abilities as a conjurer – he was a member of The Magic Circle – to come up with a Christmas play based on Charles Dickens's enthusiasm for performing magic shows for his friends and extended family. What the Dickens! depicted the novelist, with the likes of Thomas Carlyle and Thackeray standing by to assist, as he manipulated "airy nothings" and assorted props to the delighted squeals of foundling children from the Thomas Coram Home. The production featured a young Ben Cross as Dickens, with a supporting cast that included Dinsdale Landen and Kenneth Haigh. It was broadcast by Channel 4 in Christmas 1983, with a repeat screening the following Christmas.

In July 1988 Williams made an extended appearance on the Channel 4 discussion programme After Dark, alongside Petra Kelly, James Lovelock, C.W. Nicol and others.

In March 1993, Williams was the subject of a half-hour spoof arts documentary, a meditation on fame and fandom titled Every Time I Cross the Tamar I Get into Trouble. Screened by Channel Four in its Without Walls slot, the BFI film database characterises the film thus: "An account of Heathcote William's work, and Al Pacino's obsession with his writing. Includes an interview with Harold Pinter and footage from Pacino's film The Local Stigmatic." The half-hour film was presented by the comedian and musician John Dowie, an avid collector of Williams memorabilia.

Personal life
Williams's personal life was always turbulent. An affair with the model Jean Shrimpton resulted in the writer setting himself alight on her doorstep. Whether this was intentional or the upshot of a magic stunt gone wrong – Williams at the time was an ardent fire-eater – is unknown. Although at the time, it was assumed Shrimpton had ended the relationship, in her autobiography published in the early 1990s, Shrimpton asserted that it was Williams who walked out on her.

Williams had a son, Charlie, born in 1989, from a relationship with novelist and journalist Polly Samson. In 1994 Samson married Pink Floyd guitarist David Gilmour, who became Charlie's adoptive father.

Williams and Samson had become involved with each other during the publication of Whale Nation, which Samson publicised and succeeded in turning into a best-selling volume despite its author's reluctance to promote his work (see §Poetry).

Williams lived in Oxford with longterm partner Diana Senior. They had two daughters and three grandchildren.

Illness and death
Williams died on 1 July 2017 in Oxford, of kidney failure after a long stay in hospital for a chest infection.

Audio

 * WILLIAMS: Sacred Elephant – NA209712 clip read by Heathcote Williams
 * YouTube – "Tell me all the swear words you know" Williams in movie Wish You Were Here

title: Heathcote Williams


text:
Category talk:Entactogens and empathogens

as entactogens and empathogens are the same thing, i've moved everything in those categories to here. --Heah 07:10, 22 Apr 2005 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text:
Charles Turner (Australian cricketer)

Charles Thomas Biass Turner (16 November 1862 – 1 January 1944) was a bowler who is regarded as one of the finest ever produced by Australia. Among his accomplishments were:

 * taking 283 wickets in the English season of 1888 for 11.27 runs each. This tally was 69 wickets ahead of Ted Peate's 1882 record, and has been bettered only by Tom Richardson in 1895 and Tich Freeman in 1928 and 1933.
 * taking 314 wickets in all matches in 1888.
 * taking 106 wickets in twelve matches in the Australian season of 1887–88 – a record for any bowler in Australia
 * taking 17 wickets for 50 runs against An England Eleven at Hastings in 1888. Of these 17, 14 were bowled, two lbw and one stumped.
 * being the first Australian bowler to reach 100 wickets in Test matches.
 * his 12 for 87 against England in his record season of 1887–1888 is still the best bowling analysis for a Test at the SCG.
 * the only bowler to take 50 wickets in their first six Test matches.

Turner was born in Bathurst, New South Wales. His early adventures in first-class cricket were unsuccessful, but in 1886–87, when he moved from Bathurst to Sydney to become a banker, his skill developed to a remarkable degree with 70 first-class wickets at 7.68 runs each from just seven matches. In two games against Victoria he took eighteen wickets for 184 runs, but it was his excellence against Alfred Shaw's touring side that brought Turner acclaim in the English cricket community. In the first Test, after England were put in on a very sticky pitch, Turner took 6/15, and in the second his combined figures were nine for 93.

The following year, Turner, with the Australian pitches already notorious for being difficult after rain, he had a strong season in the wet weather of a La Niña summer, his best performances outside the Test including:

 * 10 for 45 v Arthur Shrewsbury's XI;
 * 16 for 79 in a second match v Arthur Shrewsbury's XI;
 * 11 for 119 v G.F. Vernon's XI at the MCG;
 * 5 for 17 in first innings for New South Wales v Victoria at the MCG.

In the English summer of 1888, along with John Ferris, Turner was prolific. However, he took ten for 53 in Australia's only win in the three-Test series at Lord's and took 9 for 15 versus An England Eleven at Stoke-on-Trent. He showed ability as a batsman, scoring a maiden century at The Oval in the first game of the tour.

After three extremely prolific seasons, Turner could not maintain his productivity. With El Niño holding sway, the wickets in Australia in 1888–89 were unresponsive and Turner took only 29 wickets in six games, and even fewer the following season. However, still regarded as the best bowler for English conditions, Turner did not disappoint the selectors in 1890, taking 179 first-class wickets (215 in all games) but being unable to break England's dominance of Test cricket at the time.

In the following few Australian seasons, Turner continued to do well even if too little cricket was played for him to equal his records of the late 1880s. In the relatively dry English summer of 1893, Turner still was Australia's leading bowler with 148 wickets at 13.63, but the absence of Ferris and business commitments were slowly taking their toll on him. During this tour his speed was measured electronically at Woolwich Arsenal and timed at 81 feet per second, or 55 miles an hour.

When England next toured in 1894–95, Turner equalled Fred Spofforth's record of 94 Test wickets in the Second Test at Melbourne on 31 December 1894, two days after the England bowler Johnny Briggs. The three men briefly held the record together, but Turner missed the Third Test at Adelaide and Briggs overtook him. Briggs became the first man to claim 100 Test wickets in the Fourth Test at Sydney on 1 February 1895, Turner being the second on 4 February in his last Test match. Turner had the unique (in Test cricket) distinction of having Bobby Peel stumped for a pair on a sticky wicket in Sydney. His record in this Test series was, actually, his best since 1888, but two years later his banking business required him to move to Queensland, where he was not able then to continue playing cricket apart from one match for his benefit as late as the 1909–10 season – when he was 47 – that was not successful.

Many batsmen who played against him considered Turner without peer. He bowled right-hand medium pace with a relatively long and rhythmic run-up and a beautiful delivery that never aimed to exploit even his rather limited height of five feet nine inches (175 centimetres). He could vary his pace a great deal, and combined this with an accurate length and a sharply-turning off-break that made him very difficult on rain-affected wickets. This unplayability on treacherous pitches earned him the nickname "Terror" Turner.

However, Turner continued to do service to the game in Australia as an administrator right through the early twentieth century. He commented, notably, on how greatly the game in Australia changed after the era in which he played due to a drier climate and improved pitch preparation (and also covering of pitches in Shield matches from the 1930s), which made Australian pitches almost impossible for bowlers of his type and led to reliance on leg spin.

On 15 January 2007, Turner was named in the NSW Cricket Team All Time Twelve, as part of the celebrations of 150 years of the NSW Cricket Team.

Charles Turner's ashes are now in the council chambers of Bathurst and a plaque at the Bathurst Oval recognises his services to both cricket and to Bathurst. His father Charles Turner and his father before him, Robert Turner arrived from England as a free settler from Leeds, England owned and ran several hotels in Bathurst including the Royal Hotel which still stands.

title: Charles Turner (Australian cricketer)


text:
Pithing

Pithing is a technique used to immobilize or kill an animal by inserting a needle or metal rod into its brain.

It is regarded as a humane means of immobilizing small animals being observed in experiments, and while once common in commercial slaughtering is no longer practiced in some developed countries on animals intended for the human food supply due to the risks of embedded metal fragments and general spread of disease.

Current United States and European Union regulations prohibit importation of beef from cows pithed due to risk of bovine spongiform encephalopathy (BSE, also known as mad cow disease). It is, however, encouraged for animals in emergency or specific disease control situations where the meat will not be consumed.

Commercial slaughter
An animal is first immobilized through captive bolt stunning. A pithing cane or rod is then inserted into the stunning hole and pushed to its full length; the rod then remains locked in the hole and is disposed of with the animal. Double pithing destroys the spinal cord, thus killing the animal, and also may reduce the reflex kicking which occurs at stunning, and so contribute to the safety of the slaughterer. This method is also used when dealing with diseased animals in the case of epidemic or notifiable disease.

Disease control
Pithing is viewed as a humane way of killing an animal that is going to be slaughtered or otherwise killed for disease control or humane reasons, for example an animal which is severely injured in an accident. When animals must be killed humanely on farms for disease control purposes or in an emergency situation, disposable pithing rods allow the slaughterer to adopt best practice. They ensure humane slaughter and seal the stunning hole, reducing bleeding, and so provide good biosecurity protection and eliminate the need to bleed out the animal. Disposable devices will help to ensure that the rods do not represent a risk of disease spread, and that they remain with the animal when it is disposed. In the case of outbreak of notifiable or epidemic disease, government agencies and welfare organisations may develop contingency plans. "Planned stocking" may be necessary to ensure that rods are available at short notice in the event of a disease outbreak.

In science
Pithing is also a procedure used in laboratories to immobilize a biological specimen, for instance a frog. A needle is inserted through the rear base of the skull and wiggled, destroying the brain. The specimen remains living due to vital functions continuing without cerebral control, allowing it to be dissected while observing such living physiology as its beating heart and expansion and contraction of its lungs without causing further pain.

title: Pithing


text:
Wikipedia:Articles for deletion/3D Arcade

 This page is an archive of the discussion about the proposed deletion of the article below. This page is no longer live. Further comments should be made on the article's talk page rather than here so that this page is preserved as an historic record. The result of the debate was delete. — Xezbeth 06:54, May 2, 2005 (UTC)

3D Arcade
Very minor arcade company with only two locations in Bakersfield, California. No encyclopedic potential (not yet, at least). I suggest it be deleted. --Poiuyt Man (talk)  07:14, 22 Apr 2005 (UTC)
 * Delete. If the chain becomes larger and more notable in the future, we can then re-create the article. Firebug 07:15, 22 Apr 2005 (UTC)
 * Delete Not yet notable Dsmdgold 10:39, Apr 22, 2005 (UTC)
 * Keep Bakersfield cruft. Klonimus 13:11, 22 Apr 2005 (UTC)
 * Keep - notable enough, and a decent article in need of some slight cleanup. --Irishpunktom\talk 14:40, Apr 22, 2005 (UTC)
 * Delete. nonnotable. It is not a manufacturer of games, just another pachinko. Mikkalai 21:46, 22 Apr 2005 (UTC)
 * Delete, they just do tournaments etc. of OTHER COMPANIES' games. So, no, non-notable. My local fish-'n'-chip shop would probably have a more exciting story to tell revolving around the acquisition of its US/Euro-region cabinets despite the shop itself being located in New Zealand. Come on. Who adds this stuff anyway? Possible vanity. Master Thief Garrett 22:22, 22 Apr 2005 (UTC)
 * Concur, delete. Radiant_* 10:27, Apr 25, 2005 (UTC)

 * This page is now preserved as an archive of the debate and, like some other VfD subpages, is no longer 'live'. Subsequent comments on the issue, the deletion, or the decision-making process should be placed on the relevant 'live' pages. Please do not edit this page.


text:
Lustre (file system)

Lustre is a type of parallel distributed file system, generally used for large-scale cluster computing. The name Lustre is a portmanteau word derived from Linux and cluster. Lustre file system software is available under the GNU General Public License (version 2 only) and provides high performance file systems for computer clusters ranging in size from small workgroup clusters to large-scale, multi-site systems. Since June 2005, Lustre has consistently been used by at least half of the top ten, and more than 60 of the top 100 fastest supercomputers in the world, including the world's No. 1 ranked TOP500 supercomputer in November 2022, Frontier, as well as previous top supercomputers such as Fugaku, Titan and Sequoia.

Lustre file systems are scalable and can be part of multiple computer clusters with tens of thousands of client nodes, hundreds of petabytes (PB) of storage on hundreds of servers, and tens of terabytes per second (TB/s) of aggregate I/O throughput. This makes Lustre file systems a popular choice for businesses with large data centers, including those in industries such as meteorology, simulation, artificial intelligence and machine learning,  oil and gas, life science,  rich media, and finance. The I/O performance of Lustre has widespread impact on these applications and has attracted broad attention.

History
The Lustre file system architecture was started as a research project in 1999 by Peter J. Braam, who was a staff of Carnegie Mellon University (CMU) at the time. Braam went on to found his own company Cluster File Systems in 2001, starting from work on the InterMezzo file system in the Coda project at CMU. Lustre was developed under the Accelerated Strategic Computing Initiative Path Forward project funded by the United States Department of Energy, which included Hewlett-Packard and Intel. In September 2007, Sun Microsystems acquired the assets of Cluster File Systems Inc. including its ”intellectual property“. Sun included Lustre with its high-performance computing hardware offerings, with the intent to bring Lustre technologies to Sun's ZFS file system and the Solaris operating system. In November 2008, Braam left Sun Microsystems, and Eric Barton and Andreas Dilger took control of the project. In 2010 Oracle Corporation, by way of its acquisition of Sun, began to manage and release Lustre.

In December 2010, Oracle announced that they would cease Lustre 2.x development and place Lustre 1.8 into maintenance-only support, creating uncertainty around the future development of the file system. Following this announcement, several new organizations sprang up to provide support and development in an open community development model, including Whamcloud, Open Scalable File Systems, Inc. (OpenSFS), EUROPEAN Open File Systems (EOFS) and others. By the end of 2010, most Lustre developers had left Oracle. Braam and several associates joined the hardware-oriented Xyratex when it acquired the assets of ClusterStor, while Barton, Dilger, and others formed software startup Whamcloud, where they continued to work on Lustre.

In August 2011, OpenSFS awarded a contract for Lustre feature development to Whamcloud. This contract covered the completion of features, including improved Single Server Metadata Performance scaling, which allows Lustre to better take advantage of many-core metadata server; online Lustre distributed filesystem checking (LFSCK), which allows verification of the distributed filesystem state between data and metadata servers while the filesystem is mounted and in use; and Distributed Namespace Environment (DNE), formerly Clustered Metadata (CMD), which allows the Lustre metadata to be distributed across multiple servers. Development also continued on ZFS-based back-end object storage at Lawrence Livermore National Laboratory. These features were in the Lustre 2.2 through 2.4 community release roadmap. In November 2011, a separate contract was awarded to Whamcloud for the maintenance of the Lustre 2.x source code to ensure that the Lustre code would receive sufficient testing and bug fixing while new features were being developed.

In July 2012 Whamcloud was acquired by Intel, after Whamcloud won the FastForward DOE contract to prepare Lustre for use with exascale computing systems in the 2018 timeframe. OpenSFS then transitioned contracts for Lustre development to Intel.

In February 2013, Xyratex Ltd., announced it acquired the original Lustre trademark, logo, website and associated intellectual property from Oracle. In June 2013, Intel began expanding Lustre usage beyond traditional HPC, such as within Hadoop. For 2013 as a whole, OpenSFS announced request for proposals (RFP) to cover Lustre feature development, parallel file system tools, addressing Lustre technical debt, and parallel file system incubators. OpenSFS also established the Lustre Community Portal, a technical site that provides a collection of information and documentation in one area for reference and guidance to support the Lustre open source community. On April 8, 2014, Ken Claffey announced that Xyratex/Seagate was donating the lustre.org domain back to the user community, and this was completed in March, 2015.

In June 2018, the Lustre team and assets were acquired from Intel by DDN. DDN organized the new acquisition as an independent division, reviving the Whamcloud name for the new division.

In November 2019, OpenSFS and EOFS announced at the SC19 Lustre BOF that the Lustre trademark had been transferred to them jointly from Seagate.

Release history
Lustre file system was first installed for production use in March 2003 on the MCR Linux Cluster at the Lawrence Livermore National Laboratory, the third-largest supercomputer in the Top500 list at the time.

Lustre 1.0.0 was released in December 2003, and provided basic Lustre filesystem functionality, including server failover and recovery.

Lustre 1.2.0, released in March 2004, worked on Linux kernel 2.6, and had a "size glimpse" feature to avoid lock revocation on files undergoing write, and client side data write-back cache accounting (grant).

Lustre 1.4.0, released in November 2004, provided protocol compatibility between versions, could use InfiniBand networks, and could exploit extents/mballoc in the ldiskfs on-disk filesystem.

Lustre 1.6.0, released in April 2007, allowed mount configuration (“mountconf”) allowing servers to be configured with "mkfs" and "mount", allowed dynamic addition of object storage targets (OSTs), enabled Lustre distributed lock manager (LDLM) scalability on symmetric multiprocessing (SMP) servers, and provided free space management for object allocations.

Lustre 1.8.0, released in May 2009, provided OSS Read Cache, improved recovery in the face of multiple failures, added basic heterogeneous storage management via OST Pools, adaptive network timeouts, and version-based recovery. It was a transition release, being interoperable with both Lustre 1.6 and Lustre 2.0.

Lustre 2.0, released in August 2010, was based on significant internally restructured code to prepare for major architectural advancements. Lustre 2.x clients cannot interoperate with 1.8 or earlier servers. However, Lustre 1.8.6 and later clients can interoperate with Lustre 2.0 and later servers. The Metadata Target (MDT) and OST on-disk format from 1.8 can be upgraded to 2.0 and later without the need to reformat the filesystem.

Lustre 2.1, released in September 2011, was a community-wide initiative in response to Oracle suspending development on Lustre 2.x releases. It added the ability to run servers on Red Hat Linux 6 and increased the maximum ext4-based OST size from 24 TB to 128 TB, as well as a number of performance and stability improvements. Lustre 2.1 servers remained inter-operable with 1.8.6 and later clients.

Lustre 2.2, released in March 2012, focused on providing metadata performance improvements and new features. It added parallel directory operations allowing multiple clients to traverse and modify a single large directory concurrently, faster recovery from server failures, increased stripe counts for a single file (across up to 2000 OSTs), and improved single-client directory traversal performance.

Lustre 2.3, released in October 2012, continued to improve the metadata server code to remove internal locking bottlenecks on nodes with many CPU cores (over 16). The object store added a preliminary ability to use ZFS as the backing file system. The Lustre File System ChecK (LFSCK) feature can verify and repair the MDS Object Index (OI) while the file system is in use, after a file-level backup/restore or in case of MDS corruption. The server-side IO statistics were enhanced to allow integration with batch job schedulers such as SLURM to track per-job statistics. Client-side software was updated to work with Linux kernels up to version 3.0.

Lustre 2.4, released in May 2013, added a considerable number of major features, many funded directly through OpenSFS. Distributed Namespace Environment (DNE) allows horizontal metadata capacity and performance scaling for 2.4 clients, by allowing subdirectory trees of a single namespace to be located on separate MDTs. ZFS can now be used as the backing filesystem for both MDT and OST storage. The LFSCK feature added the ability to scan and verify the internal consistency of the MDT FID and LinkEA attributes. The Network Request Scheduler (NRS) adds policies to optimize client request processing for disk ordering or fairness. Clients can optionally send bulk RPCs up to 4 MB in size. Client-side software was updated to work with Linux kernels up to version 3.6, and is still interoperable with 1.8 clients.

Lustre 2.5, released in October 2013, added the highly anticipated feature, Hierarchical Storage Management (HSM). A core requirement in enterprise environments, HSM allows customers to easily implement tiered storage solutions in their operational environment. This release is the current OpenSFS-designated Maintenance Release branch of Lustre. The most recent maintenance version is 2.5.3 and was released in September 2014.

Lustre 2.6, released in July 2014, was a more modest release feature wise, adding LFSCK functionality to do local consistency checks on the OST as well as consistency checks between MDT and OST objects. The NRS Token Bucket Filter (TBF) policy was added. Single-client IO performance was improved over the previous releases. This release also added a preview of DNE striped directories, allowing single large directories to be stored on multiple MDTs to improve performance and scalability.

Lustre 2.7, released in March 2015, added LFSCK functionality to verify DNE consistency of remote and striped directories between multiple MDTs. Dynamic LNet Config adds the ability to configure and modify LNet network interfaces, routes, and routers at runtime. A new evaluation feature was added for UID/GID mapping for clients with different administrative domains, along with improvements to the DNE striped directory functionality.

Lustre 2.8, released in March 2016, finished the DNE striped directory feature, including support for migrating directories between MDTs, and cross-MDT hard link and rename. As well, it included improved support for Security-Enhanced Linux (SELinux) on the client, Kerberos authentication and RPC encryption over the network, and performance improvements for LFSCK.

Lustre 2.9 was released in December 2016 and included a number of features related to security and performance. The Shared Secret Key security flavour uses the same GSSAPI mechanism as Kerberos to provide client and server node authentication, and RPC message integrity and security (encryption). The Nodemap feature allows categorizing client nodes into groups and then mapping the UID/GID for those clients, allowing remotely administered clients to transparently use a shared filesystem without having a single set of UID/GIDs for all client nodes. The subdirectory mount feature allows clients to mount a subset of the filesystem namespace from the MDS. This release also added support for up to 16 MiB RPCs for more efficient I/O submission to disk, and added the  interface to allow clients to provide I/O hints to the servers to prefetch file data into server cache or flush file data from server cache. There was improved support for specifying filesystem-wide default OST pools, and improved inheritance of OST pools in conjunction with other file layout parameters.

Lustre 2.10 was released in July 2017 and has a number of significant improvements. The LNet Multi-Rail (LMR) feature allows bonding multiple network interfaces (InfiniBand, Omni-Path, and/or Ethernet) on a client and server to increase aggregate I/O bandwidth. Individual files can use composite file layouts that are constructed of multiple components, which are file regions based on the file offset, that allow different layout parameters such as stripe count, OST pool/storage type, etc. Progressive File Layout (PFL) is the first feature to use composite layouts, but the implementation is flexible for use with other file layouts such as mirroring and erasure coding. The NRS Token Bucket Filter (TBF) server-side scheduler has implemented new rule types, including RPC-type scheduling and the ability to specify multiple parameters such as JobID and NID for rule matching. Tools for managing ZFS snapshots of Lustre filesystems have been added, to simplify the creation, mounting, and management of MDT and OST ZFS snapshots as separate Lustre mountpoints.

Lustre 2.11 was released in April 2018 and contains two significant new features, and several smaller features. The File Level Redundancy (FLR) feature expands on the 2.10 PFL implementation, adding the ability to specify mirrored file layouts for improved availability in case of storage or server failure and/or improved performance with highly concurrent reads. The Data-on-MDT (DoM) feature allows small (few MiB) files to be stored on the MDT to leverage typical flash-based RAID-10 storage for lower latency and reduced IO contention, instead of the typical HDD RAID-6 storage used on OSTs. As well, the LNet Dynamic Discovery feature allows auto-configuration of LNet Multi-Rail between peers that share an LNet network. The LDLM Lock Ahead feature allows appropriately modified applications and libraries to pre-fetch DLM extent locks from the OSTs for files, if the application knows (or predicts) that this file extent will be modified in the near future, which can reduce lock contention for multiple clients writing to the same file.

Lustre 2.12 was released on December 21, 2018 and focused on improving Lustre usability and stability, with improvements the performance and functionality of the FLR and DoM features added in Lustre 2.11, as well as smaller changes to NRS TBF, HSM, and JobStats. It added LNet Network Health to allow the LNet Multi-Rail feature from Lustre 2.10 to better handle network faults when a node has multiple network interfaces. The Lazy Size on MDT (LSOM) feature allows storing an estimate of the file size on the MDT for use by policy engines, filesystem scanners, and other management tools that can more efficiently make decisions about files without a fully accurate file sizes or blocks count without having to query the OSTs for this information. This release also added the ability to manually restripe an existing directory across multiple MDTs, to allow migration of directories with large numbers of files to use the capacity and performance of several MDS nodes. The Lustre RPC data checksum added SCSI T10-PI integrated data checksums from the client to the kernel block layer, SCSI host adapter, and T10-enabled hard drives.

Lustre 2.13 was released on December 5, 2019 and added a new performance-related features Persistent Client Cache (PCC), which allows direct use of NVMe and NVRAM storage on the client nodes while keeping the files part of the global filesystem namespace, and OST Overstriping which allows files to store multiple stripes on a single OST to better utilize fast OSS hardware. As well, the LNet Multi-Rail Network Health functionality was improved to work with LNet RDMA router nodes. The PFL functionality was enhanced with Self-Extending Layouts (SEL) to allow file components to be dynamically sized, to better deal with flash OSTs that may be much smaller than disk OSTs within the same filesystem. The release also included a number of smaller improvements, such as balancing DNE remote directory creation across MDTs, using Lazy-size-on-MDT to reduce the overhead of "lfs find", directories with 10M files per shard for ldiskfs, and bulk RPC sizes up to 64 MB.

Lustre 2.14 was released on February 19, 2021 and includes three main features. Client Data Encryption implements fscrypt to allow file data to be encrypted on the client before network transfer and persistent storage on the OST and MDT. OST Pool Quotas extends the quota framework to allow the assignment and enforcement of quotas on the basis of OST storage pools. DNE Auto Restriping can now adjust how many MDTs a large directory is striped over based on size thresholds defined by the administrator, similar to Progressive File Layouts for directories.

Lustre 2.15 was released on June 16, 2022 and includes three main features. Client Directory Encryption expands on the fscrypt data encryption in the 2.14 release to also allow file and directory names to be encrypted on the client before network transfer and persistent storage on the MDT. DNE MDT space balancing automatically balances new directory creation across MDTs in the filesystem in round-robin and/or based on available inodes and space, which in turn helps distribute client metadata workload over MDTs more evenly. For applications using the NVIDIA GPU Direct Storage interface (GDS), the Lustre client can do zero-copy RDMA read and write from the storage server directly into the GPU memory to avoid an extra data copy from CPU memory and extra processing overhead. User Defined Selection Policy (UDSP) allows setting interface selection policies for nodes with multiple network interfaces.

Architecture
A Lustre file system has three major functional units:
 * One or more metadata servers (MDS) nodes that have one or more metadata target (MDT) devices per Lustre filesystem that stores namespace metadata, such as filenames, directories, access permissions, and file layout. The MDT data is stored in a local disk filesystem. However, unlike block-based distributed filesystems, such as GPFS and PanFS, where the metadata server controls all of the block allocation, the Lustre metadata server is only involved in pathname and permission checks, and is not involved in any file I/O operations, avoiding I/O scalability bottlenecks on the metadata server. The ability to have multiple MDTs in a single filesystem is a new feature in Lustre 2.4, and allows directory subtrees to reside on the secondary MDTs, while 2.7 and later allow large single directories to be distributed across multiple MDTs as well.
 * One or more object storage server (OSS) nodes that store file data on one or more object storage target (OST) devices. Depending on the server's hardware, an OSS typically serves between two and eight OSTs, with each OST managing a single local disk filesystem. The capacity of a Lustre file system is the sum of the capacities provided by the OSTs.
 * Client(s) that access and use the data. Lustre presents all clients with a unified namespace for all of the files and data in the filesystem, using standard POSIX semantics, and allows concurrent and coherent read and write access to the files in the filesystem.

The MDT, OST, and client may be on the same node (usually for testing purposes), but in typical production installations these devices are on separate nodes communicating over a network. Each MDT and OST may be part of only a single filesystem, though it is possible to have multiple MDTs or OSTs on a single node that are part of different filesystems. The Lustre Network (LNet) layer can use several types of network interconnects, including native InfiniBand verbs, Omni-Path, RoCE, and iWARP via OFED, TCP/IP on Ethernet, and other proprietary network technologies such as the Cray Gemini interconnect. In Lustre 2.3 and earlier, Myrinet, Quadrics, Cray SeaStar and RapidArray networks were also supported, but these network drivers were deprecated when these networks were no longer commercially available, and support was removed completely in Lustre 2.8. Lustre will take advantage of remote direct memory access (RDMA) transfers, when available, to improve throughput and reduce CPU usage.

The storage used for the MDT and OST backing filesystems is normally provided by hardware RAID devices, though will work with any block devices. Since Lustre 2.4, the MDT and OST can also use ZFS for the backing filesystem in addition to ext4, allowing them to effectively use JBOD storage instead of hardware RAID devices. The Lustre OSS and MDS servers read, write, and modify data in the format imposed by the backing filesystem and return this data to the clients. This allows Lustre to take advantage of improvements and features in the underlying filesystem, such as compression and data checksums in ZFS. Clients do not have any direct access to the underlying storage, which ensures that a malfunctioning or malicious client cannot corrupt the filesystem structure.

An OST is a dedicated filesystem that exports an interface to byte ranges of file objects for read/write operations, with extent locks to protect data consistency. An MDT is a dedicated filesystem that stores inodes, directories, POSIX and extended file attributes, controls file access permissions/ACLs, and tells clients the layout of the object(s) that make up each regular file. MDTs and OSTs currently use either an enhanced version of ext4 called ldiskfs, or ZFS/DMU for back-end data storage to store files/objects using the open source ZFS-on-Linux port.

The client mounts the Lustre filesystem locally with a VFS driver for the Linux kernel that connects the client to the server(s). Upon initial mount, the client is provided a File Identifier (FID) for the root directory of the mountpoint. When the client accesses a file, it performs a filename lookup on the MDS. When the MDS filename lookup is complete and the user and client have permission to access and/or create the file, either the layout of an existing file is returned to the client or a new file is created on behalf of the client, if requested. For read or write operations, the client then interprets the file layout in the logical object volume (LOV) layer, which maps the file logical offset and size to one or more objects. The client then locks the file range being operated on and executes one or more parallel read or write operations directly to the OSS nodes that hold the data objects. With this approach, bottlenecks for client-to-OSS communications are eliminated, so the total bandwidth available for the clients to read and write data scales almost linearly with the number of OSTs in the filesystem.

After the initial lookup of the file layout, the MDS is not normally involved in file IO operations since all block allocation and data IO is managed internally by the OST. Clients do not directly modify the objects or data on the OST filesystems, but instead delegate this task to OSS nodes. This approach ensures scalability for large-scale clusters and supercomputers, as well as improved security and reliability. In contrast, shared block-based filesystems such as GPFS and OCFS allow direct access to the underlying storage by all of the clients in the filesystem, which requires a large back-end SAN attached to all clients, and increases the risk of filesystem corruption from misbehaving/defective clients.

Implementation
In a typical Lustre installation on a Linux client, a Lustre filesystem driver module is loaded into the kernel and the filesystem is mounted like any other local or network filesystem. Client applications see a single, unified filesystem even though it may be composed of tens to thousands of individual servers and MDT/OST filesystems.

On some massively parallel processor (MPP) installations, computational processors can access a Lustre file system by redirecting their I/O requests to a dedicated I/O node configured as a Lustre client. This approach is used in the Blue Gene installation at Lawrence Livermore National Laboratory.

Another approach used in the early years of Lustre is the liblustre library on the Cray XT3 using the Catamount operating system on systems such as Sandia Red Storm, which provided userspace applications with direct filesystem access. Liblustre was a user-level library that allows computational processors to mount and use the Lustre file system as a client. Using liblustre, the computational processors could access a Lustre file system even if the service node on which the job was launched is not a Linux client. Liblustre allowed data movement directly between application space and the Lustre OSSs without requiring an intervening data copy through the kernel, thus providing access from computational processors to the Lustre file system directly in a constrained operating environment. The liblustre functionality was deleted from Lustre 2.7.0 after having been disabled since Lustre 2.6.0, and was untested since Lustre 2.3.0.

In Linux Kernel version 4.18, the incomplete port of the Lustre client was removed from the kernel staging area in order to speed up development and porting to newer kernels. The out-of-tree Lustre client and server is still available for RHEL, SLES, and Ubuntu distro kernels, as well as vanilla kernels.

Data objects and file striping
In a traditional Unix disk file system, an inode data structure contains basic information about each file, such as where the data contained in the file is stored. The Lustre file system also uses inodes, but inodes on MDTs point to one or more OST objects associated with the file rather than to data blocks. These objects are implemented as files on the OSTs. When a client opens a file, the file open operation transfers a set of object identifiers and their layout from the MDS to the client, so that the client can directly interact with the OSS node(s) that hold the object(s). This allows the client(s) to perform I/O in parallel across all of the OST objects in the file without further communication with the MDS, avoiding contention from centralized block and lock management.

If only one OST object is associated with an MDT inode, that object contains all the data in the Lustre file. When more than one object is associated with a file, data in the file is "striped" in chunks in a round-robin manner across the OST objects similar to RAID 0 in chunks typically 1 MB or larger. Striping a file over multiple OST objects provides significant performance benefits if there is a need for high bandwidth access to a single large file. When striping is used, the maximum file size is not limited by the size of a single target. Capacity and aggregate I/O bandwidth scale with the number of OSTs a file is striped over. Also, since the locking of each object is managed independently for each OST, adding more stripes (one per OST) scales the file I/O locking capacity of the file proportionately. Each file created in the filesystem may specify different layout parameters, such as the stripe count (number of OST objects making up that file), stripe size (unit of data stored on each OST before moving to the next), and OST selection, so that performance and capacity can be tuned optimally for each file. When many application threads are reading or writing to separate files in parallel, it is optimal to have a single stripe per file, since the application is providing its own parallelism. When there are many threads reading or writing a single large file concurrently, then it is optimal to have at least one stripe on each OST to maximize the performance and capacity of that file.

In the Lustre 2.10 release, the ability to specify composite layouts was added to allow files to have different layout parameters for different regions of the file. The Progressive File Layout (PFL) feature uses composite layouts to improve file IO performance over a wider range of workloads, as well as simplify usage and administration. For example, a small PFL file can have a single stripe on flash for low access overhead, while larger files can have many stripes for high aggregate bandwidth and better OST load balancing. The composite layouts are further enhanced in the 2.11 release with the File Level Redundancy (FLR) feature, which allows a file to have multiple overlapping layouts for a file, providing RAID 0+1 redundancy for these files as well as improved read performance. The Lustre 2.11 release also added the Data-on-Metadata (DoM) feature, which allows the first component of a PFL file to be stored directly on the MDT with the inode. This reduces overhead for accessing small files, both in terms of space usage (no OST object is needed) as well as network usage (fewer RPCs needed to access the data). DoM also improves performance for small files if the MDT is SSD-based, while the OSTs are disk-based. In Lustre 2.13 the OST Overstriping feature allows a single component to have multiple stripes on one OST to further improve parallelism of locking, while the Self-Extending Layout feature allows the component size to be dynamic during write so that it can cope with individual (flash) OSTs running out of space before the whole filesystem is out of space.

Metadata objects and DNE remote or striped directories
When a client initially mounts a filesystem, it is provided the 128-bit Lustre File Identifier (FID, composed of the 64-bit Sequence number, 32-bit Object ID, and 32-bit Version) of the root directory for the mountpoint. When doing a filename lookup, the client performs a lookup of each pathname component by mapping the parent directory FID Sequence number to a specific MDT via the FID Location Database (FLDB), and then does a lookup on the MDS managing this MDT using the parent FID and filename. The MDS will return the FID for the requested pathname component along with a DLM lock. Once the MDT of the last directory in the path is determined, further directory operations (for non-striped directories) will normally take place on that MDT, avoiding contention between MDTs.

For DNE striped directories, the per-directory layout stored on the parent directory provides a hash function and a list of MDT directory FIDs across which the directory is distributed. The Logical Metadata Volume (LMV) on the client hashes the filename and maps it to a specific MDT directory shard, which will handle further operations on that file in an identical manner to a non-striped directory. For readdir operations, the entries from each directory shard are returned to the client sorted in the local MDT directory hash order, and the client performs a merge sort to interleave the filenames in hash order so that a single 64-bit cookie can be used to determine the current offset within the directory.

In Lustre 2.15, the client LMV implements round-robin and space balanced default directory layouts, so that clients can use a large number of MDTs in a single filesystem more effectively. When a new subdirectories is created near the root of the filesystem (the top 3 directory levels by default), it will automatically be created as a remote directory one of the available MDTs (selected in sequential order) to balance space usage and load across servers. If the free space on the MDTs becomes imbalanced (more than 5% difference in free space and inodes) then the clients will bias new subdirectory creation toward MDTs with more free space in order to restore balance.

Locking
The Lustre distributed lock manager (LDLM), implemented in the OpenVMS style, protects the integrity of each file's data and metadata. Access and modification of a Lustre file is completely cache coherent among all of the clients. Metadata locks are managed by the MDT that stores the inode for the file, using FID as the resource name. The metadata locks are split into separate bits that protect the lookup of the file (file owner and group, permission and mode, and access control list (ACL)), the state of the inode (directory size, directory contents, link count, timestamps), layout (file striping, since Lustre 2.4), and extended attributes (xattrs, since Lustre 2.5). A client can fetch multiple metadata lock bits for a single inode with a single RPC request, but currently they are only ever granted a read lock for the inode. The MDS manages all modifications to the inode in order to avoid lock resource contention and is currently the only node that gets write locks on inodes.

File data locks are managed by the OST on which each object of the file is striped, using byte-range extent locks. Clients can be granted overlapping read extent locks for part or all of the file, allowing multiple concurrent readers of the same file, and/or non-overlapping write extent locks for independent regions of the file. This allows many Lustre clients to access a single file concurrently for both read and write, avoiding bottlenecks during file I/O. In practice, because Linux clients manage their data cache in units of pages, the clients will request locks that are always an integer multiple of the page size (4096 bytes on most clients). When a client is requesting an extent lock the OST may grant a lock for a larger extent than originally requested, in order to reduce the number of lock requests that the client makes. The actual size of the granted lock depends on several factors, including the number of currently granted locks on that object, whether there are conflicting write locks for the requested lock extent, and the number of pending lock requests on that object. The granted lock is never smaller than the originally requested extent. OST extent locks use the Lustre FID of the object as the resource name for the lock. Since the number of extent lock servers scales with the number of OSTs in the filesystem, this also scales the aggregate locking performance of the filesystem, and of a single file if it is striped over multiple OSTs.

Networking
The communication between the Lustre clients and servers is implemented using Lustre Networking (LNet), which was originally based on the Sandia Portals network programming application programming interface. Disk storage is connected to the Lustre MDS and OSS server nodes using direct attached storage (SAS, FC, iSCSI) or traditional storage area network (SAN) technologies, which is independent of the client-to-server network.

LNet can use many commonly used network types, such as InfiniBand and TCP (commonly Ethernet) networks, and allows simultaneous availability across multiple network types with routing between them. Remote Direct Memory Access (RDMA) is used for data and metadata transfer between nodes when provided by the underlying networks, such as InfiniBand, RoCE, iWARP, and Omni-Path, as well as proprietary high-speed networks such as Cray Aries and Gemini, and Atos BXI. High availability and recovery features enable transparent recovery in conjunction with failover servers.

Since Lustre 2.10 the LNet Multi-Rail (MR) feature allows link aggregation of two or more network interfaces between a client and server to improve bandwidth. The LNet interface types do not need to be the same network type. In 2.12 Multi-Rail was enhanced to improve fault tolerance if multiple network interfaces are available between peers.

LNet provides end-to-end throughput over Gigabit Ethernet networks in excess of 100 MB/s, throughput up to 11 GB/s using InfiniBand enhanced data rate (EDR) links, and throughput over 11 GB/s across 100 Gigabit Ethernet interfaces.

High availability
Lustre file system high availability features include a robust failover and recovery mechanism, making server failures and reboots transparent. Version interoperability between successive minor versions of the Lustre software enables a server to be upgraded by taking it offline (or failing it over to a standby server), performing the upgrade, and restarting it, while all active jobs continue to run, experiencing a delay while the backup server takes over the storage.

Lustre MDSes are configured as an active/passive pair exporting a single MDT, or one or more active/active MDS pairs with DNE exporting two or more separate MDTs, while OSSes are typically deployed in an active/active configuration exporting separate OSTs to provide redundancy without extra system overhead. In single-MDT filesystems, the standby MDS for one filesystem is the MGS and/or monitoring node, or the active MDS for another file system, so no nodes are idle in the cluster.

HSM (Hierarchical Storage Management)
Lustre provides the capability to have multiple storage tiers within a single filesystem namespace. It allows traditional HSM functionality to copy (archive) files off the primary filesystem to a secondary archive storage tier. The archive tier is typically a tape-based system, that is often fronted by a disk cache. Once a file is archived, it can be released from the main filesystem, leaving only a stub that references the archive copy. If a released file is opened, the Coordinator blocks the open, sends a restore request to a copytool, and then completes the open once the copytool has completed restoring the file.

In addition to external storage tiering, it is possible to have multiple storage tiers within a single filesystem namespace. OSTs of different types (e.g. HDD and SSD) can be declared in named storage pools. The OST pools can be selected when specifying file layouts, and different pools can be used within a single PFL file layout. Files can be migrated between storage tiers either manually or under control of the Policy Engine. Since Lustre 2.11, it is also possible to mirror a file to different OST pools with a FLR file layout, for example to pre-stage files into flash for a computing job.

HSM includes some additional Lustre components to manage the interface between the primary filesystem and the archive:
 * Coordinator: receives archive and restore requests and dispatches them to agent nodes.
 * Agent: runs a copytool to copy data from primary storage to the archive and vice versa.
 * Copytool: handles data motion and metadata updates. There are different copytools to interface with different archive systems. A generic POSIX copytool is available for archives that provide a POSIX-like front-end interface. Copytools are also available for the High Performance Storage System (HPSS), Tivoli Storage Manager (TSM), Amazon S3, and Google Drive.
 * Policy Engine: watches filesystem Changelogs for new files to archive, applies policies to release files based on age or space usage, and communicates with MDT and Coordinator. The Policy Engine can also trigger actions like migration between, purge, and removal. The most commonly used policy engine is RobinHood, but other policy engines can also be used.

HSM also defines new states for files including:
 * Exist: Some copy, possibly incomplete exists in a HSM.
 * Archive: A full copy exists on the archive side of the HSM.
 * Dirty: The primary copy of the file has been modified and differs from the archived copy.
 * Released: A stub inode exists on an MDT, but the data objects have been removed and the only copy exists in the archive.
 * Lost: the archive copy of the file has been lost and cannot be restored
 * No Release: the file should not be released from the filesystem
 * No Archive: the file should not be archived

Deployments
Lustre is used by many of the TOP500 supercomputers and large multi-cluster sites. Six of the top 10 and more than 60 of the top 100 supercomputers use Lustre file systems. These include the 700PB 13 TB/s Orion filesystem for the Frontier supercomputer at Oak Ridge National Laboratory (ORNL), Fugaku and K Computer at the RIKEN Advanced Institute for Computational Science, Tianhe-1A at the National Supercomputing Center in Tianjin, China, LUMI at CSC, Jaguar and Titan at ORNL, Blue Waters at the University of Illinois, and Sequoia and Blue Gene/L at Lawrence Livermore National Laboratory (LLNL).

There are also large Lustre filesystems at the National Energy Research Scientific Computing Center, Pacific Northwest National Laboratory, Texas Advanced Computing Center, Brazilian National Laboratory of Scientific Computing, and NASA in North America, in Asia at Tokyo Institute of Technology, in Europe at CEA, and many others.

Commercial technical support
Commercial technical support for Lustre is often bundled along with the computing system or storage hardware sold by the vendor. Some vendors include Hewlett-Packard (as the HP StorageWorks Scalable File Share, circa 2004 through 2008), ATOS, Fujitsu. Vendors selling storage hardware with bundled Lustre support include Hitachi Data Systems (2012), DataDirect Networks (DDN), Aeon Computing, and others. It is also possible to get software-only support for Lustre file systems from some vendors, including Whamcloud.

Amazon Web Services offers Amazon FSx for Lustre, a fully managed service, making it easy to launch and run high-performance file systems cost effectively in their cloud.

Documentation

 * Understanding Lustre Internals, Second Edition
 * Internal workings of Lustre file system and its core subsystems

Information wikis

 * Lustre Community wiki
 * Lustre (DDN) wiki
 * Lustre (OpenSFS) wiki

Community foundations

 * OpenSFS
 * EOFS – European Open File System

Hardware/software vendors

 * DataDirect Networks (DDN)
 * Hewlett Packard Enterprise / Cray (including former Xyratex employees )
 * NetApp
 * Aeon Computing

title: Lustre (file system)


text:
Talk:Lord Omar Khayyam Ravenhurst

I feel this Item should link directly to the extensive page about Kerry Thornley. The only new information - his date of death in the discordian calendar - could be moved there (and should include a link to that calendar). If no-one beats me to it I'll make those changes as soon as I find the time to learn how to do this correctly. (BjKa)

title: Talk:Lord Omar Khayyam Ravenhurst


text:
KTM Komuter

KTM Komuter is a commuter rail system in Malaysia operated by Keretapi Tanah Melayu (KTM). It was introduced in 1995 to provide local rail services in Kuala Lumpur and the surrounding Klang Valley suburban areas. Services were later expanded to other parts of Malaysia with the introduction of the Northern and Southern sectors.

The service uses air-conditioned electric multiple units in 3 and 6 car formations.

KTM Komuter contributed RM146.2 million to group revenue in 2017, carrying a total of 37.235 million passengers. The total number of passengers travelling with KTM Komuter in 2017 shows a decrease of 10.2%. This can be attributed to reduced service frequency due to the ongoing Klang Valley Double Tracking (KVDT) rehabilitation project.

Central Sector

KTM Komuter's 287 km (179 mi) network in the Central Sector mainly covers the Klang Valley. It has 53 stations. It consists of two cross-city routes, namely the KTM Tanjung Malim-Port Klang Line and the KTM Batu Caves-Pulau Sebang Line.

Transfers between the two main lines can be made at any of the four stations on the central core: KL Sentral, Kuala Lumpur, Bank Negara and Putra. Same-platform or cross-platform interchange is available at Kuala Lumpur.

The KTM KL Sentral-Terminal Skypark Line is a limited express service for passengers headed towards Subang Airport. To save time, it only stops at Subang Jaya station. The link is the second of its kind in Malaysia. However, it is temporarily suspended due to low ridership.

The routes have been modified over the years. Previously, Batu Caves-Pulau Sebang line (formerly, Seremban Line) trains would head towards Tanjung Malim while the Tanjung Malim-Port Klang line (formerly, Port Klang Line) trains would head to Batu Caves. Following a successful trial, the routes were swapped. Trains from Seremban began heading towards Batu Caves, while trains from Port Klang headed towards Tanjung Malim. The train service from Seremban was extended permanently to Pulau Sebang/Tampin, hence the current name of the line.

The service is subject to overcrowding during rush hours. Several steps were taken to alleviate this. Firstly, the operator introduced a new queuing system, in which the lines are painted on the floor with three colour codes representing each of the train set. Trains were also run in 3+3 formations, although this has been discontinued with the introduction of six-car sets. An express service from Seremban to KL Sentral is available during rush hour.

Northern Sector
The KTM Komuter Northern Sector (KTM Komuter Utara) service initially operated between Gurun in Kedah, Butterworth in Penang and Kamunting in Perak. This followed the completion of electrification works on that stretch.

The route has been modified multiple times since. Today, there are two lines, namely the Padang Besar-Butterworth Line and the Ipoh-Butterworth Line. Butterworth, Bukit Tengah and Bukit Mertajam are interchange stations between the two lines.

Southern Sector (discontinued)
The KTM Komuter Southern Sector (Malay: KTM Komuter Sektor Selatan) operated from Seremban to Gemas following the completion of electrification works on that stretch. This was the second KTM Komuter service outside the Klang Valley after the northern counterpart. The Gemas and Batang Melaka stops were removed starting 20 June 2016 with the train running between Seremban and Pulau Sebang/Tampin. Subsequently, the shuttle service was terminated on 11 July 2016 when it was absorbed into the Batu Caves-Pulau Sebang Line. There are currently plans to reintroduce the Southern Sector line as a commuter service from Gemas to Johor Bahru after the completion of the double tracking project.

History
The double-tracking project, which cost cost RM 1.5 billion, began in 1990. The project covers over a 150 km route stretching as far as Rawang, Port Klang and Seremban. However, the completion was delayed as of January 1995, causing the service to not launch on time. The first phase of the service originally planned to begin in July 1995.

As part of KTM's efforts to get the public to "think commuter", KTM offered free rides of the service from 2 to 11 August 1995.

The service started on 12 August 1995 from Kuala Lumpur to Rawang, on what was the original Seremban Line. The commercial run of the service began two days later. The double-tracking project with 18 EMU trains and additional 62 trains purchased at RM 180 million. Each train carries about 240 passengers and would run at the speed of 100 kmh.

The line was extended to Salak Selatan on 29 September 1995. Operations between Sentul and Shah Alam began on 28 August 1995, on what was the original Port Klang Line. This line was extended to Klang on 29 September 1995. The Seremban Line was extended to Kajang on 20 November 1995 and to Seremban itself on 18 December 1995. This would form the Komuter network for more than a decade.

In the early 2000s, more stations were added along the existing route. KL Sentral was added on 16 April 2001 and served as the new transport hub of Kuala Lumpur. Mid Valley station was added on 23 August 2004, serving the surrounding Mid Valley Megamall. Kepong Sentral was added on 1 July 2006.

The Seremban-KL Sentral express service was introduced on 9 December 2004 The service was discontinued later before being reintroduced again on 25 July 2018. These services run only during the rush hour.

The route was expanded for the first time since 1995 when train services on the Seremban Line were extended to Rasa in 2007. Initially, KTM Komuter services to the new stations north of Rawang was run as a shuttle service. The route was extended to Kuala Kubu Bharu in January 2008, and finally to Tanjung Malim on 1 June 2009. The Rawang-Tanjung Malim shuttle service was absorbed into the main Port Klang Line on 11 July 2016.

Women-only coaches were introduced on 28 April 2010.

The Port Klang Line was extended to Batu Caves on 29 July 2010. Four intermediate new stations, Batu Kentonmen, Kampung Batu and Taman Wahyu were opened with this extension.

The Seremban Line was extended from Seremban to Sungai Gadut on 14 May 2011 with an intermediate station at Senawang, and to Rembau in 2013.

Northern Sector services were introduced on 11 September 2015 between Gurun in Kedah, Butterworth in Penang and Kamunting in Perak. This followed the completion of the Ipoh-Padang Besar Electrification and Double-Tracking Project in December 2014. On 1 January 2016, a second line was introduced between Butterworth and Padang Besar in Perlis, while on 17 January 2016, the Gurun-Butterworth-Kamunting route was replaced with two separate routes: Butterworth-Gurun and Butterworth-Kamunting. The three-line service operated until 1 July 2016 when the Butterworth-Gurun route was dropped, and subsequently on 1 September 2016, the route took on its current form.

Southern Sector services were introduced on 10 October 2015 following the completion of the Seremban-Gemas Electrified Double Tracking Project on 30 October 2013. This service is the second KTM Komuter service outside the Klang Valley after its northern counterpart. The Gemas and Batang Melaka stops were removed starting 20 June 2016 with the train running between Seremban and Pulau Sebang/Tampin. Subsequently, the shuttle service was terminated on 11 July 2016 when it was absorbed into the Seremban Line.

From 15 December 2015, the routes of Seremban Line and Port Klang Line were switched as part of a six-month trial. Trains from Seremban began heading towards Batu Caves, while trains from Port Klang headed towards Rawang, and vice versa. Transfers could be done at the four shared stations. This change was made permanent, and the name of the lines we changed; from Seremban Line and Port Klang Line to Batu Caves-Pulau Sebang Line and Tanjung Malim-Port Klang Line respectively.

The KL Sentral-Terminal Skypark Line to Subang Airport was introduced on 1 May 2018.

Beginning 10 September 2018, all service abolished the cash ticketing system, cashless ticketing method was then compulsory.

Stations
The Komuter service was largely built from existing lines, with minor alterations (i.e. removal or abandonment of lines and replacement of wooden sleepers with concrete ones). Relevant station platforms were added and heightened to allow easier access to Komuter trains travelling in both directions.

Major pre-independence stations including Kuala Lumpur station, Klang station, Port Klang station and Seremban station were retained and upgraded to support Komuter services. Smaller, wood-based stations and halts along the line that were built at around the same time were either demolished and replaced by modern brick-and-concrete counterparts, or simply abandoned. The only exception to the rule is the old Sentul station, which has remained in service years since KTM Komuter's launch, albeit with a replacement platform.

The layouts and sizes of the new station buildings, as of the launch of the service in 1995, vary by location but are generally divided into two classes:

 * Railway halts, consisting of a small single-storey structure with only ticket counters (a ticket booth, ticket machines and faregates). The stations are usually placed along straightforward dual-lane lines.
 * Medium-sized and single-storey stations, housing both the ticket counters and station offices, and typically stationed along three or more lines. Such stations are typically intended to support additional responsibilities, such as managing railway signals, controlling points and handling goods services. The stations themselves are similar in design to the original wood-based stations along the line with slight hints of Western colonial designs (arches, wooden-and-glass windows and wooden doors), but are larger and modernised.

Some stations also have parking facilities.

The platforms of the 1995 stations are virtually standardised, down to the design of the passenger semicircle-crossed shelters, the use of similarly-styled foot crossings to link all platforms, and the diamonds-based brickwork of the platforms.

Depending on the number of patrons through the years, each station has undergone upgrades or expansions that consist of either increasing the number of ticket counters or opening new facilities for use by passengers or railway staff. Taller, wider canopies were erected on the platforms of most stations to replace narrower, original versions in 2006 and 2007. The pace of the upgrades varies by location.

During the 2000s, new stations such as the Mid Valley station appeared in more modern designs, consisting primarily of high, curved canopies above the entire platforms. Certain new stations along dual-lane lines are also included with facilities typically reserved for medium-sized stations, such as the Rasa station. The Kuala Lumpur Sentral station, however, is housed under the concrete base of the transport hub, and is stark and utilitarian in design.

Rolling stock
The original Komuter rolling stock consists of three versions of three-car EMUs added over the course of three years, beginning in 1994. The EMUs were the first in KTM's history. All Komuter EMUs operate in multiple-unit formation, running from overhead single-phase 25 kV AC 50 Hz catenary supply, with two driving cars and 1 trailer car in between. The EMUs were state-of-the-art, with remote-controlled pneumatic doors, Automatic Train Protection (ATP), train data recorder, wheel-slip control, GTO/IGBT traction electronics and regenerative braking. Up to the point of their introduction, no other KTM motive power used these modern train control systems.

Designated by KTM as "Class 8x"s, the EMUs wear a yellow, blue and grey livery, a departure from the predominantly grey livery that KTM adopted on other locomotives and passenger coaches at the time. A handful of EMUs include full advertisements on the sides of their cars.

The original Komuter fleet consisted of the following models:

The Class 8x suffered from more mechanical problems as they aged, especially the Class 81 and Class 82, which had poor reliability. The manufacturers of both classes had gone bankrupt since the trains were built, hence spare parts became unavailable. On paper, the number of serviceable units in 2010 stood at 53 out of the original 62, although there are reports of far fewer trains. Ultimately, four Class 81 sets were refurbished, albeit with new motors from Hyundai instead of Jenbacher. All Class 82s were taken out of service.

In 2012, six-car Class 92s were introduced, replacing most of the Class 8x in the central sector. A handful of them remain, usually on the Kl Sentral-Terminal Skypark Line or Sentul-Batu Caves shuttle, but many have been reallocated to the northern sector.

Ticketing
Passengers travelling on KTM Komuter may use the following ticketing options:

 * Mobile ticket (QR code) via KTMB Mobile app
 * Touch n' Go card (Klang Valley sector only. Not available at Northern sector).
 * Ticket Vending Machines (cashless payment via credit/debit cards only)
 * Ticketing counters at stations
 * Debit or Credit Card
 * NFC based mobile payment system (Apple Pay, Google Pay, Samsung Pay)

Ridership
Ridership statistics published by the Ministry of Transport are for all KTM Komuter services. No separate statistics for the individual lines or operational regions are published. Statistics before 1999 are also not available.

Incidents and accidents

 * On the evening of 3 March 2004, a Seremban-bound KTM Komuter train in the Seremban Line collided with the rear of another Komuter train facing the same direction, which had been waiting at a signal between Tiroi station and Seremban station for five minutes. Forty were injured, but no deaths were reported. The accident was ascribed to the faulty signal light (struck by lightning) that stopped the earlier train, though the driver of the rear-ending train is reported to have run a red light into the section occupied by the rear-ended train. The resulting crash disrupted KTM Komuter services along the line for a day. This is so far the worst accident involving the KTM Komuter service.
 * On 2 March 2007, a crane fell onto a KTM Komuter train track near the Sentul-Port Klang Route's Shah Alam Komuter station, stranding about 10,000 passengers and cancelling 40 trips. Alternative transport services were provided.
 * On 25 May 2007, a person was killed after he was hit by a KTM Komuter train while crossing the tracks illegally. Deaths in this manner have occurred along Komuter lines before.
 * On 27 February 2008, overhead power cables between Subang Jaya and Petaling stations of the Sentul-Port Klang route broke, causing all train services to be modified to run on the Sentul-Petaling route instead.
 * On 22 October 2009, a multipurpose vehicle plunged into the railway track as it was heading from Kuala Lumpur towards Subang Jaya. Train services were disrupted, and the vehicle was towed away 3 hours after the accident.
 * On 4 February 2013, A woman in her 50s was run over by a commuter train at the Taman Wahyu KTM Komuter Station. The victim was said to have been dragged 50m along the track in the incident.
 * On 15 February 2013 at 23:00, an out-of-service KTM Class 92 SCS 20 derailed near Shah Alam station while returning to Sentul depot for maintenance. No one was injured. The train was heavily damaged and was subsequently written off.
 * On 1 November 2013, a 3 coach KTM Class 83 derailed near Rawang station while moving through a track switch. No one was hurt in the incident. The two rear coaches were separated and towed away using a locomotive while the remaining front coach removed by use of cranes.
 * On 18 September 2017, KTM train services suffered a major disruption after an electrical cable snapped at KM361.76 on the tracks between the Rawang and Kuang stations, causing closure to both of the rail tracks.

title: KTM Komuter