Project

General

Profile

Actions

Bug #68954

closed

cephfs-journal-tool: check the headers in dump file after journal recovery

Added by Jos Collin over 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Administration/Usability
Target version:
% Done:

0%

Source:
Community (dev)
Backport:
reef,squid
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
tools
Labels (FS):
Pull request ID:
Tags (freeform):
backport_processed
Fixed In:
v20.0.0-1628-gbbed733090
Released In:
v20.2.0~523
Upkeep Timestamp:
2025-11-01T01:27:54+00:00

Description

Check the headers in dump file after journal recovery. Otherwise, importing a file with Invalid Header, would lead to 'Journal not readable'.

$  ./bin/cephfs-journal-tool --rank a:0 journal export ./file1 
journal is 4194304~940
wrote 940 bytes at offset 4194304 to ./file1
NOTE: this is a _sparse_ file; you can
    $ tar cSzf ./file1.tgz ./file1
      to efficiently compress it while preserving sparseness.

# Edit file1 to have an invalid header.

$ ./bin/cephfs-journal-tool --rank a:0  journal import file1
undump file1
start 4194304 len 940 write_pos 4194304 format 1 trimmed_pos 4194304 stripe_unit 4194304 stripe_count 1 object_size 4194304
writing header 200.00000000
Purging 2 objects from 1
 writing 4194304~940
2024-11-14T10:49:58.964+0530 7f13452c9300 -1 Failed to write header: (22) Invalid argument
Error ((22) Invalid argument)

$ rm file1

$  ./bin/cephfs-journal-tool --rank a:0 journal export ./file1 
2024-11-14T10:50:42.591+0530 7f9e60adf300 -1 Missing object 200.00000001
Error ((5) Input/output error)
2024-11-14T10:50:42.592+0530 7f9e60adf300 -1 journal_export: Journal not readable, attempt object-by-object dump with `rados`

$  ./bin/cephfs-journal-tool --rank a:0 journal export ./file1 
2024-11-14T10:50:42.591+0530 7f9e60adf300 -1 Missing object 200.00000001
Error ((5) Input/output error)
2024-11-14T10:50:42.592+0530 7f9e60adf300 -1 journal_export: Journal not readable, attempt object-by-object dump with `rados`


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #71036: reef: cephfs-journal-tool: check the headers in dump file after journal recoveryResolvedJos CollinActions
Copied to CephFS - Backport #71037: squid: cephfs-journal-tool: check the headers in dump file after journal recoveryResolvedJos CollinActions
Actions #1

Updated by Jos Collin over 1 year ago

  • Project changed from Ceph to CephFS
  • Category set to Administration/Usability
  • Source set to Community (dev)
Actions #2

Updated by Jos Collin over 1 year ago

  • Status changed from New to In Progress
  • Pull request ID set to 60731
Actions #3

Updated by Venky Shankar over 1 year ago

  • Status changed from In Progress to Fix Under Review
  • Assignee set to Jos Collin
  • Target version set to v20.0.0
  • Backport set to quincy,reef,squid
  • Component(FS) tools added
Actions #4

Updated by Konstantin Shalygin about 1 year ago

  • Backport changed from quincy,reef,squid to reef,squid
Actions #5

Updated by Rishabh Dave 11 months ago

  • Status changed from Fix Under Review to Pending Backport
Actions #6

Updated by Upkeep Bot 11 months ago

  • Copied to Backport #71036: reef: cephfs-journal-tool: check the headers in dump file after journal recovery added
Actions #7

Updated by Upkeep Bot 11 months ago

  • Copied to Backport #71037: squid: cephfs-journal-tool: check the headers in dump file after journal recovery added
Actions #8

Updated by Upkeep Bot 11 months ago

  • Tags (freeform) set to backport_processed
Actions #9

Updated by Upkeep Bot 8 months ago

  • Merge Commit set to bbed733090899ea97435ea3c4403d152af7454dd
  • Fixed In set to v20.0.0-1628-gbbed7330908
  • Upkeep Timestamp set to 2025-07-08T18:34:05+00:00
Actions #10

Updated by Jos Collin 8 months ago

  • Status changed from Pending Backport to Resolved
Actions #11

Updated by Upkeep Bot 8 months ago

  • Fixed In changed from v20.0.0-1628-gbbed7330908 to v20.0.0-1628-gbbed733090
  • Upkeep Timestamp changed from 2025-07-08T18:34:05+00:00 to 2025-07-14T17:10:37+00:00
Actions #12

Updated by Upkeep Bot 5 months ago

  • Released In set to v20.2.0~523
  • Upkeep Timestamp changed from 2025-07-14T17:10:37+00:00 to 2025-11-01T01:27:54+00:00
Actions

Also available in: Atom PDF