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
The DVD-RAM is detected like so (my system is an nVidia nForce 590
SLI, with kernel 2.6.22.1 and the new SCSI-using PATA/SATA drivers in
use):
pata_amd 0000:00:0c.0: version 0.3.8
PCI: Setting latency timer of device 0000:00:0c.0 to 64
scsi6 : pata_amd
scsi7 : pata_amd
ata7: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6
bmdma 0x000000000001f400 irq 14
ata8: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376
bmdma 0x000000000001f408 irq 15
ata7.00: ATAPI: MATSHITADVD-RAM LF-D310, A123, max UDMA/33
ata7.00: configured for UDMA/33
ata8: port disabled. ignoring.
scsi 6:0:0:0: CD-ROM MATSHITA DVD-RAM LF-D310 A123 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 6:0:0:0: Attached scsi CD-ROM sr0
Are the above errors related to media flaws, drive flaws, driver
flaws, or usage flaws (i.e. "I copied $LARGE_AMOUNT from a DVD-RAM
disc to a network share", "Don't do that.")?
--
SCREW THE ADS! http://adblock.mozdev.org/
On Thu, Aug 23, 2007 at 10:44:55PM -0400, 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:
No idea about the error, but isn't vfat torture of a dvd-ram? Don't
they come preformated with UDF since it does wear leveling while vfat
would very very quickly trash the part of the disk storing the FAT.
--
Len Sorensen
On 8/24/07, Lennart Sorensen <[email protected]> wrote:
> On Thu, Aug 23, 2007 at 10:44:55PM -0400, 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:
>
> No idea about the error, but isn't vfat torture of a dvd-ram? Don't
> they come preformated with UDF since it does wear leveling while vfat
> would very very quickly trash the part of the disk storing the FAT.
I wouldn't know - someone else gave the media to me and wanted to try
to rescue the data on it. I certainly didn't out vfat on it on
purpose. As soon as I can fix the dmesg errors and get a clean read of
the disk, I intend to clean it off and put UDF on both sides.
--
SCREW THE ADS! http://adblock.mozdev.org/
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.
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?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
Mr. Hancock,
On 8/24/07, Robert Hancock <[email protected]> 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/
> > 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?
And more generally mounting readonly