Output of fs extract is not clear about its actions on identified filesystems #689

New Issue

claunia · 2026-01-29T15:26:34Z

claunia commented

2026-01-29 15:26:34 +00:00

Originally created by @robin-francois on GitHub (Mar 3, 2021).

Check and fill as appropriate:

Support for a new media image format...
Support for identifying a new filesystem...
Support for extracting files from a new filesystem...
New command...
Improvement to output...
Other...

Detailed Description

The output of the fs extract function is not explicit about what actions have been performed or not if the filesystem is identified. The following output shows that while the first partition has not been processed since the filesystem is not identified, the situation for the second partition (partition 1) is unclear:

Is the partition empty?
Is the filesystem not supported for file extraction?
Is the extraction failing for some other reason?

# aaru -v fs extract test-extract
aaru 5.2.0.3330
Copyright © 2011-2020 Natalia Portillo

Image format identified by Aaru Format (49360069-1784-4a2f-b723-0c844d610b0a).
2 partitions found.

Partition 0:
Identifying filesystem on partition
Filesystem not identified

Partition 1:
Identifying filesystem on partition

Through the use of i analyze (see below), we can see that partition 1 has a HFS filesystem that is not supported for file extraction. However, at no point does Aaru indicates that HFS is not supported for file extraction. Aaru's output should be adapted to explicit the situation.

Context

Aaru adoption is growing and new users will need to have explicit feedback on what the tool is doing or not doing since it cannot be expected from them to know in details the capabilities of the tool. Automation and bash use of aaru should also be in mind when designing the output of the tool.

Known documentation

Attached, output of i analyze for the image used as file extraction example.

# aaru i analyze test-extract
Copyright © 2011-2020 Natalia Portillo

Image format identified by Aaru Format.

2 partitions found.

Partition 0:
Partition name: Track 1
Partition type: CdMode1
Partition start: sector 0, byte 0
Partition length: 97157 sectors, 0 bytes
Partition scheme: Optical disc track
Partition description:

Identifying filesystem on partition
Filesystem not identified

Partition 1:
Partition name: Toast 3.5.4 PPC HFS Builder
Partition type: Apple_HFS
Partition start: sector 9, byte 18944
Partition length: 96995 sectors, 198646272 bytes
Partition scheme: Apple Partition Map
Partition description:
Partition flags:
Partition is valid.
Partition entry is allocated.
Partition is readable.

Identifying filesystem on partition
Identified by Apple Hierarchical File System.
Apple Hierarchical File System

HFS uses 512 bytes/sector while device uses 2048 bytes/sector.

Master Directory Block:
Creation date: 11/2/2000 12:36:02 PM
Last modification date: 11/2/2000 12:36:02 PM
Volume has never been backed up
Volume was unmonted.
4 files on root directory
0 directories on root directory
4 files on volume
0 directories on volume
Volume write count: 1000
Volume bitmap starting sector (in 512-bytes): 3
Next allocation block: 1.
16165 volume allocation blocks.
12288 bytes per allocation block.
12288 bytes to allocate when extending a file.
12288 bytes to allocate when extending a Extents B-Tree.
12288 bytes to allocate when extending a Catalog B-Tree.
Sector of first allocation block: 19
Next unused CNID: 22
0 unused allocation blocks.
65536 bytes in the Extents B-Tree
0 bytes in the Catalog B-Tree
Volume name: Guy
Finder info:
CNID of bootable system's directory: 0
CNID of first-run application's directory: 0
CNID of previously opened directory: 0
CNID of bootable Mac OS 8 or 9 directory: 0
CNID of bootable Mac OS X directory: 0
0 blocks in volume cache
12288 blocks in volume bitmap cache
0 blocks in volume common cache
Volume is not bootable.

Originally created by @robin-francois on GitHub (Mar 3, 2021).  ### Check and fill as appropriate: * [ ] Support for a new media image format... * [ ] Support for identifying a new filesystem... * [ ] Support for extracting files from a new filesystem... * [ ] New command... * [x] Improvement to output... * [ ] Other... ## Detailed Description  The output of the `fs extract` function is not explicit about what actions have been performed or not if the filesystem is identified. The following output shows that while the first partition has not been processed since the filesystem is not identified, the situation for the second partition (partition 1) is unclear: - Is the partition empty? - Is the filesystem not supported for file extraction? - Is the extraction failing for some other reason? ``` # aaru -v fs extract test-extract aaru 5.2.0.3330 Copyright © 2011-2020 Natalia Portillo Image format identified by Aaru Format (49360069-1784-4a2f-b723-0c844d610b0a). 2 partitions found. Partition 0: Identifying filesystem on partition Filesystem not identified Partition 1: Identifying filesystem on partition ``` Through the use of `i analyze` (see below), we can see that partition 1 has a HFS filesystem that is not supported for file extraction. However, at no point does Aaru indicates that HFS is not supported for file extraction. Aaru's output should be adapted to explicit the situation. ## Context   Aaru adoption is growing and new users will need to have explicit feedback on what the tool is doing or not doing since it cannot be expected from them to know in details the capabilities of the tool. Automation and bash use of aaru should also be in mind when designing the output of the tool. ## Known documentation  Attached, output of `i analyze` for the image used as file extraction example. ``` # aaru i analyze test-extract Copyright © 2011-2020 Natalia Portillo Image format identified by Aaru Format. 2 partitions found. Partition 0: Partition name: Track 1 Partition type: CdMode1 Partition start: sector 0, byte 0 Partition length: 97157 sectors, 0 bytes Partition scheme: Optical disc track Partition description: Identifying filesystem on partition Filesystem not identified Partition 1: Partition name: Toast 3.5.4 PPC HFS Builder Partition type: Apple_HFS Partition start: sector 9, byte 18944 Partition length: 96995 sectors, 198646272 bytes Partition scheme: Apple Partition Map Partition description: Partition flags: Partition is valid. Partition entry is allocated. Partition is readable. Identifying filesystem on partition Identified by Apple Hierarchical File System. Apple Hierarchical File System HFS uses 512 bytes/sector while device uses 2048 bytes/sector. Master Directory Block: Creation date: 11/2/2000 12:36:02 PM Last modification date: 11/2/2000 12:36:02 PM Volume has never been backed up Volume was unmonted. 4 files on root directory 0 directories on root directory 4 files on volume 0 directories on volume Volume write count: 1000 Volume bitmap starting sector (in 512-bytes): 3 Next allocation block: 1. 16165 volume allocation blocks. 12288 bytes per allocation block. 12288 bytes to allocate when extending a file. 12288 bytes to allocate when extending a Extents B-Tree. 12288 bytes to allocate when extending a Catalog B-Tree. Sector of first allocation block: 19 Next unused CNID: 22 0 unused allocation blocks. 65536 bytes in the Extents B-Tree 0 bytes in the Catalog B-Tree Volume name: Guy Finder info: CNID of bootable system's directory: 0 CNID of first-run application's directory: 0 CNID of previously opened directory: 0 CNID of bootable Mac OS 8 or 9 directory: 0 CNID of bootable Mac OS X directory: 0 0 blocks in volume cache 12288 blocks in volume bitmap cache 0 blocks in volume common cache Volume is not bootable. ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#689