- ceph-users - lists.ceph.io

Re: Ubuntu 24.04 with Tentacle
by Szabo, Istvan (Agoda) 24 Jul '26

24 Jul '26

Thank you very much, this makes me thinking again should I use cephadm or should we still stay with the manual setup and package based update for a heavy loaded critical block storage cluster :/ Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Marek Szuba via ceph-users <ceph-users(a)ceph.io> Sent: Thursday, 23 July 2026 18:33:59 To: ceph-users(a)ceph.io <ceph-users(a)ceph.io> Subject: [ceph-users] Re: Ubuntu 24.04 with Tentacle Email received from the internet. If in doubt, don't click any link nor open any attachment ! ________________________________ On 2026-07-23 07:06, Szabo, Istvan (Agoda) via ceph-users wrote: > Reading throught the Ceph documentation regarding different versions and I see here https://docs.ceph.com/en/latest/start/os-recommendations/#platforms and "Upcoming" text. > What does this mean exactly, which release is going to be "A" on Ubuntu 24.04? Hi Istvan, Not really the answer you have asked for because I am not a Ceph developer, we have however got some experience with running Tentacle on Noble so perhaps it will come in handy to you. We have in recent months upgraded all of our Ceph servers, in both production and development clusters, from Jammy to Noble. This has been originally for two reasons: - for several reasons I shan't bore you with we currently use Podman rather than Docker with cephadm, and it transpired that the Jammy version of Podman does not support namespace settings required by multi-container services like the cephadm-managed SMB gateways; - since the upgrade from Squid to Tentacle one of our cluster kept seeing CPU lock-ups (and subsequent "slow BlueStore operations" warnings) progressively appear for more and more OSDs, and having tried to no avail a lot of different configuration tweaks we got to the point where the remaining choices were "upgrade to a newer kernel" and "start replacing HBAs". So far - touch wood! - all the upgraded systems have been operating perfectly as far as Ceph is concerned. -- MS _______________________________________________ ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an email to ceph-users-leave(a)ceph.io ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

1 0

Re: Ec pool min size
by Anthony D'Atri 23 Jul '26

23 Jul '26

> > the default min_size for an EC pool is always k + 1, except when you choose m = 1, then it will be k (I won’t go into details if m = 1 is a good choice or not) I will. It’s a bad idea for data you can’t easily reconstruct or write off. Indeed if you need continued availability if 3 hosts out of 9 are down, I would just do replica3. You could do a custom or MSR CRUSH rule but that’s a rabbit hole. With Umbrella you should be able to transparently migrate pools to different protection schemes … one it gets a lot of shakeout. > . You can temporarily reduce min_size to k, in a disaster recovery scenario it can help. But k + 1 is a safety switch, so if you reduce it, ensure to set it back after recovery. If you plan to take multiple hosts offline on a regular basis, I’d recommend to consider a different EC profile. Note that you can’t change the EC profile of a pool, you would need to create a new pool with the desired profile and copy the data over to the new pool. > > Regards > Eugen > > Zitat von "GLE, Vivien via ceph-users" <ceph-users(a)ceph.io>: > >> Hi, >> >> >> We have a 9 hosts (3 per pod) cluster with 1 pool in EC 5+3 (host domain failure), I expected that shutting down 1 pod wouldn't affect our pg but I just discovered that the EC pool is in min_size 6 while trying it. >> >> >> Is min_size 6 important in this case ? Could I safely lower it to 5 or using another EC k+m would suit better ? >> >> >> Thanks ! >> >> >> Vivien >> _______________________________________________ >> ceph-users mailing list -- ceph-users(a)ceph.io >> To unsubscribe send an email to ceph-users-leave(a)ceph.io > > > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io > To unsubscribe send an email to ceph-users-leave(a)ceph.io

1 0

Re: Ec pool min size
by Eugen Block 23 Jul '26

23 Jul '26

Hi, the default min_size for an EC pool is always k + 1, except when you choose m = 1, then it will be k (I won’t go into details if m = 1 is a good choice or not). You can temporarily reduce min_size to k, in a disaster recovery scenario it can help. But k + 1 is a safety switch, so if you reduce it, ensure to set it back after recovery. If you plan to take multiple hosts offline on a regular basis, I’d recommend to consider a different EC profile. Note that you can’t change the EC profile of a pool, you would need to create a new pool with the desired profile and copy the data over to the new pool. Regards Eugen Zitat von "GLE, Vivien via ceph-users" <ceph-users(a)ceph.io>: > Hi, > > > We have a 9 hosts (3 per pod) cluster with 1 pool in EC 5+3 (host > domain failure), I expected that shutting down 1 pod wouldn't affect > our pg but I just discovered that the EC pool is in min_size 6 while > trying it. > > > Is min_size 6 important in this case ? Could I safely lower it to 5 > or using another EC k+m would suit better ? > > > Thanks ! > > > Vivien > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io > To unsubscribe send an email to ceph-users-leave(a)ceph.io

1 0

Ec pool min size
by GLE, Vivien 23 Jul '26

23 Jul '26

Hi, We have a 9 hosts (3 per pod) cluster with 1 pool in EC 5+3 (host domain failure), I expected that shutting down 1 pod wouldn't affect our pg but I just discovered that the EC pool is in min_size 6 while trying it. Is min_size 6 important in this case ? Could I safely lower it to 5 or using another EC k+m would suit better ? Thanks ! Vivien

1 0

Re: Ubuntu 24.04 with Tentacle
by Marek Szuba 23 Jul '26

23 Jul '26

On 2026-07-23 07:06, Szabo, Istvan (Agoda) via ceph-users wrote: > Reading throught the Ceph documentation regarding different versions and I see here https://docs.ceph.com/en/latest/start/os-recommendations/#platforms and "Upcoming" text. > What does this mean exactly, which release is going to be "A" on Ubuntu 24.04? Hi Istvan, Not really the answer you have asked for because I am not a Ceph developer, we have however got some experience with running Tentacle on Noble so perhaps it will come in handy to you. We have in recent months upgraded all of our Ceph servers, in both production and development clusters, from Jammy to Noble. This has been originally for two reasons: - for several reasons I shan't bore you with we currently use Podman rather than Docker with cephadm, and it transpired that the Jammy version of Podman does not support namespace settings required by multi-container services like the cephadm-managed SMB gateways; - since the upgrade from Squid to Tentacle one of our cluster kept seeing CPU lock-ups (and subsequent "slow BlueStore operations" warnings) progressively appear for more and more OSDs, and having tried to no avail a lot of different configuration tweaks we got to the point where the remaining choices were "upgrade to a newer kernel" and "start replacing HBAs". So far - touch wood! - all the upgraded systems have been operating perfectly as far as Ceph is concerned. -- MS

1 0

Guidance Required for Changing Ceph Squid Development Version to Stable Release
by Kathirvel T 23 Jul '26

23 Jul '26

Hello Ceph Community, We are looking for guidance regarding our existing Ceph cluster. Our cluster was deployed using ceph-ansible and is currently running the Squid development release (v19.3.0). We are planning to adopt the cluster into cephadm using the cephadm-adopt playbook provided by ceph-ansible. Before proceeding, we would like to understand the recommended approach for changing our Ceph version from the Squid development release (v19.3.0) to the stable Squid release (v19.2.3). Cluster Details Deployment: ceph-ansible Current Version: Squid Development (v19.3.0) Health: HEALTH_OK Hosts: 4 MONs: 3 MGRs: 1 Active, 2 Standby OSDs: 15 (15 Up / 15 In) RGW: 1 daemon Pools: 15 Objects: ~1.64 million Usage: 17 TiB used, 9.2 TiB / 26 TiB avail We have the following questions: Is it possible to change from the Squid development version (v19.3.0) to the stable Squid release (v19.2.3)? Is this a supported approach, or is there a recommended alternative? Should we change to the stable release before adopting the cluster into cephadm, or is it better to perform the cephadm adoption first and then update the version? Are there any known limitations, prerequisites, or best practices we should be aware of before proceeding? Any guidance, recommendations, or references to relevant documentation would be greatly appreciated. Thanks & Regards, Kathirvel T Associate R&D Engineer mailto:manoj.kumar@zybisys.com kathirvel.t(a)zybisys.com https://www.zybisys.com https://in.linkedin.com/company/zybisys https://www.facebook.com/Zybisys/ https://www.instagram.com/ZyBiSys/ https://www.youtube.com/@zybisys https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

1 0

Ubuntu 24.04 with Tentacle
by Szabo, Istvan (Agoda) 23 Jul '26

23 Jul '26

Hi Developers, Reading throught the Ceph documentation regarding different versions and I see here https://docs.ceph.com/en/latest/start/os-recommendations/#platforms and "Upcoming" text. What does this mean exactly, which release is going to be "A" on Ubuntu 24.04? Thank you ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

1 0

Re: No container image for 17.2.9 on quay.io?
by Patrick Donnelly 22 Jul '26

22 Jul '26

Hi Robert, On Wed, Jul 22, 2026 at 5:19 AM Robert Sander via ceph-users <ceph-users(a)ceph.io> wrote: > Why is there no container image for 17.2.9 available on quay.io? The answer is here: https://docs.ceph.com/en/latest/releases/quincy/#v17-2-9-quincy -- Patrick Donnelly, Ph.D. He / Him / His Red Hat Partner Engineer IBM, Inc. GPG: 19F28A586F808C2402351B93C3301A3E258DD79D

1 0

Re: CephFS+snapshots - unable to open files/directories that are known to exist in snapshots on some clients
by Andras Pataki 22 Jul '26

22 Jul '26

Hi Xiubo and Dhariya, The way I was able to reproduce the problem was to look at the error log of my copy processes and take those files and check on them on the various clients. Today, unfortunately, all those files seem to be visible - and at the moment I don't have a way of reproducing the issue from scratch. I'm trying to see what could be done to set up the reproduction from scratch. If I manage to do that, I'll try to gather some information on whether this is a client issue (i.e. flushing the client caches changes anything) or whether it comes from the MDS. Unfortunately the MDS in question is a very busy one, our main file system MDS, so there are limits to what I can do to it. Andras On 7/22/26 5:37 AM, Xiubo Li via ceph-users wrote: > Hi Dhairya, > > Yeah, makes sense. > > Since I couldn't reproduce this locally, @Andras Pataki Could you help > reproduce it by enabling the debug logs as Dhairya mentioned? And if > possible please also try with the fuse client to see could you see > too. > > Thanks > Xiubo > > On Wed, 22 Jul 2026 at 17:11, Dhairya Parmar via dev <dev(a)ceph.io> wrote: >> Hi Xiubo, >> >> I did look at the codepaths you shared when I responded but the thing that made me put my money on kclient is in `Server::handle_client_readdir`, there is this block https://urldefense.com/v3/__https://github.com/ceph/ceph/blob/squid/src/mds… . Meaning say if the trim_dentry() didn't clear the `CDir::STATE_COMPLETE` state then the readdir should've also served from memory and omit GSK, no? IMO if this is easily reproducible, we should get the MDS logs to verify the exact sequence. WDYT? >> >> >> On Wed, Jul 22, 2026 at 12:38 PM Xiubo Li <xiubo.li(a)clyso.com> wrote: >>> Hi Andras, Dhairya, >>> >>> I recall hitting a similar issue with this and the workaround involves >>> running the 'ls' command, but I can't recall exactly which command or >>> the tracker reference. This happened years ago. >>> >>> This morning I tried to reproduce this locally but failed. And I just >>> went through the mds and kclient code just found two suspect places >>> could cause this: >>> >>> MDS side: in https://urldefense.com/v3/__https://github.com/ceph/ceph/blob/main/src/mds/… >>> >>> MDCache::path_traverse() uses two shortcuts to conclude a dentry doesn't exist: >>> >>> if (curdir->is_complete() || // (1) >>> (snapid == CEPH_NOSNAP && ...bloom...)) { // (2) >>> return -ENOENT; >>> >>> is_complete() means all live entries are cached in memory. Shortcut >>> (2) correctly only applies to live lookups (snapid == CEPH_NOSNAP), >>> but shortcut (1) applies to all snapids — including snapshots. >>> >>> When a snapshot exists but the file was later deleted from the live >>> tree, the MDS eventually evicts the deleted file's dentry from the >>> in-memory cache (a null dentry, which trim_dentry() removes without >>> clearing the COMPLETE flag). A subsequent snapshot LOOKUP hits >>> is_complete()=true with the dentry absent (ENOENT), without ever >>> checking the OSD where the snapshot data actually lives. >>> >>> READDIR takes a different code path that fetches from the OSD, which >>> is why ls -l fixes it. >>> >>> Fix: move snapid == CEPH_NOSNAP to guard both shortcuts: >>> if (snapid == CEPH_NOSNAP && >>> (curdir->is_complete() || ...bloom...)) { >>> >>> @Andras >>> >>> BTW, to verify the above could you try to reproduce this by using the >>> ceph-fuse mount ? Locally I couldn't reproduce it by trying many times >>> and I am planing to add some debug code in MDS to ammulated it to >>> reproduce it later. >>> >>> ==== >>> >>> Kclient side: https://urldefense.com/v3/__https://github.com/ceph/ceph-client/blob/for-li… >>> Plus a kclient defense: ceph_d_revalidate() unconditionally trusts >>> negative dentries in snapshot directories, caching a transient ENOENT >>> forever. Change valid = 1 to valid = inode ? 1 : 0. >>> >>> I just created on trakcer to follow this: https://urldefense.com/v3/__https://tracker.ceph.com/issues/78529__;!!DSb-a… >>> >>> Thanks >>> Xiubo >>> >>> >>> >>> >>> On Wed, 22 Jul 2026 at 13:49, Dhairya Parmar via ceph-users >>> <ceph-users(a)ceph.io> wrote: >>>> Hi Andras, >>>> >>>> This sounds like the client served the lookups from its cached negative? >>>> Can you check if you see the lookup calls being made to MDS and maybe set >>>> debug_mds=20 to check if the client did send the request but it was MDS >>>> which returned ENOENT but since the `ls -l` succeeded I'm wondering if this >>>> is actually something from MDS. Maybe try a sync and drop_caches to >>>> validate that? >>>> >>>> *Dhairya Parmar* >>>> >>>> Software Engineer, CephFS >>>> >>>> >>>> On Wed, Jul 22, 2026 at 3:46 AM Andras Pataki via ceph-users < >>>> ceph-users(a)ceph.io> wrote: >>>> >>>>> Hi ceph users/devs, >>>>> >>>>> We've been encountering a strange issue with snapshots as part of a >>>>> project to copy our large ceph file system to a backup in parallel >>>>> across nodes. We are taking a snapshot, and then doing a copy of the >>>>> snapshot, which we expect to be static (unchanging) - using several >>>>> clients in parallel - all kernel mounts. Some clients are unable to >>>>> open files and directories that are known to exist (were discovered >>>>> traversing the file system on perhaps another node). >>>>> After some playing around, I could reproduce the issue on a single node >>>>> with just 'ls' as follows: >>>>> >>>>> # This file doesn't seems to exist - and some number of parent directories >>>>> are also "missing": [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W/gamess_io/gamess_qm_energy_thread0_2026_05_15_13_18_13.log >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W/gamess_io/gamess_qm_energy_thread0_2026_05_15_13_18_13.log': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W/gamess_io >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W/gamess_io': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen >>>>> >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen': >>>>> >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM >>>>> ls: cannot access >>>>> '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM': >>>>> No such file or directory [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK ls: cannot >>>>> access '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK': >>>>> No such file or directory # Until we get to this 'Projects' parent >>>>> directory, which seems to be there [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects drwxr-sr-x 45 >>>>> 1961 1961 46 Jun 8 14:02 >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects # GSK under it >>>>> is still not there ... [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK ls: cannot >>>>> access '/mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK': >>>>> No such file or directory # But ... let's see if the "tickle" the Projects >>>>> directory a bit ... >>>>> [root@cephmds603 ~]# ls -l >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects > /dev/null >>>>> >>>>> # Now all subdirectories and the file in question immediately becomes >>>>> visible: >>>>> [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK >>>>> drwxrwsr-x 5 1961 1961 3 May 7 17:18 >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK >>>>> [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM >>>>> drwxrwsr-x 12 1961 1961 10 May 11 16:08 >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM >>>>> [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen >>>>> drwxrwsr-x 5 1961 1961 3 May 11 16:18 >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen >>>>> [root@cephmds603 ~]# ls -ld >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W/gamess_io/gamess_qm_energy_thread0_2026_05_15_13_18_13.log >>>>> -rw-rw-r-- 1 1961 1961 51538071 May 15 14:10 >>>>> /mnt/ceph/users/.snap/sync-20260701-0904/bturzo/Projects/GSK/RosettaQM/af3_ensemble_gen/output/ddg_analysis/mutation_total_scores/C_32_S_to_W/gamess_io/gamess_qm_energy_thread0_2026_05_15_13_18_13.log >>>>> >>>>> # This is the kernel client 6.18.32 (relatively recent LTS kernel) with >>>>> ceph squid 19.2.3: >>>>> [root@cephmds603 ~]# uname -a >>>>> Linux cephmds603 6.18.32.1.fi #4 SMP Mon May 18 11:45:58 EDT 2026 x86_64 >>>>> x86_64 x86_64 GNU/Linux >>>>> [root@cephmds603 ~]# ceph --version >>>>> ceph version 19.2.3 (c92aebb279828e9c3c1f5d24613efca272649e62) squid >>>>> (stable) >>>>> [root@cephmds603 ~]# >>>>> >>>>> What is most interesting is that in the live tree (non-snapshotted tree) - >>>>> the Projects directory exists, but everything under it has been removed! >>>>> >>>>> [root@cephmds600 ~]# ls -ld /mnt/ceph/users/bturzo/Projects/ >>>>> drwxr-sr-x 43 1961 1961 45 Jul 17 11:56 /mnt/ceph/users/bturzo/Projects/ >>>>> [root@cephmds600 ~]# ls -ld /mnt/ceph/users/bturzo/Projects/GSK >>>>> ls: cannot access '/mnt/ceph/users/bturzo/Projects/GSK': No such file or >>>>> directory >>>>> >>>>> Am I running into some known issue? This looks to be specific to some >>>>> clients - i.e. some clients see the directory and some don't at the same >>>>> point in time, i.e. this is perhaps a kclient problem? >>>>> Any ideas/suggestions would be appreciated, >>>>> >>>>> Andras >>>>> _______________________________________________ >>>>> ceph-users mailing list -- ceph-users(a)ceph.io >>>>> To unsubscribe send an email to ceph-users-leave(a)ceph.io >>>>> >>>>> >>>> _______________________________________________ >>>> ceph-users mailing list -- ceph-users(a)ceph.io >>>> To unsubscribe send an email to ceph-users-leave(a)ceph.io > _______________________________________________ > ceph-users mailing list -- ceph-users(a)ceph.io > To unsubscribe send an email to ceph-users-leave(a)ceph.io

1 0

Re: v21.1.0 Umbrella RC0 released
by Stefan Möding 22 Jul '26

22 Jul '26

Patrick Donnelly via ceph-users <ceph-users(a)ceph.io> writes: > Why is Canonical not updating/fixing these packages when the standard > EOL for 24.04 is May 2029? The Qt5 packages are part of the Universe repo. This is not covered by the standard (viz. free) 5 year. LTS covers only the Main repo. It requires an ESM contract to get support for the Universe repo. So with the release of Ubuntu 26.04 the ongoing effort to keep the Universe repo up to date has effectively been dropped. -- Stefan

1 0