blobs: fix outdated comment about file format
the wrong info here was rather misleading, especially when encountering errors just talking about "blobs" when the actual problem is with a chunk. chunks did originally have their own magic values, but that got removed in 4ee8f53d07bf0becf19a22cf4f4674558a4d128c "remove DataChunk file format - use DataBlob instead" back in 2019, before the 0.1.1 release(!) Reported-by: Dominik Csapak <d.csapak@proxmox.com> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
This commit is contained in:
parent
66215b38f8
commit
61167351a1
@ -35,8 +35,8 @@ pub const DYNAMIC_SIZED_CHUNK_INDEX_1_0: [u8; 8] = [28, 145, 78, 165, 25, 186, 1
|
|||||||
///
|
///
|
||||||
/// (MAGIC || CRC32 || Data)
|
/// (MAGIC || CRC32 || Data)
|
||||||
///
|
///
|
||||||
/// This is basically the same format we use for chunks, but
|
/// This format is used for blobs (stored in a BackupDir and accessed directly) and chunks (stored
|
||||||
/// with other magic numbers so that we can distinguish them.
|
/// in a chunk store and accessed via a ChunkReader / index file).
|
||||||
#[derive(Endian)]
|
#[derive(Endian)]
|
||||||
#[repr(C, packed)]
|
#[repr(C, packed)]
|
||||||
pub struct DataBlobHeader {
|
pub struct DataBlobHeader {
|
||||||
|
Loading…
x
Reference in New Issue
Block a user