public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias <kaminsky@finswimmer.de>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REQUEST] Option for skipping unreadable blocks on Video DVD
Date: Sun, 18 Nov 2007 23:34:52 +0100	[thread overview]
Message-ID: <200711182334.52703.kaminsky@finswimmer.de> (raw)
In-Reply-To: <473FC662.7020901@shaw.ca>

Am Sunday 18 November 2007 schrieben Sie:
> Tobias wrote:
> > If you are accessing a scratched Video DVD and the device cannot read it,
> > the process ends.
> > What about a more tolerant way to handle unreadable blocks.
> > Especially on Video DVDs single blocks are not that important than on
> > data dvds.
>
> If the DVD player process ends from this, I'd say that's the fault of
> the player software not handling errors properly.
>
> I think that if they are using the normal block layer accesses on the
> DVD device, there may be some retries that occur which are likely
> undesirable in this case since they will just stall playback. If they
> are using SG_IO to feed raw requests into the drive (which I imagine
> they need to do for CSS authentication, etc. anyway), then all error
> handling is passed up to the user application.

Normal apps like cp are ending because of Input/Output error. 
I did some researches and 
dd if=/dev/hdc of=image.iso conv=noerror,sync bs=1M 
does everything I want for whole Video Dvds. It skips unreadable blocks.
But I get recorded tv shows from friends and there is the same as with 
scratched dvds. Now the problem is that there are several .avi files on it. 
So I cannot use dd. 

> > So is there a way that the kernel tells the device to skip these bad
> > blocks?
>
> We don't know they're bad until we try and read them. 
> How long the drive will stall trying to read that sector before giving up 
>and returning an error is up to the drive. 

It would be enough that the drive does not report it as a error. If it would 
be a warning it may be skipped.

> I'm not sure if the MMC command set allows any 
> way to tell the drive to give up more quickly or not..

How can I figure this out? The best way would be a special command that all 
user apps can use which tells the drive to skip all of these bad blocks. With 
this you could turn it on if you want to watch movies where single bytes are 
not that important or turn it off if you want to have a identical copy of the 
dvd.

By the way, I am surprised that I am the only one who has problems with this.

Tobi

  reply	other threads:[~2007-11-18 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.DNZjDdh1eNcFR2zDRKzQ6G2bIVU@ifi.uio.no>
2007-11-18  4:58 ` [REQUEST] Option for skipping unreadable blocks on Video DVD Robert Hancock
2007-11-18 22:34   ` Tobias [this message]
2007-11-25 18:32     ` Pavel Machek
2007-11-17 11:29 Tobias

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=200711182334.52703.kaminsky@finswimmer.de \
    --to=kaminsky@finswimmer.de \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@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