bug-xorriso
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "Calculated and written ECMA-119 tree end differ" under very specifi


From: Valtteri Vuorikoski
Subject: Re: "Calculated and written ECMA-119 tree end differ" under very specific circumstances
Date: Sun, 31 Jan 2021 13:06:54 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1.90 (gnu/linux)

Hi. I need to leave soon for today, but I'll try to test 1.5.4 in the
evening or tomorrow. Meanwhile answers to the easier questions below.

"Thomas Schmitt" <scdbackup@gmx.net> writes:

> Ouch again. I haven't used NFS since a decade. I will have to learn again
> how to set it up.
>
> (As a side note i wonder whether zisofs can compress any gain out of MPEG.)

More precisely, this is NFS 4.2 which supports ACLs and possibly even user
xattrs, unlike v3 and older versions. The backup content is very mixed
and the MPEGs are a small part of it.

> What do you get if you replace the final -commit command by
>
>   -find / -has_xattr -exec get_any_xattr -- -rollback
>
> This should list the files which will get AAIP records attached for
> hardlink detection. Like
>   ...
>   # file: n
>   isofs.di="\002\010\003\0036\020\214"
>   ...
>
> "isofs.di" records device and inode number of the file in the original
> filesystem.

Output starts with:

# file: a
isofs.di="\001L\003\005\336\272"

# file: a/05000100
system.nfs4_acl="\000\000\000\003\000\000\000\000\000\000\000\000\000\026\001\207\000\000\000\006OWNER@\000\000\000\000\000\000\000\000\000\000\000\022\000\201\000\000\000\006GROUP@\000\000\000\000\000\000\000\000\000\000\000\022\000\201\000\000\000\011EVERYONE@\000\000\000"
isofs.di="\001L\003\005\336\273"

# file: a/05000200
system.nfs4_acl="\000\000\000\003\000\000\000\000\000\000\000\000\000\026\001\207\000\000\000\006OWNER@\000\000\000\000\000\000\000\000\000\000\000\022\000\201\000\000\000\006GROUP@\000\000\000\000\000\000\000\000\000\000\000\022\000\201\000\000\000\011EVERYONE@\000\000\000"
isofs.di="\001L\003\005\336\274"

So looks like the NFS client causes all files to get an ACL-related
system xattr. I was looking only for user xattrs before and missed these before.

> Most AAIP info gets attached only when the ISO is written.
> Is the written ISO loadable by xorriso and if so, does it tell something
> about the files when you do:
>
>   xorriso -xattr any -indev foo3.iso -find / -has_xattr -exec get_any_xattr --

Looks like it can't tell anything, it only prints "Media summary: 0
sessions, 0 data blocks, 0 data, 69.4g free".

>> I can provide the produced .iso file if needed.
>
> This might be of help. Send it directly to  scdbackup@gmx.net .
>
> It would be nice if it was smaller than 119 MB.
> Do you need all 101 files to reproduce the failure ?
> Do the files have to be large MPEGs (or do small dummy files suffice) ?

I'll send you the start of the file as discussed in your next mail
next and test with dummy files later.

 -Valtteri

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]