UDF & open integrity type

["Pali Rohár" <pali.rohar@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

Hi! After doing more experiments with UDF Integrity Type stored in UDF
Logical Volume Integrity Descriptor, it looks like for me that kernel
udf fs driver does not implement handling of open integrity correctly.

Open Integrity Type (except on VAT disk) mean that filesystem was last
time improperly unmounted, e.g. removable media was disconnected when
some write operation was in progress or when umount on Linux was not
issued.

Filesystem with Open Integrity type should be checked for error and
ideally also repaired prior next write (or maybe also read) operations.
Probably Open Integrity type can be treated on Linux as Dirty bit in FAT
filesystem.

But it looks like that kernel udf driver automatically change Open
Integrity Type to Closed when doing unmount, even when Type was Open
prior to UDF mount. For me it does not seem to be correct as kernel
itself does not implement any repair/recovery for UDF filesystem and
automatically lost any information that chkdsk/fsck should be run.

As there is planned fsck.udf, it is really important to have correct
information of successful umount command stored in filesystem itself.
This can help fsck to know last state of filesystem, like Dirty bit in
FAT or clean state of journal for ext*.

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]