SeqBox - Revision history

Parchivist at 20:48, 4 November 2023

2023-11-04T20:48:23Z

Parchivist at 20:20, 4 November 2023

2023-11-04T20:20:23Z

Mark0 at 00:50, 22 August 2023

2023-08-22T00:50:06Z

Parchivist at 20:04, 21 August 2023

2023-08-21T20:04:01Z

Jsummers at 17:08, 23 March 2017

2017-03-23T17:08:23Z

Mark0 at 14:51, 16 March 2017

2017-03-16T14:51:56Z

Mark0 at 14:51, 16 March 2017

2017-03-16T14:51:15Z

Mark0 at 14:50, 16 March 2017

2017-03-16T14:50:22Z

Mark0: First draft of the page

2017-03-16T14:35:32Z

First draft of the page

New page

{{FormatInfo
| extensions = {{ext|sbx}}, {{ext|seqbox}}
| released = 2017
| image = sbx.png
| caption = SeqBox - Sequenced Box container
| endianness = Big_endian
| developed by = Marco Pontello
| reference impl = http://mark0.net/soft-seqbox-e.html
| error resiliance = {{CRC}}, {{SHA-2}}
| subcat = Archiving
}}

[[SeqBox]] is a single file container/archive that can be reconstructed even after total loss of file system structures.

An [[SBX]] container is composed of a collections of blocks with size sub/equal to that of a sector, so they can survive any level of fragmentation. Each block have a minimal header that include a unique file identifier, block sequence number, checksum, version. Additional, non critical info/metadata are contained in block 0 (like name, file size, crypto-hash, other attributes, etc.).

If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then CRCs to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number and reassembled to form the original SeqBox containers.

== Identification ==

A SeqBox files start with bytes <code>53 42 78</code> or "SBx" in [[ASCII]].

== Format description ==

* [https://github.com/MarcoPon/SeqBox SeqBox] GitHub repository

== Links ==

* [http://mark0.net/soft-seqbox-e.html SeqBox], Marco Pontello's Home Page

@@ Line 25: / Line 25: @@
 Adds < 3.5% to file size.
@@ Line 38: / Line 41: @@
 * [http://mark0.net/soft-seqbox-e.html SeqBox], Marco Pontello's Home Page
-* [https://github.com/darrenldl/ocaml-SeqBox OCaml implementation of SeqBox by darrenldl (Darren Li)]
+* [https://github.com/darrenldl/ocaml-SeqBox osbx] - OCaml implementation of SeqBox by darrenldl (Darren Li)

← Older revision		Revision as of 20:20, 4 November 2023
Line 38:		Line 38:

	* [http://mark0.net/soft-seqbox-e.html SeqBox], Marco Pontello's Home Page		* [http://mark0.net/soft-seqbox-e.html SeqBox], Marco Pontello's Home Page
		+	* [https://github.com/darrenldl/ocaml-SeqBox OCaml implementation of SeqBox by darrenldl (Darren Li)]

@@ Line 16: / Line 16: @@
 If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then [[CRC]]s to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number, and reassembled to form the original SeqBox containers.
-Does not work on encrypted filesystems or filesystems that don't have a 512-byte block size.
+Does not work on encrypted filesystems or filesystems that don't have a multiple of 128-byte block size.
 Striping/RAID instead is usually not a problem.

← Older revision		Revision as of 20:04, 21 August 2023
Line 15:		Line 15:

	If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then [[CRC]]s to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number, and reassembled to form the original SeqBox containers.		If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then [[CRC]]s to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number, and reassembled to form the original SeqBox containers.
		+
		+	Does not work on encrypted filesystems or filesystems that don't have a 512-byte block size.
		+
		+	Striping/RAID instead is usually not a problem.
		+
		+	With password set, can be used for steganography (attach to another file and it won't be recognizable unless password is provided).
		+
		+	If multiple copies are stored, can automatically pull together all the good segments.
		+
		+	Adds < 3.5% to file size.
		+

	== Identification ==		== Identification ==

@@ Line 10: / Line 10: @@
 | subcat                 = Archiving
 }}
-[[SeqBox]] is a single file container/archive that can be reconstructed even after total loss of file system structures.
+An SBX container is composed of a collection of blocks with size sub/equal to that of a sector, so they can survive any level of fragmentation. Each block has a minimal header that includes a unique file identifier, block sequence number, checksum, version. Additional non critical info/[[metadata]] are contained in block 0 (like name, file size, crypto-hash, other attributes, etc.).
-An [[SBX]] container is composed of a collections of blocks with size sub/equal to that of a sector, so they can survive any level of fragmentation. Each block have a minimal header that include a unique file identifier, block sequence number, checksum, version. Additional, non critical info/[[metadata]] are contained in block 0 (like name, file size, crypto-hash, other attributes, etc.).
+If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then [[CRC]]s to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number, and reassembled to form the original SeqBox containers.
-−
-If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then [[CRC]]s to detect valid [[SBX]] blocks. Then the blocks can be grouped by UIDs, sorted by sequence number and reassembled to form the original SeqBox containers.
 == Identification ==
-A SeqBox files start with bytes <code>53 42 78</code> or "SBx" in [[ASCII]].
+A SeqBox files start with bytes {{magic|53 42 78}}, or "{{magic|SBx}}" in [[ASCII]].
 == Format description ==

@@ Line 15: / Line 15: @@
 An [[SBX]] container is composed of a collections of blocks with size sub/equal to that of a sector, so they can survive any level of fragmentation. Each block have a minimal header that include a unique file identifier, block sequence number, checksum, version. Additional, non critical info/[[metadata]] are contained in block 0 (like name, file size, crypto-hash, other attributes, etc.).
-If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then CRCs to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number and reassembled to form the original SeqBox containers.
+If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then [[CRC]]s to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number and reassembled to form the original SeqBox containers.
 == Identification ==