From: Guest section DW <dwguest@win.tue.nl>
To: Lourenco <andyrock50@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: IDE PROBLEM 2.4.0 and 2.4.1 ...
Date: Wed, 7 Feb 2001 21:36:04 +0100 [thread overview]
Message-ID: <20010207213604.A21989@win.tue.nl> (raw)
In-Reply-To: <20010207191207.50272.qmail@web12008.mail.yahoo.com>
In-Reply-To: <20010207191207.50272.qmail@web12008.mail.yahoo.com>; from Lourenco on Wed, Feb 07, 2001 at 11:12:07AM -0800
On Wed, Feb 07, 2001 at 11:12:07AM -0800, Lourenco wrote:
> i am getting an error every time i try to copy a big
> file from my cdrom to one of my harddrives...
>
> PS : It works FINE with 2.2.* and other OS's...
>
> ...
> VFS: Disk change detected on device ide1(22,0)
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISOFS: changing to secondary root
> isofs_read_level3_size: More than 100 file sections
> ?!?, aborting...
> isofs_read_level3_size: inode=45152 ino=53408
> isofs_read_level3_size: More than 100 file sections
> ?!?, aborting...
> isofs_read_level3_size: inode=45232 ino=53488
> hdc: command error: status=0x51 { DriveReady
> SeekComplete Error }
> hdc: command error: error=0x51
> end_request: I/O error, dev 16:00 (hdc), sector 18356
> hdc: command error: status=0x51 { DriveReady
> SeekComplete Error }
You describe two entirely different things:
(i) the kernel complains that the data on the CD is bad
(ii) the kernel complains that it has problems reading the CD.
The code that generates the message "More than 100 ..."
is almost identical in 2.2 and 2.4 - if you didnt get that
message in 2.2 then perhaps (i) was caused by (ii): there
are problems reading the thing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-07 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 19:12 Lourenco
2001-02-07 20:36 ` Guest section DW [this message]
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=20010207213604.A21989@win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=andyrock50@yahoo.com \
--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®