public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: k.lichtenwalder@computer.org
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: xine discussion list <xine-user@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [xine-user] Re: why raw devices don't seek above 4GB (sometimes)
Date: Wed, 18 Apr 2001 06:52:53 +0200	[thread overview]
Message-ID: <3ADD1DA5.3ABAB724@computer.org> (raw)
In-Reply-To: <E14pbfD-00036X-00@the-village.bc.nu>

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

Alan Cox wrote:
> 
> > I set up a raw device: raw /dev/raw/raw1 /dev/hdd
> > with /dev/hdd being my DVD drive.
> > Xine then does repeated llseeks on /dev/raw/raw1 until it gets above 4G.
> > Because /dev/raw/raw1 and the associated /dev/hdd both are on reiserfs,
> > and reiserfs has a 4G limit, llseek assumes the same for the associated
> > raw devices and returns from the llseek with EINVAL. Bang.
> > I don't know whether there's an easy solution.
> 
> That sounds like /dev/raw/.. should have its own lseek method.

Yeah, while going to bed I thought that this can only be cured by doing
an raw-device specific lseek method, as lseek has no other means to find
out which device this really is. I guess I'll give it a try but I don't
know whether I'm up to it.

Klaus
-- 
------------------------------------------------------------------------ 
 Klaus Lichtenwalder, Dipl. Inform.,       http://www.webforum.de/Klaus/
 Fax +49-(0)89-91072699                            Lichtenwalder@ACM.org
 NIC: KL2100, KL76-RIPE                     K.Lichtenwalder@Computer.org
 PGP Key fingerprint = 2658 EA97 E1A1 2680 5ECA  0036 80F5 F250 3CF8
C2C7

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2036 bytes --]

      reply	other threads:[~2001-04-18  4:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 18:52 why raw devices don't seek above 4GB (sometimes) k.lichtenwalder
2001-04-17 20:01 ` Alan Cox
2001-04-18  4:52   ` k.lichtenwalder [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=3ADD1DA5.3ABAB724@computer.org \
    --to=k.lichtenwalder@computer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xine-user@lists.sourceforge.net \
    /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