From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: Re: editable udf metadata Date: 23 Oct 2003 10:06:26 -0600 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1066925185.11813.21.camel@patehci2> References: <1065553341.8172.45.camel@patehci2> <20031007204951.A25423@falcon.csc.calpoly.edu> <1065631289.6625.34.camel@patehci2> <1065631668.6625.48.camel@patehci2> <1065635511.7602.38.camel@patehci2> <1066773266.2888.83.camel@patehci2> <1066778250.2888.129.camel@patehci2> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:732 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S263602AbTJWQGm (ORCPT ); Thu, 23 Oct 2003 12:06:42 -0400 Received: from royntex01.iomegacorp.com (unknown [147.178.90.120]) by email.iomega.com (Postfix) with ESMTP id 04E231E60 for ; Thu, 23 Oct 2003 10:06:42 -0600 (MDT) To: linux-fsdevel@vger.kernel.org In-Reply-To: <1066778250.2888.129.camel@patehci2> List-Id: linux-fsdevel.vger.kernel.org > 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" $