From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: editable udf metadata
Date: 23 Oct 2003 10:06:26 -0600 [thread overview]
Message-ID: <1066925185.11813.21.camel@patehci2> (raw)
In-Reply-To: <1066778250.2888.129.camel@patehci2>
> We mean to say udfct in Linux needs no SCSI pass thru, right?
> We mean to say udfct only needs a raw block device?
> Mac OS X has those too, so Mac OS X could work if we volunteer a patch?
No explicit answers yet.
But here now in summary we do have four UDF FAQ's answered, per request
kindly received offline:
/// Contents
1: Where on the web does the fsck for linux udf.ko appear?
2: Why does an erased disk fail udf fsck?
3: Where on the web does an already `make`able udf fsck appear?
4: Why doesn't udfct_1_0r2/ understand `./configure ; make`?
/// 1: Where on the web does the fsck for linux udf.ko appear?
As the udffsck/ of:
$ export CVSROOT=:pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-udf
$ cvs login
(Logging in to anonymous@cvs.sourceforge.net)
CVS password:
$ cvs co udftools
...
/// 2: Why does an erased disk fail udf fsck?
It doesn't, if you erased your disk correctly.
The one "error:|warning:|note:" you can expect is "EFE 28 icbtag
error: parentICBLocation: (10,0)," if you erased your disk via the
mkudffs/mkudffs of 2002 Feb 9 1.0.0b2 udftools freely offered as the
"latest file release" of:
http://sourceforge.net/projects/linux-udf/
If you want no "error:|warning:|note:", then instead you can try the
mkudffs/mkudffs you get via CVS.
/// 3: Where on the web does an already `make`able udf fsck appear?
We haven't yet published how to make the cvs udf fsck.
At the end of the web trail:
http://www.google.com/search?q=philips+udf+test
http://www.google.com/search?q=philips+udf+verifier&btnI=1
http://www.extra.research.philips.com/udf/
http://www.extra.research.philips.com/udf/download.html
http://www.extra.research.philips.com/udf/download/udfct_1_0r2.tar.gz
The src/udf_tester/udf_test you make is the "Philips UDF Verifier" of
Gerrit Scholls et al.
/// 4: Why doesn't udfct_1_0r2/ understand `./configure ; make`?
I have no idea. But a tty log of what worked for me follows:
$ cd udfct_1.0r2
$ less FAQ.txt
$ cd src/udf_tester
$ make
...
$
$ ./udf_test /dev/sg0
UDF Conformance Testing Application
(c) Koninklijke Philips Electronics N.V. 1999-2003
Application version: 1.0r2
UCT Core version : 1.0r2
...
No image configuration file /dev/sg0.cfg
Error: Image file chunk byte size: 0,
- expected: not zero, at most (1048575 * 2048), and
- an integral multiple of the block size (2048).
- for: /dev/sg0
Cannot create image device
...
fatal error: Exit code 2, quit.
...
$
$ ./udf_test -show-scsi
...
Unknown, misplaced or unused command line arguments:
-show-scsi
fatal error: Exit code 2, quit.
...
$
$ sudo dd of=/dev/scd0 bs=2K count=1 if=/dev/zero
1+0 records in
1+0 records out
$
$ mkudffs /dev/scd0
trying to change type of multiple extents
$
$ sudo mkudffs /dev/scd0
start=0, blocks=16, type=RESERVED
...
start=524287, blocks=1, type=ANCHOR
$
$ sudo udf_test /dev/scd0 >1
$ sudo udf_test /dev/scd0 >2
$ diff 1 2
50c50
< Start time : 2003-10-21 17:14:31 -06:00 (west of UTC)
---
> Start time : 2003-10-21 17:14:33 -06:00 (west of UTC)
$
$ grep -i 'note:' 1 | wc -l
0
$ grep -i 'warning:' 1 | wc -l
0
$ grep -i 'error:' 1 | wc -l
1
$
$ grep -i -A 6 'error:' 1
EFE 28 icbtag error: parentICBLocation: (34,0),
- recommended: (0,0) for strategy type 4.
- Icbtag Parent ICB Location shall not point to itself
- or to a higher parent in the directory hierarchy.
- ECMA 3rd edition 4/8.10.1, 4/14.6.7, UDF 2.3.5.3.
- icbtag: ECMA 4/14.6.*, 4/A.5, UDF 2.3.5.*, 6.6
- name: "lost+found"
$
next prev parent reply other threads:[~2003-10-23 16:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 19:02 zeroes read back more often than appended Pat LaVarre
2003-10-07 20:54 ` Pat LaVarre
2003-10-08 3:49 ` Ben Fennema
2003-10-08 16:41 ` Pat LaVarre
2003-10-08 16:47 ` editable udf metadata Pat LaVarre
2003-10-08 17:51 ` Pat LaVarre
2003-10-08 18:09 ` big-endian udfct_1_0r2 Pat LaVarre
2003-10-08 18:30 ` Matthew Wilcox
[not found] ` <3F8472FE.9040403@lougher.demon.co.uk>
2003-10-08 19:49 ` Matthew Wilcox
2003-10-08 20:43 ` Phillip Lougher
2003-10-21 21:54 ` editable udf metadata Pat LaVarre
2003-10-21 23:17 ` Pat LaVarre
2003-10-23 16:06 ` Pat LaVarre [this message]
2003-10-24 21:40 ` Pat LaVarre
2003-10-22 8:15 ` same page access Mark B
2003-10-22 11:21 ` Matthew Wilcox
2003-10-22 17:09 ` Mark B
2003-10-22 17:10 ` Matthew Wilcox
2003-10-08 17:02 ` zeroes read back more often than appended Pat LaVarre
2003-10-08 17:06 ` toggling smp clears x86_mce_p4thermal of make xconfig Pat LaVarre
2003-10-08 17:21 ` zeroes read back more often than appended Pat LaVarre
2003-10-08 16:46 ` soft trace of read/write of drivers/block/loop.c Pat LaVarre
2003-10-08 20:32 ` zeroes read back more often than appended Pat LaVarre
2003-10-09 20:54 ` Pat LaVarre
2003-10-10 0:52 ` Pat LaVarre
2003-10-10 16:39 ` Pat LaVarre
2003-10-10 18:15 ` Pat LaVarre
2003-10-14 0:38 ` Pat LaVarre
2003-10-14 1:48 ` Pat LaVarre
2003-10-20 23:20 ` Pat LaVarre
2003-10-21 14:47 ` Pat LaVarre
2003-10-21 16:46 ` Pat LaVarre
2003-10-21 18:44 ` Pat LaVarre
2003-10-23 18:52 ` Pat LaVarre
2003-10-27 21:55 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 15:58 editable udf metadata Pat LaVarre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1066925185.11813.21.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox