Menu
▾
▴
Re: [robinhood-support] Help understanding running the changelog reader
|
From: <Yoa...@ce...> - 2026-01-28 10:31:05
|
Hello, No there shouldn't be any issue performing requests while the scan or update is occuring. Your issue seems to be at the system-level indeed, files with a modification time in 2186 is strange. Maybe you fiddled with the system's time? Otherwise I'd say it's a Lustre issue, most likely corrupt metadata for times in the future. For times in the past like 2007, maybe you copied the entries from another system which was up at the time, and duplicated the metadata at the same time? If not, then most likely corrupt metadata aswell. Kind regards, Yoann Valeri. ________________________________ De : Angel de Vicente <ang...@ia...> Envoyé : mardi 27 janvier 2026 21:16:43 À : VALERI Yoann 610657 Cc : rob...@li... Objet : Re: [robinhood-support] Help understanding running the changelog reader Hello, "Yoa...@ce..." <Yoa...@ce...> writes: > What you're saying is making sense, but the issue comes from the > changelog reader's usage. Perfect. Thanks for the detailed explanation. It all makes sense now. Since my previous mail, I've been experimenting a bit, and changed the server where I install Robinhood, so now the database is stored in a SSD and I use MariaDB (as opposed to HDD + MySQL in the previous attempt). I'm performing now the initial scan and I can see that it is going faster, but I assume the real test will be later, trying to measure the speed of queries. In any case, I'm about to start playing with policies. Basically I want to be able to keep our system below 90%, by deleting old files when we reach that threshold, and later on I'll probably have some questions about that, but now I've some strange result from trying to check some details of some files. I tried the "rbh-report --oldest-files", but to my surprise it reported files accessed in 2007 (we didn't have that system yet). I tried then with the "--reverse" option and I got results which access times in 2050! If I check the stats for one of those files you see that Robinhood reports access and modification times in 2050, while "stat" reports pretty crazy stuff for the modify time. Since the policy that I want to implement would take into account last access time this is not ideal. Does this mean that my Lustre file system is corrupt in some way? (I was performing queries while the initial scan was being performed. Is that safe or did I go into dangerous territory?) Any pointers on how to debug/avoid these wrong data? Robinhood stats =============== $ sudo /scratch/angelv-adm/robinhood/robin/sbin/rbh-report -f /etc/robinhood.d/basto.conf -e /storage/WIPEOUT_JAN31/BACKED_UP/martinlc/backup_portatil/home/martinlc/.cache/mesa_shader_cache/70/cd1e3cd724a4085d417bcda03b5be4e8417f41 id : [0x20000cf4d:0x6a64:0x0] parent_id : [0x20000cf33:0x714c:0x0] name : cd1e3cd724a4085d417bcda03b5be4e8417f41 path updt : 2026/01/26 16:24:40 path : /storage/WIPEOUT_JAN31/BACKED_UP/martinlc/backup_portatil/home/martinlc/.cache/mesa_shader_cache/70/cd1e3cd724a4085d417bcda03b5be4e8417f41 depth : 9 user : martinlc group : tmgs-old projid : ? size : 1.17 KB spc_used : 4.00 KB creation : 2024/11/22 14:17:54 last_access : 2050/06/12 21:10:19 last_mod : 2050/06/12 21:10:19 last_mdchange : 2024/11/22 14:17:54 type : file mode : rw-r----- nlink : 1 md updt : 2026/01/26 16:24:40 invalid : no fileclass : small_files class updt : 2026/01/26 16:24:40 stripe_cnt, stripe_size, pool: 1, 1.00 MB, stripes : ost#21: 4375333 lhsm.status : new lhsm.archive_id: 0 lhsm.no_release: no lhsm.no_archive: no lhsm.last_archive: 0 lhsm.last_restore: 0 "Stat" stats ============ $ sudo stat /storage/WIPEOUT_JAN31/BACKED_UP/martinlc/backup_portatil/home/martinlc/.cache/mesa_shader_cache/70/cd1e3cd724a4085d417bcda03b5be4e8417f41 File: /storage/WIPEOUT_JAN31/BACKED_UP/martinlc/backup_portatil/home/martinlc/.cache/mesa_shader_cache/70/cd1e3cd724a4085d417bcda03b5be4e8417f41 Size: 1203 Blocks: 8 IO Block: 4194304 regular file Device: f96638d6h/4184226006d Inode: 144116078425959012 Links: 1 Access: (0640/-rw-r-----) Uid: ( 1518/martinlc) Gid: ( 60/tmgs-old) Access: 2025-12-16 16:06:14.000000000 +0000 Modify: 2186-07-20 03:38:35.000000000 +0100 Change: 2024-11-22 14:17:54.000000000 +0000 Birth: - Many thanks, -- Ángel de Vicente Research Software Engineer (Supercomputing and BigData) Tel.: +34 922-605-747 --------------------------------------------------------------------------------------------- AVISO LEGAL: Este mensaje puede contener información confidencial y/o privilegiada. Si usted no es el destinatario final del mismo o lo ha recibido por error, por favor notifíquelo al remitente inmediatamente. Cualquier uso no autorizadas del contenido de este mensaje está estrictamente prohibida. Más información en: https://www.iac.es/es/responsabilidad-legal DISCLAIMER: This message may contain confidential and / or privileged information. If you are not the final recipient or have received it in error, please notify the sender immediately. Any unauthorized use of the content of this message is strictly prohibited. More information: https://www.iac.es/en/disclaimer |
