[lustre-discuss] LBUG: 2.5.16, EL8 Linux 4.18.0-553.30.1 in 'll_truncate_inode_pages

[Andreas Dilger]

You can always take the patch and apply it locally to your clients to see if it fixes the issue.

Cheers, Andreas

On Jan 2, 2025, at 06:27, Aurelien Degremont <adegremont at nvidia.com> wrote:


You don't often get email from adegremont at nvidia.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Hello Peter,

This is indeed this bug, and as the ticket said, this is not fixed in 2.15.x, only 2.16.0
I've no idea if this will ever make 2.15.x


Aurélien

________________________________
De : lustre-discuss <lustre-discuss-bounces at lists.lustre.org> de la part de Peter Grandi <pg at lustre.list.sabi.co.UK>
Envoyé : jeudi 2 janvier 2025 13:45
À : list Linux fs Lustre <lustre-discuss at lists.Lustre.org>
Objet : [lustre-discuss] LBUG: 2.5.16, EL8 Linux 4.18.0-553.30.1 in 'll_truncate_inode_pages

External email: Use caution opening links or attachments


Relatively rarely across a 200-machine cluster I get an LBUG on the
clients which seems triggered by specific access patterns (most jobs do
not trigger it) and looks quite similar to:

  https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.whamcloud.com%2Fbrowse%2FLU-16637&data=05%7C02%7Cadegremont%40nvidia.com%7Cf5d4d3826d8a48b637a508dd2b2bc296%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638714189150988150%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=D4tRyR%2BoN2euGk8W5zjL1Y3ksJ6j0iFuJ7%2FS%2BYidmIg%3D&reserved=0<https://jira.whamcloud.com/browse/LU-16637>
  https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.lustre.org%2Fpipermail%2Flustre-devel-lustre.org%2F2023-April%2F011016.html&data=05%7C02%7Cadegremont%40nvidia.com%7Cf5d4d3826d8a48b637a508dd2b2bc296%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638714189151026923%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Qwm%2Blb7Wb4nGaO%2Fb6wW6LPUuW22DsLlwnUGG2R5wtik%3D&reserved=0<http://lists.lustre.org/pipermail/lustre-devel-lustre.org/2023-April/011016.html>
  https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.whamcloud.com%2F%3Fp%3Dfs%2Flustre-release.git%3Ba%3Dcommit%3Bh%3D7bb1e211d217d5a82ac2d5e4edad5ae018090761&data=05%7C02%7Cadegremont%40nvidia.com%7Cf5d4d3826d8a48b637a508dd2b2bc296%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638714189151046567%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=8JLPFy1CyyoJn9OrW8i6mnSo%2BW6Q3D2JSK0ZNKHCn%2Fg%3D&reserved=0<https://git.whamcloud.com/?p=fs/lustre-release.git;a=commit;h=7bb1e211d217d5a82ac2d5e4edad5ae018090761>

Since the LBUG is fatal all I get is the backtrace from the crash dump:

  lbug_with_loc.cxold.8+0x18
  ll_truncate_inode_pages_final+0xab
  vvp_prune+0x181
  cl_object_prune+0x58
  lov_layout_change.isra.49+0x1ba
  lov_conf_set+0x391
  cl_conf_set+0x60
  ll_layout_conf+0x14b
  ? _ptlrpc_req_finished+0x54d
  ll_layout_lock_set+0x3df
  ? ll_take_md_lock+0x148
  ll_layout_refresh+0x1cc
  vvp_io_init+0x22e
  cl_io_init0.isra.14+0x86
  ll_file_io_generic+0x388
  ? file_update_time+0x62
  ? srso_return_thunk+0x5
  ? __generic_file_write_iter+0x102
  ll_file_write_iter+0x558
  ? kmem_cache_freee+0x116
  new_sync_write+0x112
  vfs_write+0x5a

If this is a manifestation of LU-16637 there is a fix, but I have
checked the changelogs and LU-16637 is listed as applied to 2.16.0 but
it does not seem to be listed in the 2.15.[1-6] changelogs.
_______________________________________________
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.lustre.org%2Flistinfo.cgi%2Flustre-discuss-lustre.org&data=05%7C02%7Cadegremont%40nvidia.com%7Cf5d4d3826d8a48b637a508dd2b2bc296%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638714189151061516%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5zgL9DVZ6HA1M630A1e4RSajZnPBoCfQA%2BuryjBnbfk%3D&reserved=0<http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org>
_______________________________________________
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20250102/5f7098b7/attachment-0001.htm>