[FAT filesystem] 0 should be considered as no time stored #735

New Issue

claunia · 2026-01-29T15:27:59Z

claunia commented

2026-01-29 15:27:59 +00:00

Originally created by @claunia on GitHub (Jun 1, 2021).

Prerequisites

Are you running the latest version?
Can you reproduce the problem in the debug version?

Check and fill as appropriate:

I was running Aaru under Linux 5.12.7-arch1-1...
...in 64-bit
...using an Intel / AMD processor

Description

0 time is interpreted.

Exact command line used:

Test unit.

Expected behavior:

0 time is taken as no time stored.

Actual behavior:

0 time is interpreted as 1980-01-01T00:00:00Z

Originally created by @claunia on GitHub (Jun 1, 2021). ### Prerequisites * [x] Are you running the latest version? * [x] Can you reproduce the problem in the debug version? ### Check and fill as appropriate: * [x] I was running Aaru under Linux 5.12.7-arch1-1... * [x] ...in 64-bit * [x] ...using an Intel / AMD processor ### Description 0 time is interpreted. ### Exact command line used: Test unit. ### Expected behavior: 0 time is taken as no time stored. ### Actual behavior: 0 time is interpreted as 1980-01-01T00:00:00Z

claunia added the bug filesystem beginner labels 2026-01-29 15:27:59 +00:00

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#735