mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: TheOneKEA <theonekea@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible problems reading a DVD-RAM disc
Date: Fri, 24 Aug 2007 21:06:31 -0400	[thread overview]
Message-ID: <443c85430708241806y4730bb15n9094fed2e51437f3@mail.gmail.com> (raw)
In-Reply-To: <46CF6B71.7030001@shaw.ca>

Mr. Hancock,

On 8/24/07, Robert Hancock <hancockr@shaw.ca> wrote:
> TheOneKEA wrote:
> > While doing a long mega-copy from one side of a DVD-RAM disc formatted
> > with the vfat filesystem to an smbfs network share, I got lots and
> > lots of these in the dmesg:
> >
> > Buffer I/O error on device sr0, logical block 4396
> > lost page write due to I/O error on sr0
> > sr 6:0:0:0: [sr0] Result: hostbyte=0x00 driverbyte=0x08
> > sr 6:0:0:0: [sr0] Sense Key : 0x7 [current]
> > sr 6:0:0:0: [sr0] <<vendor>> ASC=0x92 ASCQ=0x0ASC=0x92 ASCQ=0x0
> > end_request: I/O error, dev sr0, sector 17584
> > Buffer I/O error on device sr0, logical block 4396
> > lost page write due to I/O error on sr0
>
> Well, the drive is reporting an error on a write to the disc. It's not
> an error code in the MMC5 standard, though, so presumably it's a
> vendor-specific error code.

Would I be able to find a datasheet explaining the code?

>
> Not sure why it would be writing to the disc though.. Maybe if the disc
> is mounted read-write it is doing last-access-time updates or something?

It's possible - I didn't explicitly specify noatime when mounting the
volume; does the vfat kernel module honor the noatime option?

-- 
SCREW THE ADS! http://adblock.mozdev.org/

  reply	other threads:[~2007-08-25  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.pKJ1f/uGrEIrPt+FdyZwKxvM2Ws@ifi.uio.no>
2007-08-24 23:36 ` Robert Hancock
2007-08-25  1:06   ` TheOneKEA [this message]
2007-08-25  9:55     ` Alan Cox
2007-08-24  2:44 TheOneKEA
2007-08-24 13:58 ` Lennart Sorensen
2007-08-24 14:41   ` TheOneKEA

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=443c85430708241806y4730bb15n9094fed2e51437f3@mail.gmail.com \
    --to=theonekea@gmail.com \
    --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

all inboxes | Powered by JetHome®