From: Pat LaVarre <p.lavarre@ieee.org>
To: kronos@kronoz.cjb.net
Cc: linux_udf@hpesjro.fc.hp.com, linux-kernel@vger.kernel.org
Subject: Re: Unable to read UDF fs on a DVD
Date: 23 Apr 2004 14:21:15 -0600 [thread overview]
Message-ID: <1082751675.3163.106.camel@patibmrh9> (raw)
In-Reply-To: <20040423195004.GA1885@dreamland.darkstar.lan>
> http://web.tiscali.it/kronoz/ucf_test.log
> I don't see anything strange.
I now agree, that disc passed fsck and mount well enough to make the ls
failure interesting.
What to try next after fsck passes, I do not know, ouch, sorry.
Offline I'm working to comment the fs/udf/ source. Even me finishing
that might not do you much good, unless we can figure out how to
reproduce your trouble at my desk.
Pat LaVarre
P.S. Five postscripts:
1)
> even with ide-scsi, though.
Whoa. You weren't engaging in the taboo act of running ide-scsi in 2.6
back when ls failed, were you? (If you are, then please remove
ide-scsi, substitute ide-cd, and confirm or deny that exercise actually
made no difference.)
2)
The disc didn't actually pass the phgfsck without complaint: The
standard phgfsck egrep is:
$ egrep -i '(info|warning|error):' http://web.tiscali.it/kronoz/ucf_test.log
PVD 72 Warning: Volume Set Identifier: "040420_0906",
PVD 72 Warning: Volume Set Identifier: "040420_0906",
Error: Number of AVDPs less than 2: 1, AVDP at 256
$
Non-compliance!
All the same, I'm guessing these complaints do Not explain the ls
failure, since to my newbie ear these sound like mount issues and we
know you can mount.
3)
I can't now rapidly reproduce the collection of file lengths you report,
because sparse files in UDF, even when the underlying volume is not
sparse, as yet crash my Linux-2.6.5.
3)
> Btw, don't know if it's related but I was unable to run ucf_test without
> scsi emulation: it complained about unknown image chunk size. I can't
> read files even with ide-scsi, though.
Yes phgfsck trouble like that is normal, thanks for asking.
4)
> > P.S. The subscriber-only archives of linux_udf@h... currently show
> > Linux-2.6.5 issues now under discussion, including an issue people have
> > reproduced by downloading a huge trial .exe into Windows and then
> > copying a file of more than 2 GiB to the disc.
>
> I think that this is a different issue, files on my disk are smaller.
I agree your conclusion is reasonable, I do not myself yet know the
udf.ko code well enough to firmly confirm or deny your conclusion.
5)
> http://web.tiscali.it/kronoz/ucf_test.log
Any chance this link will still work, a year from now? (I ask because
I'm hoping to see a collection of observed UDF non-compliance come into
being.)
next prev parent reply other threads:[~2004-04-23 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 16:28 Kronos
2004-04-23 17:56 ` Pat LaVarre
2004-04-23 19:50 ` Kronos
2004-04-23 20:21 ` Pat LaVarre [this message]
2004-04-24 19:47 ` Kronos
2004-04-26 15:52 ` Bill Davidsen
2004-04-26 21:48 ` Pat LaVarre
[not found] <OF7EE48D71.4DD148E6-ONC1256E82.003678FE-C1256E82.0038D7EE@phili ps.com>
[not found] ` <OF7EE48D71.4DD148E6-ONC1256E82.003678FE-C1256E82.0038D7EE@phil i ps.com>
2004-04-26 21:24 ` Pat LaVarre
[not found] <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phili ps.com>
[not found] ` <OFA36FDF30.41353846-ONC1256E83.0039A57A-C1256E83.003B5183@phil i ps.com>
2004-04-27 16:11 ` Pat LaVarre
2004-04-27 19:48 ` 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=1082751675.3163.106.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_udf@hpesjro.fc.hp.com \
/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
all inboxes | Powered by JetHome®